Privacy Law Headlines Chase Fines. The Paperwork Decides Who Pays
Archi4 min read
Contents
- The fine is the last paragraph, not the story
- The headlines focus on fines. What is the operative part of an enforcement decision?
- What does the intake of a case look like?
- Consent banners are everywhere. Where does that go wrong?
- Data subject requests: what is the actual cost?
- Deletion requests and backups. How do companies square that?
- Breach notification. What do the headlines miss?
- International transfers get heavy coverage. Is the coverage useful?
- What about US state laws?
- Employee data?
- If a company did three things this quarter, what would they be?
The fine is the last paragraph, not the story#
Privacy enforcement arrives in the news as a number: a fine, a settlement, a percentage of annual revenue. Those numbers are real. They also describe the end of a process that routinely runs three to five years, survives at least one appeal, and gets revised before anyone pays. The parts that change how a company actually operates happen long before the announcement and get almost no coverage.
Marta Oyelaran is privacy counsel at a software company with about 700 employees and customers in the EU, the UK and three US states. We spoke about the distance between the coverage and the work.
The headlines focus on fines. What is the operative part of an enforcement decision?#
"The remediation order. The money gets the headline, and the number in the first press release is often not the number that ends up being paid. What a regulator actually imposes is a list of changes with deadlines: rewrite the retention policy, document the lawful basis for this processing, appoint a representative, submit to audits for two years. That list is what other companies should be reading, because it previews what an examiner will ask them for."
What does the intake of a case look like?#
"Most cases start with one complaint from one person. Not a sweep, not a researcher's report. Somebody made a request and did not get an answer, or got an answer that was incomplete, and kept the emails. The case file is often built almost entirely from the company's own correspondence. The lesson people miss is that the risk sits in a single thread handled badly by a support agent who had no escalation path."
Consent banners are everywhere. Where does that go wrong?#
"The banner is the visible part. The tag list behind it is the exposure. A marketing team adds a tool, the tool drops four cookies, and nobody updates the vendor inventory. I have seen companies that believed they had twelve trackers and actually had closer to forty. The second failure is honoring the choice: consent gets recorded, then a server-side tag fires anyway because someone hardcoded it."
Data subject requests: what is the actual cost?#
"We plan on 40 to 60 hours for a complicated one. The legal analysis takes an afternoon. The rest is search: which systems hold this person's data, who owns each system, whether the retention policy deletes it before we finish. The statutory clock is one month in the EU and 45 days in several US states, and it starts when the request arrives, not when it reaches legal. If the request sits in a shared inbox for nine days, those nine days are gone."
Deletion requests and backups. How do companies square that?#
"You cannot surgically edit a tape. The workable answer is to delete from live systems, suppress the record so it does not reappear in the next import, and let backups age out on schedule. Document the schedule. The failure mode is a company that deletes from the CRM and then restores the CRM from backup three months later without a suppression step. That is a repeat."
Breach notification. What do the headlines miss?#
"The 72-hour clock is not the hard part. The hard part is the gap between when the incident happened and when someone understood it. That gap is usually measured in weeks, and it is the first thing a plaintiff's lawyer asks about. So the record that matters is your own timeline: who saw what, when, and what they did about it. Companies spend money on the notification letter and almost nothing on keeping that log."
International transfers get heavy coverage. Is the coverage useful?#
"The rulings matter, but the failure is usually a data map that does not exist. Ask a support manager which countries their ticket system routes through and you will often get a guess. Transfers happen inside vendors you have never audited, in sub-processors named in an attachment nobody read. The unglamorous control is an inventory of vendors, countries and contract clauses, updated when procurement signs something."
What about US state laws?#
"The piece that gets skipped is opt-out signals. A handful of states require you to honor a browser-level signal, and plenty of companies still treat it as a cookie banner problem. Global Privacy Control is a header, not a click. If your stack only responds to the banner, you are out of compliance in those states whether or not anyone complains."
Employee data?#
"Headlines cover consumers. Most of the volume inside a company's own files is staff: monitoring software, background checks, performance analytics. Works councils and employee representatives have been more effective at forcing changes than regulators have, and that never makes the news."
If a company did three things this quarter, what would they be?#
"Write down a retention schedule and enforce it, because every other obligation depends on knowing how long you keep things. Inventory the tags and the sub-processors, not just the vendors you hold contracts with. And keep a request log with timestamps, so the clock is visible to more than one person."
More articles