Anonymising Contracts for Sale in Residential and Commercial Conveyancing – UK GDPR-compliant anonymisation per Law of Property (Miscellaneous Provisions) Act 1989 s.2

A contract for sale of land must satisfy the formal requirements of the Law of Property (Miscellaneous Provisions) Act 1989 s.2, and names the seller, buyer, their solicitors, the property, and the agreed price. anonym.legal pseudonymises those personal identifiers across draft and engrossed contracts — preserving the property description, completion date, purchase price, title number, and all incorporated conditions — so the commercial terms can be reviewed before exchange without personal-data exposure.

When this applies

This task applies when a draft contract for sale (whether incorporating the Standard Conditions of Sale or the Standard Commercial Property Conditions) is shared with the client, a lender, a third-party reviewer, or a co-purchaser's separate legal advisers before exchange of contracts.

  1. Upload the draft or engrossed contract for sale (PDF or DOCX) and any special conditions document to anonym.legal.
  2. The engine identifies the seller's and buyer's names and addresses in the front page and execution block, together with named solicitors' contacts.
  3. Each natural person is pseudonymised consistently; the property address (as a property description rather than a residence indicator), title number, purchase price, completion date, deposit amount, and all Standard Conditions remain in clear text.
  4. Special conditions naming individual occupiers or tenants are pseudonymised at the name level while the condition substance is preserved.
  5. A mapping table is produced with UK/EU data residency.
  6. Circulate the pseudonymised contract for review; restore original names before exchange, at which point the contract becomes binding under the Law of Property (Miscellaneous Provisions) Act 1989 s.2.

What you provide

  • Draft or engrossed contract for sale (incorporating SCS or SCPC)
  • Special conditions document (if separate from the main contract)
  • Replies to enquiries document (if appended as an exhibit)

Limitations & cautions

  • A contract for sale of land is not legally binding until exchange of contracts — the pseudonymised version is a working copy for pre-exchange review only.
  • The Law of Property (Miscellaneous Provisions) Act 1989 s.2 requires the contract to be in writing, signed, and contain all agreed terms; the executed original must bear the correct legal names.
  • The tool does not assess compliance with the Standard Conditions of Sale or the Standard Commercial Property Conditions — obtain conveyancing legal advice.

FAQ

Will pseudonymisation affect the binding effect of the contract at exchange?

The pseudonymised copy is not the contractual document. Exchange of contracts takes place using the original named versions; the pseudonymised copy is for pre-exchange review only.

Does the tool handle contracts incorporating the Standard Commercial Property Conditions?

Yes. The engine pseudonymises personal identifiers in the contract particulars and execution block regardless of which set of conditions is incorporated. The conditions text itself is preserved.

Are tenants' names in special conditions pseudonymised?

Yes. Named tenants or occupiers referenced in special conditions (for example, a condition subject to an existing tenancy) are pseudonymised while the tenancy condition substance is preserved.

Can I process a sale contract and the replies to enquiries in the same batch?

Yes. Upload all documents together so that any individual named in both receives consistent pseudonyms across the full pre-contract pack.

Property & Conveyancing

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.