← Back to Blog €1.2 Billion in GDPR Fines Landed in 2024—and the 750-Employee Exemption Won't Save You Until 2031

€1.2 Billion in GDPR Fines Landed in 2024—and the 750-Employee Exemption Won't Save You Until 2031

The EU's Q4 2025 Digital Package expands the SME exemption to 750 employees and mandates one-click cookie rejection. Here's what it means for email compliance.

The European Commission's Q4 2025 Digital Package proposes raising the Records of Processing Activities exemption from 250 to 750 employees and forcing one-click cookie rejection. Neither rule takes effect before 2031. Enforcement, meanwhile, is not waiting: €1.2 billion in GDPR fines landed in 2024 alone. If you run outbound into the EU, plan for the current regime, not the promised one.

The exemption expansion is real but slow

Here's the headline number. The Commission wants to lift the ROPA exemption threshold from under 250 employees to under 750. That means most small sales teams stop maintaining the Article 30 register of processing activities. Good news on paper.

The catch is the timeline. This is a proposal inside a package that still needs trilogue negotiation, member-state transposition, and a compliance grace period. Realistic implementation: 2031 at the earliest. Some provisions will slip further. The Parliament and Council will each renegotiate scope, and the employee-count threshold is exactly the kind of number that gets traded against other concessions. Watch for the final text to attach conditions the current draft doesn't carry — a turnover test, a processor-only carve-out, or a retention of the register for high-risk processing regardless of headcount.

So what do you do between now and then? You keep the register. If you're processing EU prospect data for outbound, you are the controller. The exemption you're relying on today is the 250-employee one, and it only applies if processing is occasional and doesn't touch special categories. Cold email at scale is not occasional. Most founders I've spoken to are technically outside the exemption already and don't know it.

There's a second trap in the reform itself. A higher headcount threshold doesn't exempt you from Article 5 principles, the lawful-basis requirement, or the erasure and access rights that prospects can exercise tomorrow. It only removes the documentation obligation. If your lawful basis for outbound is legitimate interest, you still need the balancing assessment on file — and that assessment is the evidence regulators ask for first when a complaint lands. Dropping the register without keeping the underlying records trades one gap for a worse one.

We covered the enforcement reality in our breakdown of the €5.88B in cumulative GDPR fines and the AI scrutiny driving them. The short version: regulators are using automated tooling to scan for compliance gaps. A missing ROPA is one of the easiest things for that tooling to flag.

One-click cookie rejection changes your tracking stack, not your email

The second proposal mandates a one-click reject mechanism for cookies. Today, most consent banners offer "Accept all" as a single click and bury rejection behind a settings menu. The Commission wants symmetry: one click to accept, one click to reject.

This matters for outbound because most sales tools rely on cookie-based tracking for website visitor identification, retargeting, and intent signals. If rejection becomes frictionless, expect opt-in rates to drop. Some estimates put the drop at 30-50% based on what happened after similar rules in France and the Netherlands.

The mechanism matters as much as the mandate. Under the current notice-and-consent model, banners can present "Accept all" prominently while routing rejection through a second layer of toggles and "legitimate interest" objections. A statutory one-click reject collapses that asymmetry: the banner must expose refusal at the same tier as acceptance, which removes the friction that currently props up opt-in rates. Consent rates under symmetric choice tend to converge toward genuine preference rather than default behavior.

What that means practically: your intent data gets noisier. Fewer identified visitors. Less reliable retargeting audiences. If your pipeline depends on "who visited the pricing page" lists from a tool like Clearbit or RB2B, model a 40% reduction in coverage by the time this lands. The loss won't be uniform — high-intent visitors who research thoroughly are often the same people who decline tracking, so the residual data skews toward lower-consideration traffic. Treat any visitor-identification list as a partial sample, not a census, and avoid drawing conclusions from small segment counts.

Email itself is unaffected. Cookie consent rules don't govern cold email. But the data you use to target that email gets thinner. The practical response is to shift qualification weight toward first-party signals you collect directly — reply behavior, meeting bookings, demo requests — and treat third-party intent as a prioritization layer rather than a pipeline source.

What actually matters for email compliance right now

Forget the 2031 reforms. Here's what regulators are enforcing today, and what we've seen trip up founders running EU outbound.

None of this is glamorous. All of it is what actually gets fined. The pattern across every enforcement action we've tracked is the same: not a missing policy, but a policy nobody operationalised. A balancing test that lives in a folder no one opens, an unsubscribe link that technically exists, a retention rule with no deletion job behind it — these are the failures that surface in a complaint. The reform debate will run for years; your outbound runs this week. Build the evidence trail now, because retrofitting it after a subject access request arrives is considerably more expensive than writing it down once.

The AI drafting question nobody's answering cleanly

If you use an AI tool to draft outbound emails, the prospect data you feed it is processing under GDPR. That means the tool needs a DPA, and you need to know where inference happens. Some tools process in the US. Some in the EU. Some won't tell you. The reform proposal doesn't resolve this ambiguity — it simply shifts where the pressure lands. By expanding the SME exemption, the Commission lowers the administrative floor for smaller operators, but it doesn't lower the substantive bar: you still need a lawful basis, you still need to honour data subject rights, and you still need a processor agreement that satisfies Article 28. What changes is the enforcement surface, not the obligation itself.

The harder question is one the proposal sidesteps entirely: whether inference constitutes "processing" in a way that triggers a DPIA, and whether the model provider or the deploying SME is the controller for that step. Most AI sales tools are architected so the vendor is a processor and you are the controller — but that allocation only holds if you can actually direct the processing. If the vendor trains on your inputs, or routes inference through infrastructure you can't audit, the controller relationship becomes contestable. A DPA that names sub-processors is the minimum; it doesn't settle the training question.

We built MiraReach with this in mind: human-in-the-loop sending, EU data residency options, and a DPA that actually names the sub-processors. But the broader point is that any AI sales tool you use should be able to answer three questions in writing: where does inference happen, what do you retain, and who are your sub-processors. If they can't, that's your answer.

We covered the broader compliance rule that works across jurisdictions in our piece on the one rule that satisfies 20 US state privacy laws. The same principle applies here: document your basis, honour opt-outs fast, minimise data. That gets you 90% of the way — and it's the 90% that survives whichever version of the reform eventually passes.

What we'd do next

Don't wait for 2031. The reform's timeline is a trap for small teams: even if the exemption lands, the transition period will reward companies that already have clean records, and penalize those scrambling to reconstruct them under deadline pressure. Audit your ROPA this quarter — not as a paperwork exercise, but as a map of where personal data actually flows through your sales process. Confirm you have DPAs for every tool in your stack, including the ones you adopted informally (a shared inbox, a scraping extension, a CRM add-on a contractor installed). These are exactly the gaps a supervisory authority will find first, and exactly the gaps an expanded SME exemption may not cover if processing is deemed "not incidental" to your core business.

Then test your unsubscribe flow end-to-end, from the recipient's click to the suppression list, and time it. One-click rejection under the reform will be judged on outcome, not intent — a link that routes through three redirects or a preference center that requires a login will fail the standard the regulation is moving toward. Document the test result. If it takes more than a few seconds or a second confirmation step, fix it now while the fix is cheap.

Finally, treat the cookie consent changes as a leading indicator rather than an isolated rule. The direction of travel is toward fewer clicks and clearer defaults, which means consent banners designed to slow users down are becoming a liability, not a conversion asset. If you want a tool that handles the compliance plumbing while you focus on the pitch, give MiraReach a try.

— Mira

Share on X Share on LinkedIn
Until next time — keep sending emails that are worth reading.
M
Mira
Head of Content at MiraReach
★ The Solopreneur Playbook · Free

Find 50 customers in 12 minutes.

Five customer-discovery prompts. Eight cold-email templates that hit 8% reply rate. The honest math: manual = 4 hours, MiraReach = 12 minutes.

Read the playbook →