Anonymising LLC1 and CON29 Local Authority Search Results – UK GDPR-compliant anonymisation per UK GDPR

A local authority search comprises the LLC1 (Local Land Charges Register search) and the CON29 enquiries of the local authority, which together disclose planning history, road agreements, enforcement notices, and financial charges on a property — many of which reference named individuals as applicants, owners, or notice addressees. anonym.legal pseudonymises those personal identifiers while preserving the substantive search results and local authority responses.

When this applies

This task applies when LLC1 and CON29 search results are shared with a purchaser's advisers, a funder, or a third-party consultant who needs the planning and local-charge information but has no legitimate need to know the identities of the named individuals referenced in those results.

  1. Upload the LLC1 and CON29 search results (typically received as a combined PDF from the local authority or a personal search company).
  2. The engine identifies named individuals in local land charges (e.g. financial charges naming individuals), planning enforcement notices, and listed-building or conservation-area notices.
  3. Each natural person is pseudonymised consistently; planning references, road adoption status, drainage agreements, and the substance of any enforcement notices remain in clear text.
  4. A mapping table is produced with UK/EU data residency.
  5. Release the pseudonymised search results for review; the originals should be retained and provided to the lender if required.
  6. Re-identify via the mapping key before any formal lender or regulatory submission.

What you provide

  • LLC1 Local Land Charges search certificate
  • CON29 enquiries of the local authority (standard and any optional questions)
  • CON29O optional enquiries (if raised)

Limitations & cautions

  • Local authority searches have a limited validity period; ensure the search is current before relying on the results for exchange.
  • The tool pseudonymises personal identifiers in search results but does not advise on the planning or legal implications of any entries — obtain conveyancing advice.
  • Personal search companies' results are not official local authority documents; the same pseudonymisation approach applies but confirm accuracy with the search provider.

FAQ

Are planning enforcement notices pseudonymised in the CON29 results?

Named individuals in enforcement notices (e.g. the notice addressee) are pseudonymised. The enforcement notice reference number, breach description, and compliance status are preserved.

Do local authority financial charges (e.g. council improvement grants) name individuals?

Some local land charges (such as improvement grants under housing legislation) may name the property owner or grant recipient. Those individuals are pseudonymised while the charge amount and purpose are preserved.

Can I process local authority searches for multiple properties in a portfolio transaction?

Yes. Upload all search results in a batch. The engine tracks individuals who may appear across multiple searches (e.g. a landlord owning several portfolio properties) and applies consistent pseudonyms.

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.