By · Last updated 2026-04-27

Back to BlogGDPR & Compliance

Global PII: SSN, CPF, Aadhaar & More

GDPR applies to German Steuer-IDs, French NIRs, Swedish Personnummers, and 260+ other identifier types most tools have never heard of.

April 27, 20268 minute read
global PII coverageEU identifier detectionSteuer-ID French NIRBrazilian CPF285+ entity types GDPR

Global PII: SSN, CPF, Aadhaar & More

The US-Centric PII Tool Problem

Most PII tools were built in the United States. They target US data formats. The Social Security Number has nine digits in AAA-BB-CCCC format. Its area, group, and serial segments follow documented rules. US-focused tools catch it well. They also detect US phone numbers, email addresses, and driver's licenses. They miss every national ID used outside the US.

GDPR does not allow a US-only exemption. Take the German Steuer-ID. It is an 11-digit tax ID. The Bundeszentralamt für Steuern issues it. Its final digit is a checksum. It identifies a German resident just as an SSN identifies an American. GDPR Article 4 covers "any information relating to an identified or identifiable natural person." A Steuer-ID fits that definition. It is personal data. That is true whether or not your tool knows the format.

GDPR fines have followed EU-specific PII exposure in systems using US-only tools. The compliance gap is real. Enforcement actions have resulted. See our GDPR compliance guide for context.

The European Identifier Landscape

The coverage gap is large. Here is a country-by-country breakdown.

Germany: Steuer-ID — 11 digits, checksum-validated. Sozialversicherungsnummer — 12 fields, structured. Reisepass — 10 characters with authority codes.

France: NIR is the national social security ID. It has 15 digits. They encode gender, birth year, birth month, department, commune, and a check key. SIRET has 14 digits. SIREN has nine.

Sweden: Personnummer uses format YYMMDD-XXXX. Samordningsnummer covers non-residents. The day value is offset by 60.

Norway: Fødselsnummer has 11 values in format DDMMYYNNNKK. Gender is encoded in the middle group. D-nummer offsets the day value by 40.

Brazil: CPF — Cadastro de Pessoas Físicas — has 11 digits with two check values. CNPJ is the 14-number business ID.

India: Aadhaar is a 12-digit biometric ID. It uses a Verhoeff check. PAN is a 10-digit tax ID with letters and numbers.

UAE: Emirates ID has 15 numbers in the format 784-birth year-sequence-check.

A global HR team covering 12 countries needs one tool. It must handle all 12 national ID formats in a single pass. Maintaining separate regex libraries per country is not workable.

The 285+ Entity Type Architecture

The 285+ entity type library covers all EU member state formats. It also covers major APAC IDs. Those include Aadhaar, PAN, CPF, CNPJ, Emirates ID, and Thai citizen ID. US formats — SSN, EIN, state driver's licenses — are included too. One engine handles them all. The library updates as formats change.

This is the gap most tools leave open. See the entities reference to review what is covered. For API pricing by volume, visit pricing.

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.