Anonymising Non-Molestation Order Applications – UK GDPR-compliant anonymisation per UK GDPR

A non-molestation order application is an application under Family Law Act 1996 Part IV, requiring the applicant's name, address, and account of the respondent's abusive behaviour. The Domestic Abuse Act 2021 strengthened victim protections; FPR 2010 r.27.10 ensures private hearings. anonym.legal pseudonymises all identifiers while preserving the incident chronology and relief sought.

When this applies

This task applies when a non-molestation order application under FLA 1996 Part IV is reviewed by a legal-aid supervisor, a domestic abuse support specialist, or a welfare adviser who requires sight of the incident chronology and legal basis but must not have access to the applicant's address or identifying details for safety reasons.

  1. Upload the non-molestation order application (Form FL401) and any supporting witness statement.
  2. The engine identifies the applicant, respondent, and any named children or witnesses across all documents.
  3. Each individual receives a consistent pseudonym; importantly, the applicant's address is pseudonymised with particular care given the safety context.
  4. The incident chronology, dates, descriptions of behaviour, and relief sought are preserved in clear text.
  5. A reversible mapping table is produced with UK data residency; access to real addresses should be restricted on a strict need-to-know basis.
  6. Release the pseudonymised application for review; restore real identities and addresses only for court filing under the court's protected-address protocol.

What you provide

  • Form FL401 non-molestation order application
  • Supporting witness statement
  • Any existing injunction or undertaking documents

Limitations & cautions

  • In proceedings involving domestic abuse within the meaning of DAA 2021 s.1, address information must be handled under the court's protected-address regime — consult the court's confidential address protocol before any disclosure of re-identified documents.
  • anonym.legal provides pseudonymisation for review purposes; decisions about safety planning and risk management under Practice Direction 12J FPR must be made by qualified domestic abuse professionals.
  • The court copy of the FL401 must bear the parties' real details — re-identify only for court filing under FLA 1996 Part IV, not for general distribution.

FAQ

Is the applicant's address pseudonymised when the court uses a protected-address scheme?

Yes. The applicant's address receives the same pseudonymisation as all other personal identifiers. The mapping table — which contains the real address — should only be accessed by the applicant's legal representative and the court under the protected-address protocol.

Can the pseudonymised application be shared with a domestic abuse support organisation?

A pseudonymised version is suitable for case-study review or welfare-adviser briefings. Any sharing with external organisations must comply with the court's disclosure orders and the applicant's safety plan.

Are the respondent's details also pseudonymised in the application?

Yes. The respondent's name, address, and personal details are pseudonymised. The pseudonymised version prevents any inadvertent disclosure of either party's details during the review process.

How does the tool handle exhibits (photographs, messages) attached to the application?

Text-based exhibits (e.g. printed message transcripts) are pseudonymised at the name level. Image files require manual review to redact visual identifiers before upload.

How does the Domestic Abuse Act 2021 affect data handling in non-molestation applications?

The Domestic Abuse Act 2021 created a statutory definition of domestic abuse covering physical, emotional, controlling, and coercive behaviour and came into force in 2021. It strengthened protections for victims' personal data in proceedings under Family Law Act 1996 Part IV. Sharing unredacted FL401 applications beyond authorised recipients risks both civil liability and regulatory sanction — including ICO fines of up to £17.5 million or 4% of global annual turnover under DPA 2018 s.157. Pseudonymising before review-stage sharing limits that risk.

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 company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds 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.