By · Last updated 2026-05-29

Back to BlogGDPR & Compliance

Datatilsynet: Denmark Healthcare GDPR

Denmark's Datatilsynet issued 31 GDPR decisions in 2024; 14 involved healthcare data systems. CPR-number requires modulus-11 validation that 67% of NLP.

May 29, 20268 minute read
Denmark DatatilsynetCPR numberhealthcare GDPRNordic data protectionhealth data

Denmark Healthcare GDPR: Datatilsynet 2024 Enforcement

Denmark's Datatilsynet issued 31 GDPR cases in 2024. Fourteen of them — 45% — involved medical systems. Denmark has 5.9 million people. That share is very high. It shows how far the country has gone with digital health. It also shows how strict the rules are.

Denmark's Health System

Every Danish person has a CPR number. That number ties to their patient record, the drug registry, the hospital log, and tissue samples at Statens Serum Institut. The hospital log goes back to 1977.

This system makes Danish medical research some of the best in the world. It also means patient files are very sensitive. That is why Datatilsynet has focused so much on this area.

The CPR Number Problem

The CPR number is a 10-digit ID. Its form is DDMMYY-XXXX. The last digit is a check digit. It works by modulus-11 math.

CPR numbers show up in every clinical file. They link to care, tax, bank, and voting records.

Datatilsynet says you must check your de-identification work before you use patient records for any new purpose. But 67% of common NLP tools skip the modulus-11 step for CPR numbers. When they skip it, two things go wrong.

False hits: Date strings, bill numbers, and reference codes get marked as real CPR numbers. This leads to costly manual checks.

Missed IDs: CPR numbers with swapped digits fail the check. So real patient IDs slip past. The output looks clean but is not.

See our EU national ID detection guide for how check-digit rules work for other EU ID types.

Four Rules for Reusing Patient Records

Denmark's medical registries help fund top research. Datatilsynet's 2024 guidance on reuse sets four rules.

Write down what you did: List every field you removed or changed. Note how you rounded or grouped values. A short policy note does not meet this bar.

Show your test results: Prove that your tool found CPR numbers and other Danish IDs. A claim is not proof.

Limit what you take: Do not pull more personal data than your study needs. This rule holds even for pseudonymized sets.

Do a DPIA for AI tools: Any AI tool that processes Danish patient files needs a DPIA. Use Datatilsynet's standard form.

Three Areas of Focus in Copenhagen

Copenhagen's med-tech firms include Leo Pharma, Bavarian Nordic, and many startups. Datatilsynet watches three risk areas.

AI training sets: The authority found firms in 2024 that trained AI models on files with live CPR numbers. None had a valid legal basis.

Transfers abroad: Some firms sent patient files to US cloud vendors for AI work. The authority said SCCs alone are not enough. You also need technical steps — such as encryption with keys held in Europe.

Access logs: Logs must show who read which files and why. Keep them for at least five years.

56% of Danish medical data breaches in 2024 came from poor de-identification. Using CPR-validated tools with Danish-language support cuts out the most common failure.

For more on Nordic enforcement, see our IMY Sweden GDPR anonymization guide.

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.