Pseudonymising TR1, TP1, and TR2 Transfer Forms Before Exchange – UK GDPR-compliant anonymisation per Land Registration Act 2002

HM Land Registry TR1 (whole title transfer), TP1 (part of title transfer), and TR2 (transfer of charge) forms identify the transferor, transferee, their addresses, and any guarantors or additional parties in the execution block. anonym.legal pseudonymises those natural-person identifiers — preserving the title number, consideration, capacity declarations, and prescribed clauses — so draft transfer forms can be reviewed and negotiated externally without premature personal-data disclosure.

When this applies

This task applies when draft TR1, TP1, or TR2 forms are circulated between the parties' solicitors, sent to a lender for approval, or reviewed by a third-party adviser before exchange of contracts, and the reviewing party does not yet have a need to process the parties' full personal details.

  1. Upload the draft TR1, TP1, or TR2 form (PDF or DOCX) to anonym.legal.
  2. The engine identifies the transferor(s) and transferee(s) by name and address in panel 2, panel 4, and the execution block, together with any named guarantors or additional parties.
  3. Each natural person is pseudonymised consistently; the title number, date of transfer, consideration figure, capacity declarations, prescribed clauses, and any agreed additional clauses remain in clear text.
  4. Co-ownership declarations in panel 10 of a TR1 (where present) are pseudonymised at the name level while the trust or tenancy-in-common terms are preserved.
  5. A mapping table is produced with UK/EU data residency.
  6. Release the pseudonymised form for review or negotiation; restore original names before execution and Land Registry submission.

What you provide

  • Draft TR1, TP1, or TR2 form
  • Any attached execution schedule naming additional parties
  • Lender's requirements or form of transfer if separately provided

Limitations & cautions

  • The executed transfer submitted to HM Land Registry must contain the correct legal names of all parties — never submit a pseudonymised form to the Land Registry.
  • Execution requirements for deeds (Law of Property (Miscellaneous Provisions) Act 1989 s.1 and the Land Registration Rules 2003) require personal signatures; pseudonymised execution blocks must be re-identified before the form is signed.
  • The tool does not advise on the legal adequacy of prescribed clauses or co-ownership declarations — obtain conveyancing advice.

FAQ

Can I pseudonymise a TR1 that has already been executed by one party?

Yes, but note that a pseudonymised copy of an executed document is for review purposes only. Any execution already on the form retains its legal effect on the original — only the review copy is pseudonymised.

Does the tool handle TP1 forms where only part of a registered title is transferred?

Yes. TP1 forms follow the same structure as TR1. All personal identifiers in the transferor/transferee panels and execution block are pseudonymised; the title number, filed plan reference, and land description are preserved.

What is a TR2 and how does it differ from a TR1 for pseudonymisation purposes?

A TR2 transfers a registered charge rather than the freehold or leasehold estate. The pseudonymisation approach is the same: the chargor and chargee personal identifiers are pseudonymised while the charge details and title number are preserved.

Are solicitors' firm details in the execution block pseudonymised?

No. Solicitors' firms are companies rather than natural persons and are not personal data under UK GDPR. Only named individual natural persons (parties, guarantors) are pseudonymised.

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.