anonym.legal

By · Last updated 2026-06-05

Terug naar BlogGDPR & Naleving

Presidio mist 220+ GDPR-entiteiten

Presidio wordt geleverd met ~40 standaard entiteitsherkenners gericht op Amerikaanse identifiers. Europese organisaties hebben IBAN, Codice Fiscale en andere EU-identifiers nodig.

June 5, 20267 min lezen
Presidio entity coverageEU GDPR PIIIBAN detectionEuropean identifiersPresidio vs managed

Presidio mist 220+ GDPR-entiteiten: de EU-dekkingskloof

Bijgewerkt voor 2026

Microsoft Presidio wordt geleverd met ongeveer 40 standaard entiteitsherkenners. Voor Amerikaanse implementaties werkt dit. Het omvat SSN's, Amerikaanse paspoorten, rijbewijzen, creditcards en e-mails.

Voor EU-implementaties is de kloof groot. GDPR omvat alle EU-persoonsgegevens. Dit geldt ongeacht de nationaliteit van de betrokkene. EU-teams hebben entiteitsherkenners nodig die specifiek zijn voor elk EU-land.

Wat Presidio standaard mist

Nationale belasting-ID's:

  • Duits Steueridentifikationsnummer
  • Frans NIR
  • Italiaans Codice Fiscale
  • Spaans NIF/NIE
  • Nederlands BSN
  • Zweeds Personnummer
  • Belgisch Rijksregisternummer
  • Pools PESEL

Financiële identifiers:

  • IBAN (alle EU-varianten)
  • BIC/SWIFT-codes
  • Europese betalingsreferentienummers

Nationale documenten:

  • EU-rijbewijzen (alle 27 lidstaten — elk een andere structuur)
  • Nationale identiteitskaarten (verschillende formaten)
  • Verblijfsvergunningen

Sectorspecifieke EU-identifiers:

  • EORI-nummers (douane)
  • LEI-codes (financiën)
  • BTW-nummers per lidstaat

De 220+-kloof

Wanneer u de EU-specifieke identifiers telt die Presidio mist maar GDPR vereist, zijn dat meer dan 220 entiteitstypen. Elk vereist een aangepaste herkenner met zijn eigen validatielogica.

Aangepaste herkenners bouwen in Presidio:

  1. Schrijf de recognizer-klasse in Python
  2. Definieer het patroon en de validatielogica
  3. Schrijf eenheidstests
  4. Registreer bij de Analyzer
  5. Test op realistisch gegevens
  6. Implementeer naar productie

Per recognizer: 4–8 uur engineering. Voor 220+ recognizers: 880–1.760 uur engineeringtijd.

anonym.legal's EU-dekking

anonym.legal omvat EU-identifierdetectie voor alle 27 EU-lidstaten plus VK, Noorwegen en Zwitserland. Checksumvalidatie is ingebakken voor alle identifiers die dit vereisen. Geen engineering vereist voor EU-implementaties.

Gerelateerde Artikelen

GDPR & Naleving

Japan My Number: Verhoeff & APPI

63% of generic tools fail My Number detection in Japanese documents. My Number uses Verhoeff algorithm — the most complex national ID checksum in Asia.

GDPR & Naleving

HDPA Greece: AFM & AMKA Detection

Greek AFM detected with 52% accuracy by generic tools. HDPA issued 89 decisions in 2024 — up 162% from 2022. Tourism and maritime sectors face distinct.

GDPR & Naleving

NAIH Hungary: TAJ-Szám and Adóazonosító Jel

Hungarian NER accuracy is 67% vs. EU average 82% — NAIH's 2024 assessment. TAJ-szám weighted checksum and adóazonosító jel detection gaps.

Klaar om uw gegevens te beschermen?

Begin met het anonimiseren van PII met 285+ entiteitstypen in 48 talen.

Start Gratis ProefperiodeBekijk Kenmerken

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.