Pseudonymising Lease Extension Paperwork Under the Leasehold Reform Acts – UK GDPR-compliant anonymisation per UK GDPR

A statutory lease extension under the Leasehold Reform Housing and Urban Development Act 1993 (LRHUDA 1993) adds 90 years at a peppercorn ground rent; collective enfranchisement requires at least 50 percent of qualifying leaseholders. Proceedings involve a formal notice, counter-notice, and draft lease — all naming the tenant, intermediate landlords, and freeholder. anonym.legal pseudonymises those identifiers, preserving the term extension and statutory premium.

When this applies

This task applies when lease extension notices, counter-notices, and draft extended leases are shared with specialist valuers, counsel, or financial advisers advising on the statutory premium or the extended lease terms, and who have no UK GDPR Art. 6 lawful basis to process the personal identities of the named parties for that advisory purpose.

  1. Upload the initial notice (tenant's notice), counter-notice, and draft extended lease to anonym.legal in a single batch.
  2. The engine identifies the qualifying tenant, any intermediate landlords, and the freeholder named across the notices and draft lease.
  3. Each natural person is pseudonymised consistently across all documents; the term extension proposed, the unexpired residue, the statutory premium and its components, and all proposed lease terms are preserved.
  4. Under the Landlord & Tenant Act 1987 Part 1, any right of first refusal notices in the proceedings are also processed if uploaded.
  5. A mapping table is produced with UK/EU data residency.
  6. Release the pseudonymised pack for valuer or legal review; restore originals before any court application or statutory timetable step.

What you provide

  • Tenant's initial notice of claim for a new lease
  • Landlord's counter-notice
  • Draft extended lease
  • Any tribunal application documents (if proceedings have reached tribunal)

Limitations & cautions

  • Lease extension proceedings are subject to strict statutory timetables under the Leasehold Reform, Housing and Urban Development Act 1993; pseudonymised versions are for advisory review only and must not be relied upon for any statutory step or tribunal filing.
  • The statutory premium for a lease extension is a complex valuation matter; from 30 June 2022 extended leases must comply with the Leasehold Reform (Ground Rent) Act 2022 peppercorn ground rent requirement — obtain a specialist surveyor's report.
  • Right of first refusal provisions under the Landlord & Tenant Act 1987 Part 1 apply only in specific circumstances — obtain specialist leasehold advice before any landlord disposal.

FAQ

Are intermediate landlord names pseudonymised alongside the freeholder?

Yes. All named parties in the lease extension proceedings — qualifying tenant, intermediate landlords, and freeholder — are individually pseudonymised with distinct, consistent pseudonyms throughout the batch.

Is the unexpired residue of the lease preserved in the pseudonymised documents?

Yes. The unexpired lease term, the extended term proposed, and all key dates — including the notice date and response deadline — are preserved as they are not personal data.

Can I use this for collective enfranchisement proceedings as well?

Yes. Collective enfranchisement notices and counter-notices follow the same structure and can be processed in the same batch as lease extension documents.

What are the statutory requirements for a qualifying leaseholder to claim a lease extension?

Under the Leasehold Reform Housing and Urban Development Act 1993 (LRHUDA 1993), a qualifying leaseholder must have held the lease for at least 2 years and the lease must be of a flat. The statutory extension adds 90 years to the current unexpired term at a peppercorn ground rent. For collective enfranchisement, at least 50 percent of qualifying leaseholders must participate. The statutory premium is a matter for specialist valuation — obtain expert surveyor and solicitor advice.

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