Pseudonymising SYSC 9 Client Records for Audit – UK GDPR-compliant anonymisation per FCA SYSC 9

FCA SYSC 9 requires firms to maintain adequate records of services provided to clients, and those records contain client names, account references, and transaction details. anonym.legal pseudonymises the personal identifiers in client record extracts so internal audit and compliance teams can review record-keeping adequacy and completeness without processing individual client data unnecessarily.

When this applies

This task applies when client record extracts are reviewed by internal audit, compliance oversight, or external assurance teams assessing whether the firm's record-keeping systems and retention practices meet the requirements of FCA SYSC 9, and those reviewers require the structural completeness of the records rather than the specific client's identity.

  1. Upload the client record extract or record-keeping completeness sample.
  2. The engine identifies client names, account references, named relationship managers, and any other personal identifiers in the extract.
  3. Each individual is pseudonymised consistently; service descriptions, transaction references, record categories, and retention-period indicators are preserved.
  4. Record-creation and last-updated timestamps remain in clear text to support record-keeping adequacy assessment.
  5. A reversible mapping table is produced with UK/EU data residency.
  6. Release the pseudonymised extract for audit or assurance review; restore originals for any regulatory inspection.

What you provide

  • Client record extract or record-keeping completeness sample
  • Record-category inventory (if separate from the extract)

Limitations & cautions

  • The tool does not assess whether the record-keeping system and retention periods meet the requirements of FCA SYSC 9.
  • Client record extracts that include embedded transaction confirmations or contract notes with personal data require a batch upload to ensure consistent pseudonymisation.
  • The pseudonymised extract is for internal audit and assurance purposes; regulatory inspection under FCA powers requires the re-identified records.

FAQ

Are retention-period indicators preserved in the pseudonymised extract?

Yes. Record category, retention period, and last-reviewed date are preserved in clear text, which is essential for assessing record-keeping compliance.

Can I use pseudonymised client record extracts to test a new record-keeping system?

Yes. Pseudonymised extracts that preserve the structural completeness of records are suitable for system-testing and data-migration validation without processing real client data in the test environment.

Does the tool handle client records held in spreadsheet format?

Yes. XLSX client record extracts are supported. Named individuals in row or column cells are detected and pseudonymised; structural headers and category labels are preserved.

Financial Services Compliance

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.