Anonymising Pre-Nuptial and Post-Nuptial Agreements – UK GDPR-compliant anonymisation per Matrimonial Causes Act 1973

Pre-nuptial and post-nuptial agreements identify the parties by full name, address, and financial details, and may include schedules disclosing assets, property interests, business holdings, and inheritance expectations. anonym.legal pseudonymises those personal identifiers — preserving financial provisions, ring-fenced assets, and review clauses — so the agreement can be shared with specialist advisers without exposing the parties' identities.

When this applies

This task applies when a pre-nuptial or post-nuptial agreement is shared with a forensic accountant, specialist family-finance solicitor, or financial adviser for an opinion on the fairness or enforceability of the financial provisions, and those advisers do not require the parties' identities to advise on the financial structure.

  1. Upload the pre-nuptial or post-nuptial agreement and any financial schedules.
  2. The engine identifies both parties' names, addresses, solicitors' details, and any named witnesses or notaries.
  3. Each individual receives a consistent pseudonym; ring-fenced asset values, property descriptions, business-holding particulars, and review trigger clauses are preserved in clear text.
  4. Advice-certification clauses (confirming independent legal advice) are preserved; the advising solicitor's name is pseudonymised.
  5. A reversible mapping table is produced with UK data residency.
  6. Release the pseudonymised agreement for adviser review; restore real identities before execution.

What you provide

  • Pre-nuptial or post-nuptial agreement document
  • Financial schedule disclosing assets
  • Independent legal advice certificates if annexed

Limitations & cautions

  • The enforceability of pre-nuptial and post-nuptial agreements under English law depends on procedural compliance — anonym.legal does not advise on enforceability.
  • Executed copies that have been signed and witnessed must re-identify all named parties before any court reliance.
  • Property particulars that identify a specific address may require careful pseudonymisation to prevent indirect identification of the parties.

FAQ

Can the pseudonymised agreement be used in financial-remedy proceedings?

No. The court-facing version must identify the parties. The pseudonymised version is for pre-proceedings review and adviser instruction only.

Are witness names on the signature page pseudonymised?

Yes. Witnesses named on the signature page are pseudonymised. Their signatures are preserved in the document image but their printed names are replaced with pseudonyms.

Does the tool handle agreements governed by foreign law (e.g. a New York pre-nup)?

The engine pseudonymises personal data irrespective of governing law. Whether the financial provisions are enforceable under the governing foreign law is a separate legal question requiring specialist advice.

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.