By · Last updated 2026-05-02

Back to BlogGDPR & Compliance

Global PII Compliance: GDPR, LGPD, and DPDP

Brazilian CPF, Indian Aadhaar, and US SSN have fundamentally different formats and validation logic. LGPD and India's DPDP Act add CPF and Aadhaar to the.

May 2, 20268 minute read
global PII complianceBrazilian CPF detectionIndian Aadhaar DPDPLGPD compliancemulti-regulatory PII

Global PII Compliance: Three Laws, Three ID Formats

A UK marketplace handles seller documents from 80 countries. Three laws apply at once: GDPR for EU sellers, LGPD for Brazilian sellers, and India's DPDP Act for Indian sellers. Each law names different national IDs as protected. Each format has its own check logic.

Brazilian CPF: Format and LGPD Status

The CPF (Cadastro de Pessoas Físicas) is Brazil's taxpayer number. It has 11 digits in the format XXX.XXX.XXX-XX. The last two digits are check digits. A math algorithm on the first nine digits produces them.

Brazil's LGPD treats CPF as a protected personal identifier, similar in sensitivity to a US SSN. A tool that does not know the CPF format cannot find it. One that skips the checksum will flag false matches.

Indian Aadhaar: Format and DPDP Rules

Aadhaar is a 12-digit number issued by India's UIDAI. Numbers are assigned at random. The last digit is a Verhoeff check digit.

India's DPDP Act creates duties for any group handling Aadhaar-linked data. Detection needs two steps. First, match the 12-digit format and check the Verhoeff digit. Second, filter by context. Not every 12-digit string is an Aadhaar.

US SSN: A Known Structure

The SSN is nine digits. The first three are the area number. The next two are the group number. The last four are the serial number. Each segment has set rules. Validation is well documented.

The Gap Between Single-Country Tools and Global Rules

These three IDs share no format and no check rule. A tool built for US use will catch SSNs. It may miss CPF and Aadhaar entirely.

Most teams find this gap when a regulator asks — not before. The gap creates real risk under each law:

  • GDPR Article 28 requires a written Data Processing Agreement with each processor. A DPIA that lists "SSN detection" as the main control — when the dataset also holds CPF numbers — has a documented gap. An auditor can find it.
  • LGPD fines can reach 2% of Brazilian revenue, up to R$50M per breach. A CPF that goes undetected is a direct LGPD violation.
  • DPDP enforcement is still new. Teams that log their coverage now will be better placed when early rulings set the standard.

Three fine regimes at once create layered risk. Single-country tools leave global teams exposed.

What Full Coverage Requires

A tool needs each ID's format, check algorithm, and legal context. CPF needs a modular checksum. Aadhaar needs the Verhoeff check plus context filtering. SSN needs area and group rules. These are three separate problems. No single search pattern covers all of them.

See also: global PII identifier gap: SSN, CPF, Aadhaar, ANPD Brazil LGPD enforcement guide, and DPDPA India privacy law technical compliance.

Sources

Ready to protect your data?

Start anonymizing PII with 285+ entity types across 48 languages.

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.

Related reading

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.