By · Last updated 2026-05-29

Back to BlogGDPR & Compliance

UODO Poland: PESEL, NIP & RODO

UODO found 89% of deployed tools fail to detect Polish PESEL correctly. Poland processes 2.3M EU customer records daily. PESEL checksum validation, NIP.

May 29, 20267 minute read
Poland UODOPESEL validationPolish RODO complianceNIP REGON detectionBPO GDPR

UODO Poland: PESEL, NIP & RODO Compliance

Updated for 2026

What Is UODO?

UODO is Poland's data protection authority. Its full name is Urząd Ochrony Danych Osobowych. It enforces RODO — the Polish name for GDPR.

In 2024, the authority ran an enforcement survey. The finding was stark. 89% of PII tools used by organizations in Poland fail to detect PESEL correctly.

Poland is a major BPO hub. It processes 2.3 million EU customer records each day. That gap creates real risk. It affects the authority's jurisdiction. It also affects every EU DPA whose citizens' data Polish-based firms handle. See our GDPR compliance guide for broader context.

PESEL: The Technical Standard

PESEL stands for Powszechny Elektroniczny System Ewidencji Ludności. It is an 11-digit national ID number. It encodes five data fields:

  • Digits 1–2: Last two digits of birth year
  • Digits 3–4: Birth period code (see below)
  • Digits 5–6: Birth day
  • Digits 7–10: Sequential serial (odd = male, even = female)
  • Digit 11: Check digit

The check digit uses a weighted sum. Multiply the first ten digits by weights (1, 3, 7, 9, 1, 3, 7, 9, 1, 3). Sum the products. Take modulo 10. A result of zero means the check digit is correct. A non-zero result means the number is invalid.

The Birth Period Code Problem

Digits 3–4 encode both the birth period and the century. The authority requires support for all five ranges:

CenturyCode range
1800s81–92
1900s01–12
2000s21–32
2100s41–52
2200s61–72

Most tools only handle the 1900s range. They miss anyone born after 1999. Codes 21–32 replace 01–12 for post-1999 births. This affects the most digitally active age group. The full five-range check is a core compliance requirement.

NIP and REGON: Business Identifiers

NIP (Numer Identyfikacji Podatkowej) is a 10-digit tax ID. It appears on invoices, contracts, and payroll records. Multiply the first nine digits by weights (6, 5, 7, 2, 3, 4, 5, 6, 7). Take modulo 11. That gives the check digit.

NIP comes in two forms: personal (NIP osoby fizycznej) and business (NIP podmiotu).

REGON is an enterprise statistical number. It comes in 9-digit and 14-digit variants. Each uses its own check algorithm. REGON appears in contracts and supplier documents.

HR records often contain PESEL alongside NIP and REGON. Full compliance requires detecting all three types. See our security and compliance page for technical safeguard details.

The BPO Multi-Jurisdiction Exposure

BPO firms in Poland process data for Western European clients:

  • German bank customers' records handled in Warsaw
  • French insurance claims processed in Kraków
  • UK healthcare data managed by back-office teams in Wrocław

A detection failure creates simultaneous exposure to four regulators:

  1. UODO — for inadequate measures affecting Polish data subjects
  2. BfDI / Landesdatenschutzbehörden — for German nationals' data
  3. CNIL — for French nationals' data
  4. ICO — for UK nationals' data

Cross-border compliance demands tools that cover the full EU identifier set. PESEL, NIP, and REGON are the local baseline. German Steuer-ID, French NIR, and Dutch BSN are also needed when those records are in scope. Each national ID has its own format and check logic. Tools that miss one create gaps. See our multilingual PII detection guide for EU entity coverage across all member states.

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.