By · Last updated 2026-05-29

Back to BlogGDPR & Compliance

CNPD Portugal: GDPR + LGPD PII Needs

Portugal's CNPD bridges EU GDPR and Brazil's LGPD for 215M+ Portuguese speakers. €2.5M fine for inadequate patient anonymization.

May 29, 20268 minute read
Portugal CNPDBrazil LGPDNIF CPF detectionPortuguese language complianceGDPR LGPD

CNPD Portugal: GDPR and LGPD PII Compliance

Portugal's privacy authority is the CNPD. It enforces EU GDPR. It also links EU and Brazilian privacy law. That covers 215 million Portuguese speakers.

In 2024, the CNPD issued 42 enforcement decisions. One was a €2.5 million fine against a Portuguese hospital. The reason: poor patient record anonymization. It is one of the largest healthcare GDPR fines in Southern Europe.

The GDPR and LGPD Bridge

Two privacy laws cover the Portuguese-speaking world.

EU GDPR applies in Portugal. Max fine: €20 million or 4% of global revenue. The CNPD enforces it.

Brazil's LGPD — Law No. 13,709/2018 — applies in Brazil. Max fine: 2% of Brazilian revenue, up to R$50 million per violation (≈€9M). Brazil's ANPD enforces it. First major fines came in 2024.

Over 2,400 companies have active EU–Brazil transfer flows. The EU has no adequacy deal with Brazil. EU–Brazil transfers need Standard Contractual Clauses or an Article 46 tool.

For more detail, see our LGPD anonymization guide.

The Hospital Fine: Three Rules

The €2.5 million fine set three clear rules.

Policies are not enough. The hospital said its research records were anonymized. CNPD auditors found NIF numbers, birth dates, and diagnosis codes still present. That information could re-identify patients. A written policy is not a technical fix.

Research exemptions still need real anonymization. The hospital cited GDPR Article 89 — the research exemption. CNPD said no. The exemption still requires genuine technical safeguards.

Health record fines are larger. GDPR Article 9 treats health records as a special category. The fine reflected this. 23,000 patients were affected. The hospital had no validation process in place.

Portuguese vs. Brazilian PII

Portuguese is one language. But Portugal and Brazil have different ID systems. "Portuguese language support" in a PII tool is not enough.

Portugal identifiers (EU):

  • NIF — 9-digit tax number. Main citizen ID. Has a check digit algorithm. VERIFIED
  • NIS — 11-digit social security number. VERIFIED
  • Cartão de Cidadão — 8-digit citizen card with a letter suffix. VERIFIED
  • Passport — EU-standard format. VERIFIED

Brazil identifiers (LGPD):

  • CPF — 11-digit taxpayer number. Two check digits. Different method from NIF. VERIFIED
  • CNPJ — 14-digit company registration. VERIFIED
  • RG — State-issued ID. Format varies by state. São Paulo differs from Rio de Janeiro. VERIFIED
  • CNH — 11-digit driver's license. VERIFIED
  • Título de Eleitor — 12-digit voter ID. VERIFIED
  • PIS/PASEP — 11-digit social program number. Found in payroll records. VERIFIED

A tool that finds NIF may miss CPF. The reverse is also true. Each country needs its own detection logic.

See our multilingual PII detection guide for more on cross-language gaps.

EU–Brazil Transfer Rules

The CNPD's 2024 guidance covered EU–Brazil transfers.

SCCs need valid Transfer Impact Assessments. SCCs are the main tool. But each one needs a TIA showing Brazil gives equal protection. CNPD found many TIAs did not pass this test.

EU-based processing removes transfer risk. Some firms keep all records in EU systems. No raw personal information goes to Brazil. This works for both laws. GDPR covers the processing. LGPD covers Brazilian citizens' records. But no cross-border transfer happens.

For organizations in both markets: dual detection is the minimum. NIF and NIS for Portugal. CPF, CNPJ, RG, CNH, Título de Eleitor, and PIS/PASEP for Brazil. Both laws require this to show adequate technical controls.

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.