Redact a bank statement: remove text and check hidden data

Start with what the other person actually needs

A landlord asking for financial evidence and a friend helping with a spreadsheet need different things. Before editing, ask which pages and fields the recipient needs, whether redactions are acceptable, and where to send the file. A field you consider irrelevant might be part of their check, and this page can't settle those requirements.

An accountant doing reconciliation may need transactions or references to trace, so agree the scope before removing them. If a friend is checking a shared expense, ask whether a short list of the relevant payments would answer the question instead of a full statement. Just label it as an extract, not a complete statement.

A public forum is different again: use a fictional example with the same formatting problem. That means inventing fresh names, dates, amounts and references, rather than changing only your name on a real statement. Someone who knows about a particular payment could still recognize its date and amount. There's rarely a good reason to publish your actual financial history to explain a broken formula.

Keep the original separately and give the working copy an unmistakable label. The ICO's redaction guidance, published July 31, 2025 and marked under review when checked, recommends working on a copy, checking before disclosure, and recording who redacted it, when and why.

A black box can cover text without removing it

A drawing tool changes what you see; a redaction tool is intended to remove the selected content from the sharing copy. The ICO gives a concrete example of why this matters: copying a PDF covered with simple black rectangles into a plain-text editor can recover the text underneath. Changing text to white hides it too. It doesn't remove it.

Converting a document to PDF isn't a complete redaction method either, as the same ICO guidance warns. It describes image-conversion alternatives, but says roundtrip conversion requires a thorough understanding of the formats involved. An improvised sequence of screenshots, cropping and exports isn't a certified result. If you can't assess the final file, use a synthetic example or get help from someone trained in document redaction.

Visible text is only part of the review. In its separate hidden-information guidance, also carrying a July 31, 2025 publication note and an under-review warning, the ICO describes document properties such as author and title, embedded files, and comments that may disclose information you did not notice on the page.

Apply the PDF redactions before you save

Adobe documents this sequence for Acrobat Pro in Redact sensitive content, updated August 31, 2026. The menu labels below come from Adobe's instructions; the page-review and copy-handling precautions are our recommendations. We did not test these steps in Acrobat:

1. Open your working copy and choose All tools → Redact a PDF, then Redact text and images.
2. Select the text or image areas to remove, reviewing every page before proceeding. Include repeated headings and footers in that review.
3. Select Apply, because marking areas isn't the end of the documented process.
4. In the dialog, enable the option to sanitize and remove hidden information for the sharing copy, then select Continue.
5. In Save Sanitized Document, choose a distinct filename and location, then select Save. If it helps avoid attaching the original by mistake, keep it out of the folder you'll attach from.

If you're using another editor, follow its current instructions for applied redaction and hidden-data removal. A menu called Draw, Highlight or Annotate isn't evidence that the selected content will be removed. Without a suitable feature, ask whether the recipient can accept a smaller, separately prepared extract or another form of evidence.

A fictional example: the reference appears more than once

Suppose a fictional statement belongs to Morgan Ellis and contains the invented account label DEMO-001234. The intended reader needs a payment amount, not the account reference or unrelated merchant. This table is a disclosure plan, not an actual redacted PDF or a claim about what any recipient must accept.

A rectangle over the heading wouldn't address the footer or author property, and even an applied redaction of the heading would leave this plan incomplete. That's why the review searches for both the full reference and its distinctive portion, 001234, and checks the document properties as well as the page.

Your own plan should include any names, addresses, payment references, account details or machine-readable codes that don't belong in the disclosure. A few remaining account digits aren't necessarily irrelevant: what can stay depends on the agreed purpose, not how small it looks on the page.

Reopen the file you are actually going to send

The final saved file is the one that matters, not the editor's preview. To check that version, close it and reopen the sharing copy from its saved location. If possible, have another authorized person review it too, especially when a mistake would expose someone else's information. The checks below cover both what you see and what you can extract.

• During a visual review of every page, look at margins, continuation pages and the edges of redacted areas for surviving letters or digits. The information you intended to retain should still be readable.
• Search for the names, full references and distinctive fragments you intended to remove. A remaining match is a reason to stop and correct the copy.
• Try selecting and copying text around the redacted areas, and inspect the available document text in a local plain-text editor. If the covered text appears, the redaction failed. The copied text is sensitive too, so don't put it in an online checker, a public support form or the sharing attachment.
• A clean-looking page doesn't mean the entire file contains only that page's content. Review document properties, comments, attachments and the editor's hidden-information inspection results as well.

Finding nothing in search or copy/paste doesn't establish complete removal. Those checks can't assess content the viewer doesn't expose as searchable text, and the ICO warns that inspection tools may miss hidden information too. The checks need to work together; no single result is clearance to share. Our guide to scanned and text-based statements explains why selecting text is a useful diagnostic, not a verdict on the whole PDF.

For CSVs, remove fields instead of hiding columns

A hidden spreadsheet column hasn't been deleted. The ICO's hidden-information guidance distinguishes presentation from removal and explains that CSV conversion removes spreadsheet formatting. To see which values actually survived export, inspect the saved CSV as text rather than relying on the workbook's appearance. If you're sending the workbook too, its comments and other content need their own review.

For a small sharing copy, you can manually retain only the required fields and replace explicitly chosen sensitive text. The CSV redactor offers the same kind of keep-column and literal-replacement controls with a preview. It doesn't redact PDFs or automatically discover sensitive information.

Here is a separate fictional CSV using the invented names above. Both amounts are USD; money leaving the account is negative. This is an explanation sample, not a real bank export:

Date,Account,Description,Amount
2026-10-01,DEMO-001234,Payment to Morgan Ellis ref DEMO-7788,-42.50
2026-10-02,DEMO-001234,Willow Clinic ref DEMO-8899,-18.00

For this copy, we want to keep Date, Description and Amount, so the Account column goes entirely. Within Description, replace Morgan Ellis with [PERSON], Willow Clinic with [MERCHANT], and each of DEMO-7788 and DEMO-8899 with [REF]. The expected cell text is:

Date,Description,Amount
2026-10-01,Payment to [PERSON] ref [REF],-42.50
2026-10-02,[MERCHANT] ref [REF],-18.00

That removes one column, changes two description cells and makes four replacements. Both data rows remain, and the signed total stays -42.50 - 18.00 = -60.50 USD. Still, a matching total can't tell you whether every amount stayed unchanged: offsetting changes can cancel out. That's why you also need to compare each retained date and amount with the input. Neither check establishes anonymity, statement completeness or reconciliation.

The tool's replacements are case-sensitive and apply only to the columns you select. A differently written name or the same reference in another retained column needs a separate decision, so read every retained field, including headings, then inspect the downloaded file. Even with the selected tokens gone, the remaining dates, amounts and payment pattern are still financial information.

Keep the check record separate from the attachment

A short private note can record the recipient, purpose, fields removed, filename, check date and reviewer without repeating the sensitive values you removed. The statement review log guide offers a way to keep review notes separate from transaction data. An unredacted log doesn't belong in the sharing attachment.

The filename can disclose an account number or another detail you meant to remove, so inspect it along with the attachment's content. Before sending, confirm the recipient and use the channel you agreed with them. If there's any chance you chose the original, open the selected attachment once more. Label the file as redacted or as an extract, and describe the omissions without disclosing their contents.

What we checked

On October 17, 2026, we opened the two ICO pages cited above, including their July 31, 2025 publication notes and under-review notices, and Adobe's instructions updated August 31, 2026. We checked the CSV example's field removal and replacements in Python and recomputed its total with Decimal. We also read the CSV helper's replacement logic. We did not run Acrobat, test a real statement, perform a forensic examination, or test recipient acceptance. The PDF steps describe vendor instructions and recommended checks, not a guarantee of complete sanitization or legal compliance.