anonym.legal

By · Last updated 2026-05-02

Terug na BlogGDPR & Nakoming

Globale PII-nakoming: GDPR, LGPD en DPDP

Brasiliaanse CPF, Indiese Aadhaar en Amerikaanse SSN het fundamenteel verskillende formate en valideringslogika. LGPD en Indie se DPDP Wet voeg CPF en Aadhaar by die lys van beskermde identifiseerders.

May 2, 20268 min lees
global PII complianceBrazilian CPF detectionIndian Aadhaar DPDPLGPD compliancemulti-regulatory PII

Globale PII-nakoming: Drie Wette, Drie ID-formate

'n Britse markplek hanteer verkoperdokumente uit 80 lande. Drie wette geld gelyktydig: GDPR vir EU-verkopers, LGPD vir Brasiliaanse verkopers en Indie se DPDP Wet vir Indiese verkopers. Elke wet noem verskillende nasionale ID'e as beskerm. Elke formaat het sy eie kontrolelogika.

Brasiliaanse CPF: Formaat en LGPD-status

Die CPF (Cadastro de Pessoas Fisicas) is Brasilse belastingnommer. Dit het 11 syfers in die formaat XXX.XXX.XXX-XX. Die laaste twee syfers is kontrolesyfers. 'n Wiskundige algoritme op die eerste nege syfers produseer hulle.

Brasilse LGPD behandel CPF as 'n beskermde persoonlike identifiseerder, soortgelyk in sensitiwiteit aan 'n Amerikaanse SSN. 'n Instrument wat nie die CPF-formaat ken nie, kan dit nie vind nie. Een wat die kontrolesom oorslaan, sal vals treffers merk.

Indiese Aadhaar: Formaat en DPDP-reels

Aadhaar is 'n 12-syfer-nommer wat deur Indie se UIDAI uitgereik word. Nommers word lukraak toegewys. Die laaste syfer is 'n Verhoeff-kontrolesyfer.

Indie se DPDP Wet skep verpligtinge vir enige groep wat Aadhaar-gekoppelde data hanteer. Opsporing vereis twee stappe. Eerste, pas die 12-syfer-formaat en kontroleer die Verhoeff-syfer. Tweede, filter na konteks. Nie elke 12-syfer-string is 'n Aadhaar nie.

Amerikaanse SSN: 'n Bekende Struktuur

Die SSN is nege syfers. Die eerste drie is die gebiedsnommer. Die volgende twee is die groepnommer. Die laaste vier is die serienommer. Elke segment het vaste reels. Validering is goed gedokumenteer.

Die Gaping Tussen Eenland-gereedskap en Globale Reels

Hierdie drie ID'e deel geen formaat en geen kontrolereel nie. 'n Instrument gebou vir Amerikaanse gebruik sal SSN'e opvang. Dit kan CPF en Aadhaar heeltemal mis.

Die meeste spanne vind hierdie gaping wanneer 'n reguleerder vra -- nie daarvoor nie. Die gaping skep werklike risiko onder elke wet:

  • GDPR Artikel 28 vereis 'n geskrewe Data Verwerking-ooreenkoms met elke verwerker. 'n DPIA wat "SSN-opsporing" as die hoofbeheer lys -- wanneer die datastel ook CPF-nommers bevat -- het 'n gedokumenteerde gaping. 'n Ouditeur kan dit vind.
  • LGPD boetes kan 2% van Brasiliaanse inkomste bereik, tot R$50 miljoen per oortreding. 'n CPF wat onopgespoor bly, is 'n direkte LGPD-skending.
  • DPDP handhawing is steeds nuut. Spanne wat nou hul dekking aanteken sal beter geplaas wees wanneer vroegtydige uitsprake die standaard stel.

Drie boetestelsels gelyktydig skep gelaagde risiko. Eenland-gereedskap laat globale spanne blootgestel.

Wat Volledige Dekking Vereis

'n Instrument benodig elke ID se formaat, kontrolealgoritme en regskonteks. CPF benodig 'n modulere kontrolesom. Aadhaar benodig die Verhoeff-kontrole plus konteksfiltering. SSN benodig gebied- en groepreels. Dit is drie afsonderlike probleme. Geen enkele soekpatroon dek almal nie.

Sien ook: globale PII-identifiseerder-gaping: SSN, CPF, Aadhaar, ANPD Brasilse LGPD-handhawingsgids en DPDPA Indie privaatheidsreg tegniese nakoming.

Bronne

Gereed om u data te beskerm?

Begin om PII te anonimiseer met 285+ entiteitstipes in 48 tale.

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.