anonym.legal
Terug naar BlogGDPR & Naleving

Multi-framework privacy met één tool

Complianceteams die GDPR, HIPAA en CCPA beheren, moeten verschillende anonimiseringsnormen toepassen afhankelijk van de documentcontext.

June 6, 20267 min lezen
GDPR HIPAA CCPAmulti-framework complianceprivacy regulationcompliance presetsDPO tools

Eén tool, drie frameworks

Een privacyteam verwerkt EU-klantbestanden onder GDPR op maandag. Zorgdossiers onder HIPAA op dinsdag. Californische consumentendata onder CCPA op woensdag.

Elke wet heeft andere regels. Elk document vereist een andere setup.

Elke dag wisselen tussen drie regelsets creëert fouten. De verkeerde setup op het verkeerde bestand veroorzaakt een compliancefout of gegevensverlies.

Genoemde nalevingsprofielen lossen dit op. Één opgeslagen setup per wet. Geen handmatige herconfiguratie.

GDPR: wat het vereist

GDPR Artikel 4 definieert persoonsgegevens breed. De entiteitsset voor GDPR-naleving:

  • Namen, e-mailadressen, telefoonnummers
  • Fysieke adressen
  • Nationale identifiers (BSN, Steuer-ID, NIR, enz.)
  • IP-adressen
  • Geboortedatums
  • Biometrische gegevens
  • Locatiegegevens
  • Financiële identifiers (IBAN, creditcardnummers)

Methode: Replace — vervangt door een type-aanduider zoals [NAAM] of [EMAIL].

HIPAA Safe Harbor: wat het vereist

HIPAA's 18 Safe Harbor-categorieën omvatten alles van GDPR plus:

  • Medische dossiernummers (ziekenhuisspecifiek formaat)
  • Gezondheidsplannummers
  • Certificaat-/licentienummers
  • Voertuigidentifiers
  • Apparaatidentifiers
  • Geografische gegevens kleiner dan een staat

Methode: Redact — volledig zwartmaken voor medische documentproductie.

CCPA/CPRA: wat het vereist

CCPA/CPRA definieert "persoonsgegevens" soortgelijk aan GDPR maar voegt specifieke categorieën toe:

  • Biometrische informatie
  • Browsegeschiedenis
  • Aankoopgeschieden
  • Geolocatiegegevens
  • Gevolgtrekkingen over voorkeuren en kenmerken

Voor documentverwerking: dezelfde entiteitsset als GDPR plus California-specifieke financiële identifiers.

Presetworkflow

Opgeslagen presets in anonym.legal:

  • Preset 1: "GDPR-Standaard"
  • Preset 2: "HIPAA-Safe-Harbor"
  • Preset 3: "CCPA-California"

Elke preset is één keer geconfigureerd door de DPO. Teamleden selecteren de preset op basis van het documenttype. Geen handmatige configuratie per sessie.

Auditlogboeken registreren welke preset werd gebruikt voor elk document. Dit bewijst consistente toepassing van het juiste framework per documenttype.

Limitations / When this doesn't apply

The wrong-profile error survives the redesign. Named profiles remove manual setup mistakes, not the choice of which profile to apply. A HIPAA record run under the GDPR profile still misses the year-only date rule and sub-state geography Safe Harbor demands; an EU file run under CCPA picks up the wrong scope. The article's own numbers confirm it — the residual error rate comes from picking the wrong profile, and mixed-jurisdiction documents still need a human to decide which framework governs.

Each framework's bar is a legal standard, not a profile output. GDPR has no fixed identifier list, so its profile is a reasonable default rather than a guarantee of adequate anonymization; HIPAA Safe Harbor still requires no actual knowledge of re-identifiability even after all 18 categories are handled. Applying the right profile produces a defensible record; it does not by itself satisfy the law. And detection accuracy bounds every profile equally — free-text identifiers, custom MRN formats, and scattered quasi-identifiers are caught less reliably than structured data, so a perfectly chosen profile can still leave residual identifiers and produce pseudonymized rather than anonymous output. Review profile coverage on a schedule and test against real samples.

Gerelateerde Artikelen

GDPR & Naleving

Self-Hosted PII Fails Compliance Audits

spaCy 3.4.4 produces different NER results than spaCy 3.5.1. Financial services firm discovers 3% of documents were differently anonymized in staging vs.

GDPR & Naleving

Presidio Misses 220+ GDPR Entities

Presidio ships with ~40 default entity recognizers focused on US identifiers. European organizations need IBAN, Codice Fiscale.

GDPR & Naleving

Configuration Drift: A Hidden GDPR Risk

Analyst A replaces names with pseudonyms. Analyst B blacks them out. Your GDPR audit finds both in the same dataset. Configuration drift — where team.

Klaar om uw gegevens te beschermen?

Begin met het anonimiseren van PII met 267+ 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, held by our hosting provider.
  • 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 company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds 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

Automated checks run on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We test detection against sample documents before each release.

A failing unit or integration run stops the release.

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.

Paid plans can buy top-up credits.

Credits reset at the end of each cycle.

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.