By · Last updated 2026-02-19

Back to BlogGDPR & Compliance

€4.7B: US Firms Pay 83% of GDPR Fines

US companies have received €4.7 billion in GDPR fines—83% of all enforcement. Learn why cross-border transfers are so risky and how to achieve compliance.

February 19, 20268 minute read
GDPRdata protectionSchrems IIcross-border transfers

€4.7B: US Firms Pay 83% of GDPR Fines

The Fine Gap

Since 2018, EU regulators have issued over €6.2 billion in GDPR fines. The split is stark. €4.7 billion — 83% — went to US firms.

Eight of the ten largest fines hit American tech companies.

The Ten Largest GDPR Fines

RankCompanyFineReasonYear
1Meta (Ireland)€1.2BEU-US transfers2023
2Amazon (Luxembourg)€746MTargeted ads2021
3TikTok (Ireland)€530MTransfers to China2025
4Instagram (Ireland)€405MChildren's records2022
5Meta (Ireland)€390MLegal basis for ads2023
6TikTok (Ireland)€345MChildren's privacy2023
7LinkedIn (Ireland)€310MBehavioral analysis2024
8Uber (Netherlands)€290MDriver records to US2024
9Meta (Ireland)€265MScraping2022
10WhatsApp (Ireland)€225MTransparency2021

The biggest fines all share one cause: cross-border transfers. Meta alone — including Instagram and WhatsApp — accounts for €2.4 billion.

Why US Transfers Fail GDPR

The Schrems II Ruling

In July 2020, the EU court struck down Privacy Shield. US spy laws clash with EU privacy rights. That ruling is known as Schrems II.

It has three main effects:

  • Standard Contractual Clauses alone are not enough
  • Firms must check whether US law gives proper cover
  • Most transfers need extra technical steps

The CLOUD Act Issue

US law can force American firms to hand over stored files. This holds true even when files sit on EU servers. The CLOUD Act lets US agencies demand content from US firms — anywhere on earth.

This is a core problem for US cloud providers in the EU.

Two Landmark Fines

Meta's €1.2 Billion Fine (2023)

Ireland's DPC found Meta had sent EU user records to the US with no valid legal basis. Meta had to halt all EU-US transfers within five months. It was the largest GDPR fine in history.

Uber's €290 Million Fine (2024)

Dutch regulators fined Uber for moving driver records to the US. Uber used Standard Contractual Clauses. But it lacked the extra safeguards Schrems II now requires.

What Regulators Check

Enforcers now look at three things:

  1. Is the transfer truly needed?
  2. Are extra safeguards in place?
  3. Does the target country's law give proper cover?

The Fix: EU Data Sovereignty

The safest path is to keep personal records inside the EU. That cuts cross-border risk at the root.

anonym.legal Infrastructure

FeatureDetail
HostingHetzner, Germany (ISO 27001)
CloudNo AWS, Azure, or GCP
Processing100% EU servers
EntityGerman legal entity
CLOUD ActNot applicable — no US parent

Zero-Knowledge Design

Our zero-knowledge setup adds a second layer of protection:

  • Passwords never leave your device
  • Keys stay on the client side
  • We cannot read your content even under legal order
  • No backdoor exists in our stack

See our security compliance overview for the full technical controls.

Steps for US Companies

1. Cut What Crosses

Anonymize personal identifiers before any transfer. Send only what is truly needed.

2. Use EU Providers

For EU user records, pick EU-based services where you can. Our GDPR compliance guide covers how to choose vendors.

3. Add Extra Safeguards

If transfers must happen, apply encryption and tokenization. These block access by US agencies even when compelled.

4. Run a Transfer Impact Check

Write up your review of whether the target country's law protects EU records. DPAs now expect this as a standard step.

How anonym.legal Helps

Before a transfer: Swap personal identifiers for tokens. Send the tokenized form. Keep real values in the EU.

For compliance: German hosting, zero-knowledge design, full audit trails, and GDPR-safe by default.

Pricing: Free tier: 200 tokens per month. Basic: €3/month. Business: €29/month.

Start protecting EU records today. Start free trial.

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.