Framework brief · EU/EEA law
GDPR follows the person, not the office.
If you process personal data of people in the EU or EEA — including from a US company that offers them a product or monitors them — the duty applies. A privacy policy does not end it.
Current as of November 2026. Operator brief, not legal advice. UK GDPR is a separate regime.
All six frameworksWhat it is
A regulation, in force since 25 May 2018.
The General Data Protection Regulation is EU law. It is not a certification you hang on a wall. Article 42 allows certification schemes. None of them replaces the duties. Supervisory authorities in the member states enforce. The higher-tier fine cap is €20 million or 4% of worldwide annual turnover, whichever is higher.
It applies to controllers and processors. Most software companies are both: controller for their own marketing and employee data, processor for the customer data they handle under contract. The role changes the contract and the duties. Getting the role wrong is how a data processing agreement gets negotiated twice.
A privacy policy is not a transfer mechanism.
When it shows up in a deal
The European customer sends a processing agreement, not a compliment.
You do not have to be in Europe. Offering goods or services to people in the EU or EEA, or monitoring their behavior, is enough. A US company with an EU waitlist is often already in the conversation.
The buyer’s counsel will ask for an Article 28 processing agreement, a list of subprocessors, a story for international transfers, and how you will help them answer a data-subject request. Security questions come too. They are necessary. They are not the whole exam.
A health product aimed at EU patients can owe GDPR and, if it also serves US covered entities, HIPAA. The BAA does not satisfy the processing agreement. The processing agreement does not satisfy the BAA.
What the company is actually on the hook for
- Lawful basis Every processing activity needs one. Consent is not the only basis, and it is often the wrong one for a product the customer cannot refuse. Contract, legal obligation, and legitimate interests are the others teams actually use. Pick one you can defend. Do not collect the basis after the campaign.
- Minimization Purpose limitation, data minimization, storage limitation. If the field is not required for the purpose you named, it does not belong in the schema. “We might want it later” is not a purpose.
- Rights People can ask for their data, ask you to correct it, ask you to delete it, restrict it, object, and take it with them. You need a way to do that, generally within a month — not a sentence on the website.
- Transfers Sending personal data out of the EEA is its own workstream. Adequacy, or a transfer tool such as standard contractual clauses, plus a look at whether the destination actually protects the data. A policy page is not that tool.
- Breach clock Notifiable breaches go to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware. That clock is why the incident process has to name an owner before the incident.
- High-risk work A data protection impact assessment is required for high-risk processing. A new model trained on customer content is the kind of change that should trigger the question, not a press release.
What done looks like
You can show a lawful basis for each activity, a record of processing, contracts with processors, a path for rights requests, a transfer story that is not a slogan, and a breach procedure someone has rehearsed. Then you can show it again next year. There is no finish-line certificate.
What it does not replace
Security controls overlap SOC 2 and the HIPAA Security Rule. Reuse the evidence. GDPR still adds lawful basis, rights, and transfers, which those frameworks do not contain.
ISO 42001 does not legalize training data. PCI-DSS does not answer a deletion request. FedRAMP does not answer a European supervisory authority. If the model is the product, expect GDPR and ISO 42001 in the same quarter, for different reasons.
Where Carbon stops
We do not clear you under GDPR.
If GDPR is a cue, Carbon shapes the documentation — purpose, requirements, risk, evidence, traceability — in your environment. It does not pick your lawful basis, sign your processing agreement, or replace counsel. A supervisory authority does not accept a generated package as compliance.
Request a trialRelated briefs