UK GDPR data minimisation in civil disclosure: pseudonymise before bundle exchange – UK GDPR-compliant anonymisation per UK GDPR Art. 5

UK GDPR Article 5(1)(e) requires that personal data be limited to what is necessary for the specified purpose; in civil litigation, solicitors must balance disclosure obligations under CPR Part 31 with the data-minimisation principle, and anonym.legal assists by pseudonymising non-party personal data in disclosure bundles, enabling proportionate compliance with both regimes simultaneously.

When this applies

Applies when a solicitor is preparing a disclosure bundle for exchange and has identified that the bundle contains personal data about non-parties that is not strictly necessary for the evidential purpose — for example, customer records in a commercial dispute that name hundreds of individuals incidental to the issues.

  1. Upload the full disclosure bundle in PDF or DOCX format.
  2. Identify with the solicitor which categories of personal data are necessary for the disclosed purpose and which are incidental.
  3. Configure anonym.legal to pseudonymise the incidental personal-identifier categories whilst retaining evidentially necessary identifiers in clear.
  4. anonym.legal processes the bundle, applying category-level pseudonymisation rules across the entire document set.
  5. The pseudonymised bundle is reviewed and any remaining personal data in clear is confirmed as necessary.
  6. A reversible mapping is maintained with EU data residency in case re-identification is required by court order.

What you provide

  • Disclosure bundle (PDF or DOCX)
  • Category-level pseudonymisation configuration (which entity types to pseudonymise)
  • Party-names allow-list

Limitations & cautions

  • The data-minimisation assessment — identifying which personal data is necessary — requires legal judgment and cannot be automated by anonym.legal.
  • UK GDPR data-minimisation does not override disclosure obligations under CPR Part 31; a solicitor must confirm that pseudonymisation is consistent with the disclosure order.

FAQ

Is there a conflict between CPR Part 31 disclosure and UK GDPR data minimisation?

Not necessarily — the ICO and courts recognise that proportionate disclosure consistent with data minimisation is good practice. Where third-party personal data is incidental to the dispute, pseudonymising it in the disclosed bundle is consistent with both regimes.

What does UK GDPR Article 5(1)(e) require?

Article 5(1)(e) requires that personal data be kept in a form that permits identification of data subjects for no longer than necessary for the purposes for which it is processed. In a disclosure context, this supports minimising unnecessary third-party identification.

Does DPA 2018 add any additional requirements?

The Data Protection Act 2018 supplements UK GDPR and includes specific exemptions relevant to legal proceedings (Schedule 2, Part 1). The solicitor should confirm whether any DPA 2018 exemption applies to the processing.

Civil Litigation

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.