BASALT · JOURNAL
How to redact a PDF before sending it for translation
Translation vendors need language context, not necessarily every name, account number, or signature in a document. Redacting first reduces unnecessary disclosure and can make the translator’s work more focused.
Preserve linguistic context
Keep the sentences and terms needed for accurate translation. Replace or remove personal identifiers only when the meaning remains clear. If a placeholder is necessary, use a consistent token such as [CLIENT] and keep any mapping separate.
Review all layers
Check text, scanned images, footnotes, headers, forms, comments, attachments, and metadata. Account numbers and names may appear in tables or screenshots. Do not send an overlay-only redaction to a vendor.
Verify the vendor copy
Search for the original identifiers, inspect pages at high zoom, and confirm the file opens without unexpected attachments or scripts. Keep the original and placeholder mapping under controlled access.
Frequently asked questions
Does redaction hurt translation quality?
It can if too much context is removed. Preserve the surrounding language and explain placeholders to the translator.
Should names be replaced or deleted?
Choose the method that preserves meaning while meeting the privacy requirement.
Can a translation vendor receive the original for quality review?
Only when authorized and necessary. Minimize first and use approved channels.
Doing it in Basalt
Basalt permanently removes or replaces sensitive PDF content locally, so you can send a purpose-limited copy to the translation workflow. Download Basalt.
Redaction that proves itself
Basalt destroys the content you mark, then re-opens the file it wrote and proves the content is gone before it saves anything. Your documents never leave your Mac.