Branch Transaction Log Redaction with anonym.plus

Clear customer and account data from a teller register before you share it.

Branch transaction log redaction is the removal of personal data from a daily teller record. GLBA (15 U.S.C. §6802) limits how a bank shares nonpublic customer information. anonym.plus marks each row on your device, so the activity pattern stays readable while customer data is shielded.

When this applies

Such a register lists each customer, account, and amount across a day. You must mask those before the file goes to an analyst.

How anonym.plus handles it

  1. Open the register in anonym.plus on your device.
  2. Local OCR reads any imaged pages.
  3. The tool flags customers, accounts, and amounts.
  4. Confirm the flags and keep the teller and time codes.
  5. Apply Mask across the customer and account columns.
  6. Save the clean record locally.

What you need to provide

PII & financial identifiers detected

Categoryanonym.plus entity typeExample
NamesPERSONcustomer A. Cole → [CUSTOMER]
FinancialUS_BANK_NUMBERacct 9087 → ****9087
MoneyMONEY$540.00 → [AMOUNT]
IdentifiersUS_SSNtax SSN → [SSN]
DatesDATE_TIME10:42 04/2026 → [TIME]
LocationLOCATIONbranch code → [LOCATION]

Compliance achieved

Anonymize branch transaction logs offline — see plans & start free →

Limitations & cautions

A rare amount at a known time can re-identify a customer even with names masked. Consider grouping or rounding amounts when the file is for analysis rather than reconciliation.

Frequently asked questions

Can the tool mask a whole column?

Yes. For a CSV or tabular file, it flags every value in the customer and account columns so you can mask them together.

Will teller and time codes survive?

Yes. Allow-list those operational codes so the activity pattern stays for analysis.

Is the file uploaded for processing?

No. The app is fully offline, so the record stays on your device.