The Deletion Request That Took Eleven Months
Archi4 min read
Contents
The Request That Took Eleven Months#
A customer wrote to a mid-sized outdoor gear retailer in February 2025 asking for her account to be deleted. The company replied inside the statutory window and closed the ticket. Eleven months later she received a promotional email from the same brand. Her address had been sitting in a marketing vendor's audience segment since 2023, copied there once and never touched by the deletion job.
No breach. No ransomware. A deletion workflow that ran on one system while the company's data lived in six. That is the shape of most privacy failures now, and it is a different shape than it was five years ago.
The Failure Was Boring, Which Is the Point#
The deletion tool worked exactly as designed. It wiped the CRM record, set a flag, and wrote a timestamp. It knew nothing about the support ticketing platform added in 2024, the reviews widget added in 2023, or the customer data platform that pushed audience segments to two ad networks every night.
The company's data map was a spreadsheet last edited in 2023. Three systems had been added since. In 2021, that gap might have produced a warning letter. In 2026 it is a live liability in more than a dozen states, several of which require deletion to reach processors and contractors, not only the controller's own database.
Five Years Ago, the Paperwork Was the Product#
In 2021, only California had a comprehensive consumer privacy statute in force. Most privacy budgets went to a policy rewrite, a cookie banner, and a request inbox that a paralegal checked twice a week.
Volume was low enough that manual tracking was defensible. A company handling forty requests a month could keep them in a shared queue and still answer on time. Vendor contracts commonly listed a data processing addendum as an afterthought, sometimes signed a year after the service went live.
Two things have changed since. Requests are routine rather than exceptional, and many arrive through one-click forms built by advocacy groups. And the average marketing stack holds more systems, each with its own copy of a customer record. The deletion job did not get harder. The surface it has to cover did.
What Regulators Actually Ask For#
Enforcement work in the past two years has leaned on documentation more than on the size of the harm. Investigators ask which systems were searched, who approved the exception list, and when a vendor confirmed the delete. A company that says it deleted the data and cannot show where it looked is in a worse position than a company that found a leftover copy and documented how it removed it.
Backups get the same treatment. A retention schedule that says tapes roll off after ninety days is a claim. A restore test that proves the deleted record is gone from the March snapshot is evidence.
That is the shift. Five years ago a privacy program was judged on notices. Now it is judged on proof of completion.
The Clause That Would Have Caught It#
A deletion propagation clause with three parts: a named contact at the vendor, a confirmation deadline measured in days, and a requirement to pass the same obligation to subprocessors. Add a subprocessor list reviewed every quarter, and the February 2025 request would have closed in all six systems.
The cost is a few hours of legal review per contract. Cheaper than a state attorney general asking why a customer's email address survived a confirmed deletion.
The Metric That Was Missing#
The retailer tracked requests received and average close time inside the CRM. Both numbers looked healthy. Neither measured the thing that failed.
A better pair: the percentage of deletion requests closed across every mapped system inside 45 days, and a monthly trace of five randomly chosen closed requests from intake to final vendor confirmation. The second one is manual work, roughly half a day each month. It is also the only reliable way to find the review site that stores a copy of every comment and email address, or the analytics tool that kept a hashed identifier long after the profile was gone.
The Next Failure Is Already Loaded#
Companies that just finished fixing deletion will find the same map gap waiting in the next request type: opting out of automated decision-making, consent for health and location data, and the question of whether support transcripts were fed into a model training set.
The pattern repeats because systems get added faster than maps get updated. In 2021, a privacy lead at a 400-person company could usually name every place customer data lived. Today the honest answer at most firms of that size is a spreadsheet with a date at the top. The date is the tell.
More articles