Anonymising Divorce Petitions (Form D8) for Mediation – UK GDPR-compliant anonymisation per Family Procedure Rules 2010

A divorce petition (Form D8) identifies both parties by full name, address, date of marriage, and children's details, and is routinely exchanged with mediators and family-law counsel. anonym.legal pseudonymises those personal identifiers — preserving the ground for divorce, particulars, and procedural history — so the petition can be reviewed without disclosing the parties' identities to third parties.

When this applies

This task applies when a completed or draft Form D8 is shared with a mediator, Collaborative Law practitioner, or external counsel for procedural advice, and those advisers do not require the parties' real identities to advise on the divorce ground or procedure.

  1. Upload the Form D8 (PDF or DOCX) to anonym.legal; document structure and pagination are preserved.
  2. The engine detects both parties' names, addresses, dates of birth, National Insurance numbers, and children's details across all sections of the form.
  3. Each named individual (petitioner, respondent, and any named children) receives a unique, consistent pseudonym applied throughout the document.
  4. The ground for divorce, particulars of unreasonable behaviour or separation periods, and procedural tick-boxes remain in clear text.
  5. A reversible mapping table is generated with UK data residency.
  6. Download the pseudonymised petition for mediator or adviser review; restore real identities using the mapping key before filing with the court.

What you provide

  • Completed or draft Form D8 (divorce petition)
  • Any accompanying statement of arrangements for children (if filed with the D8)
  • List of parties' roles and relationship (to guide pseudonym labelling)

Limitations & cautions

  • The court-filed version must bear the parties' real names and must be re-identified from the mapping key before submission.
  • Handwritten or scanned forms require OCR pre-processing before entity detection achieves full coverage.
  • anonym.legal does not provide legal advice on the adequacy of the particulars or the choice of divorce ground.

FAQ

Does pseudonymisation affect the legal validity of the petition?

No. The pseudonymised version is a review copy only. The court copy must bear the parties' real legal names. Re-identify using the mapping key before any court filing.

Are children's names and dates of birth pseudonymised?

Yes. Children are detected as distinct data subjects and each receives a consistent pseudonym separate from the parties, so the family structure is preserved while protecting the children's identities.

Can I process a joint application under the no-fault divorce process?

Yes. Joint applications naming both applicants are processed identically to sole petitions — both parties' personal data are pseudonymised consistently.

What happens to National Insurance numbers in the form?

National Insurance numbers are detected as personal identifiers under UK GDPR and are pseudonymised with consistent placeholder references, preserving the field structure.

Family Law

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.