By · Last updated 2026-05-29

Back to BlogGDPR & Compliance

ÚOOÚ Czech: GDPR for Manufacturing

Czech ÚOOÚ issued 58 enforcement decisions in 2024; manufacturing accounts for 34% of violations. 67% of Czech firms use German tools missing Czech.

May 29, 20268 minute read
Czech Republic ÚOOÚrodné číslomanufacturing GDPRCentral Europe complianceCzech identifiers

ÚOOÚ and GDPR in Czech Manufacturing

The Úřad pro ochranu osobních údajů (ÚOOÚ) issued 58 enforcement decisions in 2024. Manufacturing and automotive firms made up 34% of those. That is the highest share of any sector.

Škoda Auto, Toyota, Foxconn, and many tier suppliers all operate in Czechia. GDPR compliance there needs tools that handle local data. Most tools in use do not.

The Parent Company Tool Problem

ÚOOÚ data shows a clear failure pattern. Parent companies abroad push foreign-configured PII tools to their local units.

When a large group deploys its standard tool to a Prague office:

  1. The tool is set up for foreign identifiers. It does not cover local ones.
  2. Employee contracts and HR files are in Czech. The tool was not trained on Czech text.
  3. NER accuracy for Czech is 23% lower than for equivalent text in other languages. (ÚOOÚ technical guidance, 2024)
  4. The rodné číslo is missed in files not marked as Czech.
  5. Employee health and HR data moves without the protection regulators require.

67% of local firms rely on tools that miss country-specific identifiers. ÚOOÚ holds the local controller liable. It does not hold the parent vendor liable.

Rodné Číslo: Special Category Data

The rodné číslo is a birth number. It uses the format RRMMDD/XXXX.

  • Digits 3–4 encode the birth month. For women, 50 is added. A woman born in January shows 51, not 01.
  • A forward slash splits the date from the suffix.
  • The suffix has 3–4 digits with a modulus-11 check digit.

The gender encoding makes this number special category data under GDPR Article 9. It reveals sex by design. Heightened protection applies.

Three things must be covered. First, the women's month offset — the 50 rule. Second, modulus-11 check digit validation. Third, both 9-digit (pre-1954) and 10-digit formats.

Pattern matching alone does not meet the ÚOOÚ standard.

Other Key Identifiers

Číslo občanského průkazu (OP): National ID card. Nine alphanumeric characters. Found on contracts, visitor logs, and health records.

IČO: Eight-digit business number. Appears in supplier contracts next to personal data of legal reps.

DIČ: Format CZ + birth number (individuals) or CZ + IČO (companies). Personal DIČ appears in freelance contracts.

IBAN: Format CZ + 22 digits. Common in payroll files and expense reports.

Where Manufacturing Is Exposed

HR records: Payroll for local staff includes birth numbers, national IDs, and bank details. Cross-border HR transfers need Transfer Impact Assessments.

Quality traceability: Auto production systems often link defect records to individual workers. This is personal data inside operational technology. It is subject to GDPR even outside HR systems.

Dealership data: Large manufacturer networks process test drive records, financing forms, and service histories. Many of these hold birth numbers.

See our GDPR compliance guide and multilingual PII detection overview for how identifier gaps apply across EU jurisdictions. For full entity coverage, see the entities reference.

The core need is simple. Birth number detection must include gender-offset handling and checksum validation. Native NER for text processing is also required. Mixed-language pipelines must be supported.

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.