GDPR and other data laws, clearly and step by step

What the law requires, when to start, which law applies in which country and what it costs. For developers and small products. Checked against sources on 17 November 2026.

datastated in a sourceinferencefollows from the sources, not stated outright

Overview

You can’t “get” compliance. It is a state you must be able to prove at any moment

There is no license, registration or mandatory certificate. You pay for four things to exist and to match reality.

Legal basisfor every purpose of processing
Documentsrecords, privacy policy, DPAs; a DPIA when risk is high
Rightsaccess, erasure, export within a month
Securityand a 72-hour plan for a breach

When GDPR starts to apply to you

If you have an establishment in the EU, deliberately offer goods or services to people in the EU, or monitor their behavior there (Art. 3). Then one customer is enough. A chance visitor from the EU does not bring you in, as long as you neither target the EU nor track people there. There is no exemption for small companies. data

When it becomes urgent inference

  • your first B2B customer in the EU sends a DPA and a security questionnaire;
  • pixels and analytics on EU traffic;
  • special-category data or children’s data;
  • your first breach.

Stage by stage

The “GDPR compliant” badge

Your own badgeThere is not and never was an official EU logo. A home-made badge has no legal weight. data
“Certified” without a certificateMisleading: in Luxembourg, a “CNPD certified” label without a valid GDPR-CARPA certificate is treated as exactly that. data
Certificate under Art. 42Europrivacy and others: voluntary, only through an accredited body, covers the listed operations rather than the whole company. EDPB: a certificate does not mean full compliance. data
What actually worksA DPA, a list of subprocessors and a description of security measures: that is what a customer will ask for. inference

ComplyJet, Luxgap, Croatian DPA, Clym on the EDPB

Data: the regime depends on the category

Ordinary data (name, email, IP) needs a legal basis, a clear policy and a retention period. Health, mental state and intimate life usually need explicit consent given as a separate action, and a DPIA; below the age of digital consent, children need a parent’s consent. The most common trap is data from which something sensitive can be inferred: it gets the same strict regime. data

All categories and an example breakdown

When to start

  1. Prototype for yourself — plan the architecture, the law is nearly silent
  2. Closed beta — an honest text, consent, deletion
  3. Public launch — a full policy, DPAs, a breach plan
  4. Money and B2B — contracts, a DPA template, security measures
All stages in detail

Laws by country

  • 30EU and EEA countries run on GDPR
  • 11have their own law and an EU adequacy decision
  • 110have their own general data law
Open the map

Money and risk

  • from €490a year: EU representative
  • from €33a month: external DPO
  • €2,500fine for a private person who emailed a group with every address visible
Costs, checks and fines

Check your product

Three open skills for AI agents run your code through this logic: they find personal data down to the file and line and propose fixes.

Skills for AI agents

Next: Data

Data

Data categories and what each one needs

The regime depends on what exactly you process, and one app almost always handles several categories at once. The square next to the risk level shows it in color. Fines have two tiers: up to €20 million or 4% of worldwide turnover, whichever is higher, and up to €10 million or 2% (Art. 83). data

Ordinary personal data Art. 4(1), 6

medium risk

Name, email, IP, device ID, cookie ID, activity history.

What you need
One of 6 legal bases per purpose, a privacy policy, a retention period, DPAs with contractors, user rights.
Cost of a mistake
up to 4%legal bases and principles; up to 2%security and documentation.

Special categories Art. 9

high risk

Health, including mental health; sex life and orientation; biometrics for identification; genetics; ethnic origin; religion; politics; trade union membership.

What you need
A basis from Art. 6 plus an exception from Art. 9(2), for apps usually explicit consent given as a separate action. DPIA, encryption, no third-party trackers nearby.
Cost of a mistake
up to 4%a breach is almost always “high risk”: notify the people themselves.

Indirectly sensitive EU Court of Justice case law

high risk

Data from which something sensitive can be inferred: a partner’s name (OT case, 2022), a medicine order (Lindenapotheke, 2024).

What you need
The same regime as Art. 9. Intent and accuracy of the inference do not matter. data
Cost of a mistake
up to 4%the most common trap: assuming that if you never ask about health directly, there are no special categories. inference

Children’s data Art. 8

elevated risk

Users below the age of digital consent: 16 by default, countries lower it to 13. For example: Germany, Ireland, the Netherlands 16; France 15; Austria, Spain, Italy 14; Belgium, Denmark 13.

What you need
If you rely on consent: a parent’s consent and a reasonable check. Text children can understand, privacy by default.
Cost of a mistake
up to 2%under Art. 8; in practice fined together with breaches of principles, and then up to 4% (TikTok, Instagram).

Profiling Art. 4(4), 21, 22

elevated risk

Automated evaluation of personality, behavior, preferences: scoring, types, predictions.

What you need
Explain the logic in the privacy policy, give a right to object. A decision with significant effects and no human involved is allowed only under a contract, law or explicit consent. In Switzerland “high-risk profiling” requires express consent.
Cost of a mistake
up to 4%data-subject rights are in the upper tier.

Pseudonymous and anonymous Art. 4(5), recital 26

lower risk

Pseudonymous: the key is kept separately, e.g. a hashed email. Anonymous: no reasonable means can single the person out.

What you need
Pseudonymous data remains personal data, just with less risk. Anonymous data falls outside GDPR entirely, but small samples are easy to re-identify.
Cost of a mistake
as for the source dataif “anonymous” data turns out to be re-identifiable.

One more category people rarely think of: data on criminal convictions and offences (Art. 10). A private business may process it only where the law expressly allows.

Baker McKenzie on the OT, Meta and Lindenapotheke cases, recital 35, age of consent by country, nFADP Art. 6, GDPR text

Example breakdown: a psychological test app for two

Data logic: a person answers questions about closeness, anxiety, avoidance and attraction; gets a profile on several scales; can invite a second person, and they see a joint result. The operator is in Switzerland, users in Switzerland and the EU, so nFADP and GDPR both apply. The classification below is an inference from the law and EU Court case law. inference

What dataAnswers about anxiety, distress, avoidanceemotional-state scales
Categoryspecial: health
What you needExplicit consent as a separate action before the first question (GDPR Art. 9(2)(a); in Switzerland Art. 6(7)). DPIA. Only the questions you need.
If you get it wrongThe top fine tier, complaints, compensation claims.
What dataAnswers about physical intimacy and attraction
Categoryspecial: sex life
What you needThe same explicit consent. A way to skip a question without breaking the result.
If you get it wrongDisclosure to the partner or third parties is a high-risk breach: notify the regulator and the people themselves.
What dataComputed profiletype, scale scores, prediction
Categoryprofilinginferred special
What you needExplain in plain words in the privacy policy how the result is calculated. In Switzerland this is probably “high-risk profiling”: an assessment of essential aspects of personality, so again express consent.
If you get it wrongThe profile is more sensitive than the answers themselves: in a breach it is the main harm.
What dataJoint result for two
Categoryspecial, data of two people
What you needConsent from each. One person’s answers are not visible to the other without consent. If one deletes their data, their part disappears from the joint result, not just their access.
If you get it wrongThe second person is a separate data subject with a right to complain and sue. Compensation for non-material damage needs no seriousness threshold (EU Court, C-300/21). data
What dataAnswers about a person who didn’t take the test
Categoryusually not personal data for the operator
What you needDon’t store the partner’s name, contacts or photo. As long as the operator cannot identify them, it is not their personal data.
If you get it wrongA “partner’s name” field turns them into a data subject you must inform under Art. 14.
What dataDevice ID, invite link, IP during sync
Categoryordinary
What you needBasis: “contract”. Short lifetimes for links and transfer sessions. US hosting: provider’s DPF certification or SCCs.
If you get it wrongA guessed link opens someone else’s result: that is already a breach of special-category data.
What dataUser’s age
Categorychildren
What you needThe topic will attract teenagers. Explicit consent to special categories from a minor is doubtful, so set a 16+ or 18+ threshold with age confirmation.
If you get it wrongChildren plus special categories is the combination regulators fine most readily.
What lowers risk the most. Keep answers on the device only and don’t send to the server what the joint result doesn’t need. What the operator doesn’t have, it can’t lose.
What’s almost free. A consent screen before the test, a clear privacy policy with the operator’s contact, a “delete for both” button, no analytics on question screens.
A Swiss nuance. For wilful failure to inform, nFADP fines the responsible individual personally, up to CHF 250,000. A company only in exceptional cases.

Next: When to start

When to start

What the law asks at each product stage

The law has no threshold by number of people: duties start with the first person who isn’t you. data But what a regulator would actually check, and what is cheaper to do right away, depends a lot on the stage. Find your row; sensitive data and money add requirements at any stage. inference

  1. Prototype for yourself

    only your own or made-up data

    Already requiredAlmost nothing by law: personal data for purely personal purposes is outside GDPR (Art. 2(2)(c)). data
    Do it now while it’s cheapDecide the architecture: what never leaves the device, what is encrypted before sending, which storage region, no third-party analytics. This is the most expensive thing to redo later. inference
    Next step whenthe first other person appears, even a friend.
  2. Closed beta with people you know

    up to a few dozen people, invite only

    Already requiredA short honest text: who you are, what you collect, why, where it is stored, how to delete it. Deletion on request. If questions touch health, intimacy or children, explicit consent with a separate checkbox. No secrets in the repository.
    Can waitAn EU representative, the full document set, a lawyer. Formally, records of processing are already required with special categories; a short one takes an hour. A complaint from people you know is unlikely, but the harm from a breach is the same. inference
    Next step whenstrangers or a public link appear.
  3. Open beta or free launch

    anyone can sign up

    Already requiredA full policy: operator and contact, purposes, bases, recipients and countries, retention, rights, where to complain. DPAs with hosting and services. A consent banner if there are optional cookies or analytics. A breach plan and an incident log. Deletion and export.
    If you are outside the EU and users are in the EUA representative under Art. 27 unless the exemption fits (see below). For special categories, a DPIA before launch.
    Next step whenyou start charging money or working with companies.
  4. Sensitive data, at any stage

    health, mental state, intimacy, children, biometrics

    From the first userExplicit consent (GDPR Art. 9(2)(a), nFADP Art. 6(7)), only the questions you need, an age threshold of 16+ or 18+, no data to analytics or AI services without separate consent.
    Before public launchA DPIA (Art. 35) and records of processing. A breach of such data is almost always “high risk”: notify both the regulator and the people.
    What lowers risk the mostdon’t store the answers on a server, or store only ciphertext you hold no key to. inference
  5. Paid product

    subscriptions, purchases

    AddsTerms of use and a contract, the payment provider as a separate recipient of data, keeping payment records for the tax period. In Switzerland, selling online needs an Impressum: name, postal address and email (UWG art. 3(1)(s)). data
    Next step whenyour first business customer signs up.
  6. Business customers (B2B)

    you sell to companies

    AddsThe customer will send a DPA and a security questionnaire. You need your own DPA template, a list of subprocessors with regions and a description of security measures. Without them the deal stalls. inference
  7. Growth or incident

    thousands of users, first breach

    AddsA DPO if your core activity is large-scale processing of special categories or systematic monitoring (Art. 37). Regular review, an external audit. After a breach, 72 hours to notify under GDPR. data

Example: the couples test app from the breakdown below, in a closed beta, matches the “closed beta” and “sensitive data” rows together. Consent, deletion and an honest text are needed now; an EU representative once the app is offered to people in the EU. inference

Next: Laws by country

Laws by country

Coverage map: where GDPR applies and where another law does

Click a country: first a short note on how it differs from GDPR, then “More” for detail. Small countries are shown as dots; any country can be picked from the list. Clicking a legend item highlights that group. Detailed notes exist for the EU and 29 key countries; for the rest, the name of the law and a link to check the differences.

Loading the map…

All detailed notes as a list

EU and EEA (GDPR)

The baseline model: six legal bases, special categories under Art. 9, breach notice within 72 hours, fines up to 4% of worldwide turnover baseline 2026-11-17

  • Applies to companies in the EU and to anyone targeting or monitoring people in the EU (Art. 3).
  • A company outside the EU appoints a representative under Art. 27 unless a narrow exemption fits.
  • Age of digital consent 16, countries lower it to 13–15.
  • National add-ons: separate laws on cookies (ePrivacy), employee data, age of consent.
  • Transfers out of the EEA: adequacy decision, SCCs with a risk assessment, BCRs.
  • From 2.04.2027 cross-border cases get binding deadlines (Regulation 2025/2518).

Switzerland

Like GDPR, but processing is lawful even without a legal basis if the principles are respected. Fines up to CHF 250,000 on the responsible individual baseline 2026-11-17

  • Sensitive data is wider: adds the intimate sphere and social assistance measures.
  • “High-risk profiling” and sensitive data based on consent need express consent (Art. 6(7)).
  • Breach: FDPIC “as soon as possible” when high risk is likely, no hour count.
  • Cookies: an opt-out model (Art. 45c Telecommunications Act), but EEA users get the EU standard.
  • The EU recognises Switzerland as adequate; to the US via the Swiss-US DPF.
  • Criminal fines under Art. 60–62 are prosecuted on complaint, under Art. 63 ex officio.

United Kingdom

UK GDPR plus the Data (Use and Access) Act changes from 2026: “recognised legitimate interests”, looser rules on automated decisions. EU adequacy renewed to 27.12.2031 baseline 2026-11-17

  • Age of digital consent 13.
  • A company outside the UK appoints a UK representative.
  • PECR fines (cookies, marketing) raised to UK GDPR level.
  • Since 5.02.2026 cookies used only for statistics or for appearance settings need no consent; the conditions are narrow data.
  • Transfers from the UK: IDTA or the UK Addendum to SCCs; to the US via the UK Extension to the DPF.
  • Regulator: ICO.

United States

No general federal law. About 20 state laws on an opt-out model plus sectoral ones: HIPAA, COPPA, GLBA baseline 2026-11-17

  • California (CCPA/CPRA): revenue threshold about USD 26.6M, or 100,000+ residents, or 50%+ of revenue from selling data.
  • A “Do Not Sell or Share” link and honouring the Global Privacy Control signal.
  • Several states require opt-in for sensitive data.
  • Fines are per violation, not a percentage of turnover; in California USD 2,663 / 7,988.
  • The FTC punishes deception in privacy policies (Section 5 FTC Act).
  • For the EU only companies certified under the Data Privacy Framework are adequate.

Brazil

LGPD is very close to GDPR: 10 legal bases, a mandatory DPO (encarregado), regulator ANPD baseline 2026-11-17

  • Breach: notify ANPD within 3 business days.
  • Fine up to 2% of revenue in Brazil, capped at BRL 50M per violation.
  • Legitimate interest exists, with stricter documentation requirements.
  • Transfers abroad: ANPD standard contractual clauses (2024).
  • EU adequacy decision of 26.01.2026: data from the EU flows without SCCs; Brazil recognises the EU in return. data
  • Children's data is processed “in their best interests”.

China

PIPL: no legitimate interest, separate consent for sensitive data and for transfers abroad, localisation for some operators baseline 2026-11-17

  • Data export: CAC security assessment, standard contract or certification.
  • Fines up to CNY 50M or 5% of revenue, plus personal fines for managers.
  • Data of children under 14 is sensitive.
  • An impact assessment is mandatory before sensitive processing and export.
  • A foreign company targeting people in China appoints a representative.

India

DPDP 2023: consent plus a narrow list of “legitimate uses”, no legitimate interest. Parental consent for everyone under 18 baseline 2026-11-17

  • Rules adopted 13.11.2025; consent managers from 13.11.2026; main duties from 13.05.2027.
  • No separate sensitive category: the same protection for all data.
  • A breach is notified to the Data Protection Board and to the people themselves.
  • Fines up to INR 250 crore (about 2.5 billion rupees) per violation.
  • Transfers abroad allowed everywhere except countries on a government blacklist.

Japan

APPI. Mutual adequacy with the EU, with supplementary rules for data received from the EU baseline 2026-11-17

  • Regulator: Personal Information Protection Commission (PPC).
  • Disclosure to third parties by consent or under a registered opt-out regime.
  • “Special care-required” data: the equivalent of sensitive data.
  • Breach reporting mandatory since 2022.
  • Transfers abroad: consent with information about the country, or an equivalent protection system at the recipient.

South Korea

PIPA is one of the strictest laws, with a strong focus on consent. EU adequacy since 2021 baseline 2026-11-17

  • Regulator: PIPC.
  • Fines up to 3% of total revenue (2023 amendments) data.
  • Right to an explanation and to refuse automated decisions (since 2024).
  • Consent must be split by purpose more strictly than under GDPR.

Canada

PIPEDA for the private sector; Quebec's Law 25 is stricter and closer to GDPR. EU adequacy for commercial activity only baseline 2026-11-17

  • Built on “meaningful consent”.
  • Breaches are reported when there is a “real risk of significant harm”.
  • In Quebec: impact assessments, fines up to CAD 25M or 4% of turnover.
  • Federal reform: C-27 died; the new Bill C-36 was tabled in June 2026 and is still at second reading data.
  • Alberta and British Columbia have their own private-sector laws.

Australia

Privacy Act 1988 and 13 APPs. Small businesses with turnover up to AUD 3M are largely exempt. No EU adequacy baseline 2026-11-17

  • Mandatory breach notification (NDB) to the OAIC and to people.
  • 2024 amendments: a tort for serious invasions of privacy, tiered penalties data.
  • Maximum penalty AUD 50M, 30% of turnover or three times the benefit.
  • The second reform tranche was published as a draft on 31.08.2026 data.

Russia

152-FZ. Russian citizens’ data must first be recorded on servers in Russia. The operator must notify Roskomnadzor before processing starts baseline 2026-11-17

  • Cross-border transfers must be notified in advance, to some countries only with Roskomnadzor permission.
  • Since 30.05.2025 a repeat leak brings a turnover fine of 1–3% of revenue data.
  • Consent to sensitive data in writing.
  • No EU adequacy; transfers from the EU need SCCs with a risk assessment that is hard in practice inference.

Ukraine

A 2010 law. Bill No. 8153, close to GDPR, passed first reading on 20.11.2024 and is being prepared for the second baseline 2026-11-17

  • Oversight currently sits with the Human Rights Commissioner.
  • Under the EU roadmap a National Commission for data protection should appear by the end of 2026.
  • No EU adequacy; transfers from the EU to a Ukrainian team need SCCs with a risk assessment.

Türkiye

KVKK follows the old EU Directive. A 2024 reform of transfers introduced SCCs and BCRs baseline 2026-11-17

  • VERBIS controller registry (with thresholds).
  • Standard transfer contracts are notified to the regulator within 5 business days data.
  • “Explicit consent” is read more strictly than under GDPR.
  • No EU adequacy.

South Africa

POPIA: 8 conditions for lawful processing, regulator: Information Regulator baseline 2026-11-17

  • An information officer must be registered.
  • Breach: notify the regulator and people “as soon as reasonably possible”.
  • Some processing needs prior authorisation.
  • Fine up to ZAR 10M; prison is possible for some offences.

Singapore

PDPA: consent plus exceptions, legitimate interest since 2021. Breach notification mandatory baseline 2026-11-17

  • Regulator: PDPC.
  • Fine up to 10% of Singapore turnover or SGD 1M.
  • A DPO is mandatory.
  • A separate Do Not Call registry for marketing.

United Arab Emirates

Federal PDPL 2021. The DIFC and ADGM free zones have their own GDPR-style laws baseline 2026-11-17

  • The federal law’s executive regulations, which make its fines and procedures operative, are still not issued in 2026 data.
  • DIFC and ADGM have their own regulators and adequacy lists.
  • No EU adequacy.

Saudi Arabia

PDPL in force since 2023, penalties since September 2024. Strict rules on transfers abroad baseline 2026-11-17

  • Regulator: SDAIA.
  • Registration on the SDAIA platform is required for sensitive data or when processing is the core activity data.
  • Transfers abroad under the 2023 rules with a risk assessment.

Israel

Privacy Protection Law. EU adequacy. Amendment 13 (in force since 14.08.2025) widened the regulator’s powers and fines baseline 2026-11-17

  • Regulator: Privacy Protection Authority.
  • Database registration is now mostly needed only above 100,000 people data.

New Zealand

Privacy Act 2020, 13 information privacy principles. EU adequacy baseline 2026-11-17

  • Mandatory notification of serious breaches.
  • Low fines (up to NZD 10,000) data.
  • Limits on transfers abroad (IPP 12).

Argentina

Law 25.326 (2000). EU adequacy since 2003. A GDPR-style reform is under discussion baseline 2026-11-17

  • Regulator: AAIP.
  • Databases are registered.
  • Argentina has ratified Convention 108+.

Uruguay

Law 18.331. EU adequacy since 2012 baseline 2026-11-17

  • Regulator: URCDP.
  • Breach notification mandatory since 2020 (Decree 64/020), within 72 hours data.

Mexico

A new federal law in force since 21.03.2025 replaced the 2010 law; the INAI regulator was abolished and its role passed to the Anti-Corruption and Good Government Secretariat data

  • A consent model with a privacy notice (aviso de privacidad).
  • No EU adequacy.

Nigeria

NDPA 2023 and the NDPC regulator. Controllers “of major importance” register and pay fees baseline 2026-11-17

  • GAID 2025: detailed implementing rules, in effect since 19.09.2025 data.
  • Fine up to 2% of annual revenue or NGN 10M.

Kazakhstan

A 2013 law with localisation: databases with citizens’ data are kept in Kazakhstan baseline 2026-11-17

  • Breaches are notified to the competent authority.
  • No EU adequacy.

Indonesia

Data protection law 27/2022 fully in force since October 2024. Implementing rules (PP 33/2026) take effect 16.01.2027; the supervisory agency is not set up yet data

  • A GDPR-like model: legal bases, rights, DPO.
  • Fines up to 2% of annual revenue.

Thailand

PDPA 2019, fully in force since June 2022, regulator PDPC. A GDPR-like model baseline 2026-11-17

  • Breach notification within 72 hours.
  • Transfers abroad under 2023 rules (BCRs, SCCs).

Vietnam

Personal Data Protection Law 91/2025 in force since 1.01.2026, replacing Decree 13/2023 data

  • Impact assessments for processing and transfers abroad are filed with the Ministry of Public Security.
  • Fines up to 5% of revenue for unlawful transfers data.

Chile

New law 21.719 (2024) on the GDPR model with a new data protection agency. By law it takes effect 1.12.2026; parliament is considering a delay to 15.10.2027 data

  • Fines will be revenue-based.
  • No EU adequacy.

Classification: the World Privacy Forum table as of June 2024, as republished by Captain Compliance; EU adequacy decisions: European Commission; Brazil’s new adequacy decision, corrections for Chile, Vietnam, Mexico and 13 more countries and territories where a law was adopted or found, and the country notes were checked against sources on 17.11.2026. Map data in machine-readable form: laws.json. Territories the base map draws separately, such as Greenland, Puerto Rico or New Caledonia, show the law that applies there.

If your team or company is outside the EU

Check whether the country has an EU adequacy decision. If it does (Switzerland, the UK, Japan and others), data flows as within the EU. If not, you need an Art. 46 tool, usually SCCs and a transfer impact assessment (TIA). data

Contractor or your own product. A processor for an EU customer pays mainly for a DPA, SCCs and security. Your own product for people in the EU adds a representative under Art. 27 and the full controller set. inference

Specifics for each country, including transfers to a team there, are on the map.

list of adequacy decisions

EU representative under Art. 27: what it is, when you need one, what it costs

What it is

A person or company in an EU country that an operator outside the EU appoints in writing as its contact for regulators and people (Art. 4(17), 27). The representative sits in a country where your users are (Art. 27(3)). data

They receive requests and letters, show the records of processing (Art. 30) when a regulator asks, and pass everything on to you. Your obligations and liability for the data do not move to them (Art. 27(5)). data

When you need one

If you have no establishment in the EU and GDPR applies to you through Art. 3(2): you offer services to people in the EU or monitor their behavior. data

Not needed only if processing is at the same time occasional, excludes large-scale processing of special categories or criminal data, and is unlikely to create risk (Art. 27(2)). A service built on sensitive answers usually does not fit this exemption. inference

Swiss law requires a representative only from foreign operators (nFADP Art. 14), so a Swiss operator does not need one for users in Switzerland. data

What it costs and what happens without one

Public prices as of November 2026: the cheapest €490–600 a year, mid-range €1,000–2,500, top tiers up to about €4,750. data

An acquaintance in the EU can also be your representative, but regulators’ letters and people’s claims will go to them. inference

The first fine specifically for having no representative: €525,000, the Netherlands, 2021 (Locatefamily.com), plus €20,000 for every two weeks of delay, capped at €120,000. data

Prices from the public price lists of six providers as of 17.11.2026, without recommending specific companies. Dutch DPA on the Locatefamily.com fine, GDPR text, nFADP

Next: Money and risk

Money and risk

Cost per year, € data

Prices from companies that sell these services themselves. The “all together” estimates are a vendor’s, with no published method. Logarithmic scale.

External DPO, up to 20 employees€33–150 a month
400–1,800
External DPO, 20–50 employees€125–350 a month
1,500–4,200
External DPO, 50–250 employees€350–900 a month
4,200–10,800
EU representative, Art. 27from €490 a year to top tiers
490–4,750
All together, 10 employeessoftware, DPO, consultants, team hours
5,000–15,000
Of which your own team’s hourswith 10 employees
3,000–10,000
All together, 50 employees
15,000–40,000
€800–2,000a consultant’s day
€1,500–5,000one-off initial audit, 10–250 employees
from $11,500a year for a SOC 2 audit at one provider, if a customer demands it

Kertos, 6.10.2026, DPO Consulting, Prighter prices, Legiscope, 8.07.2026, G2

What a mistake leads to, besides a fine data

Corrective orderThe regulator can ban processing, order data deleted, stop a transfer (Art. 58(2)).
Claim by a personCompensation for non-material damage without a seriousness threshold; the damage must still be proven (C-300/21, 2023).
Claim by a competitorEU countries may let competitors sue over GDPR breaches as unfair competition (C-21/23, 2024). Germany already does.
Lost dealsA corporate customer won’t sign without a DPA and answers on security. inference

Jones Day on C-300/21, EU Court on C-21/23, BGH 2025

How checks work

Nobody checks in advance. A regulator learns about you in one of three ways. data

A person’s complaintArt. 77, free, to the regulator where they live, work or where the breach happened. They don’t need to prove the breach first.
Your own breach noticeKnuddels reported a hack itself; the investigation found passwords stored in plain text.
The regulator’s own initiativeCoordinated EDPB actions; the 2026 topic is transparency and information.
  1. Requesta letter with questions
  2. Responsedocuments and explanations
  3. Decisionorder, reprimand or fine
  4. Courtappeal against the decision
In parallel: a person can sue the company straight away (Art. 79, 82) without waiting for the regulator. If the regulator says nothing about a complaint for 3 months, you can sue the regulator itself (Art. 78). NGOs like noyb file complaints on people’s behalf (Art. 80).

From 2 April 2027 cross-border cases get binding deadlines (Regulation 2025/2518).

Art. 77, Art. 78–80, Knuddels, CMS, Matheson

Modest fines data

€4,800Austria, 2018. A betting shop filmed the pavement and car park and put up no CCTV sign.
€20,000Germany, 2018. The Knuddels chat stored passwords in plain text. According to the regulator, data of about 330,000 users was stolen; other sources give higher numbers. The amount was reduced for quick cooperation.
€2,500Germany, 2019, a private person. An email where all recipients saw each other’s addresses.
€100–€6,000Private persons. At least 65 fines by October 2022, mostly for cameras at home and other people’s photos on social media.

Enforcement Tracker, JD Supra, Privacy Affairs, 12.10.2022

Who gets fined and for what inference

Small businesses and private personsHundreds to tens of thousands of euros. Cameras, mailings without consent, a letter to the wrong recipient, no information for people, weak security exposed after a breach.
Big TechHundreds of millions of euros. Data transfers out of the EU, advertising without a legal basis, children’s data.

CMS statistics as of 1 March 2026 data

2,685fines with complete data
1,048of them published by Spain
€2.28Maverage fine, heavily skewed by the largest ones

The most common reason is processing without a legal basis. Retail and telecoms lead by number of fines. The statistics are incomplete: some countries publish fines of a few hundred euros, others only large ones.

CMS Enforcement Tracker Report 2026

Next: Skills

Skills

Check your product against this page with a single sentence to your AI agent

Three open skills read your code, trace every personal-data flow down to the file and line, decide which laws apply and bring ready fixes. They send, delete and commit nothing without your “yes”.

Install
git clone https://github.com/stevedevhere/privacy-for-builders mkdir -p ~/.agents/skills ~/.claude/skills cp -r privacy-for-builders/skills/* ~/.agents/skills/ cp -r privacy-for-builders/skills/* ~/.claude/skills/

Works with Claude Code, Codex, Gemini CLI, GitHub Copilot and Cursor. In Claude.ai, upload each folder from skills/ in the skills section of settings. MIT license.

Check journal-app for GDPR and nFADP, it’s already live.

Possible incident. Journal entries and photos are open to outsiders. Close access first (fix #1), then check the logs.

Checked: 21 files from git, static only.

Laws: nFADP and GDPR Art. 3(2)(a): sign-up offers Switzerland and Germany [code: signup/page.tsx:34] [inference].

Top findings:

  1. Blocker. Table ai_reflections has no RLS [code: init.sql:42]
  2. Blocker. Any signed-in user reads other people’s entries [code: init.sql:33]
  3. Blocker. The photo bucket is public [code: storage.sql:2]

Apply fix #1?

Based on a blind-test answer, shortened. The full report with tables and patches goes into a private document.
  1. You write“check the project for GDPR”
  2. privacy-directorunderstands the request, owns the severity scale and safety rules
  3. privacy-code-auditfinds the data in the code
    privacy-jurisdictionsworks out the laws
  4. Reporta summary in chat, the full report in a document, patches one by one
  • 12problem types it hunts for, from tracking before consent to secrets in git history
  • 9scenarios, from a code audit to a data leak or a deletion request
  • 11jurisdictions with links to the official texts; other countries via the regulators’ register
  • file:lineon every finding, with a ready patch for blockers

How the skills were tested on test repositories: see the README. The skills give findings and drafts; the decision stays with you.