Claim Form (N1): redact third-party details before internal review – UK GDPR-compliant anonymisation

The Claim Form (N1) commences civil proceedings and states the nature of the claim and the parties; where the brief details of claim reference non-party witnesses or third-party data, anonym.legal pseudonymises those identifiers so draft claim forms can circulate internally without premature disclosure of third-party personal data before the form is issued.

When this applies

Applies when a solicitor is preparing an N1 Claim Form whose brief details of claim or attached Particulars reference individuals beyond the immediate parties to the proceedings.

How anonym.legal handles it

Upload the draft N1 Claim Form and any attached document in DOCX or PDF format.
Configure the party-names allow-list for claimant and defendant.
anonym.legal pseudonymises third-party personal identifiers in the brief details and any attachment.
Court fee, remedy sought, and case reference fields are preserved in full.
A reversible mapping is stored for re-identification before issue.

What you provide

Draft N1 Claim Form (DOCX or PDF)
Attached Particulars of Claim if not already processed
Party-names allow-list

Limitations & cautions

The N1 issued by the court will include full party names — ensure you re-identify completely before submission to HMCTS.
Court-issued fee and case reference fields are not altered.

FAQ

Does anonym.legal support online claim forms submitted through HMCTS Money Claim Online?

anonym.legal processes DOCX and PDF offline. For online portal submissions, apply re-identified names at the point of online entry.

Can I process the N1 and the Particulars of Claim together?

Yes — upload both in one session for consistent pseudonymisation across both documents.

What if the N1 is already issued and I need to pseudonymise it for a subsequent sharing?

You can process an already-issued N1 using the same workflow; note that the issued form is a public document and parties' names will be known to the court.

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.