BASALT · JOURNAL
PDF redaction for public-records requests
Public-records releases balance transparency with statutory privacy exceptions. A clean workflow separates pages that should not be released from information that can be disclosed after targeted redaction.
Build a response inventory
Record the request scope, responsive page set, exemption categories, and any required notation. Remove duplicate drafts and irrelevant attachments before marking. Keep the original records under the agency’s retention and access controls.
Apply consistent exceptions
Search names, addresses, phone numbers, medical details, minors’ information, and account identifiers in multiple formats. Review photographs, handwritten notes, OCR, forms, comments, and attachments. Keep enough context for the public to understand the record.
Validate the release package
Check page count, order, labels, redaction permanence, metadata, and attachments. Reopen every released PDF and search for exempt values. Preserve a private redaction log that explains the legal category without reproducing the data.
Frequently asked questions
Should a withheld page be deleted silently?
Follow the governing public-records procedure, which may require a placeholder or explanation.
Can OCR miss information in a scan?
Yes. Combine search with page-by-page visual review.
Are comments and metadata public records?
They can be disclosed unintentionally. Review and remove them when they are not part of the approved release.
Doing it in Basalt
Basalt supports local, repeatable PDF redaction and verification for public-records releases, without uploading the source records. 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.