What it means
A person asks a company to delete personal data. A dashboard marks the case closed, but a backup, marketing list or vendor system may still contain data, while some records may be lawfully retained.
Customer data deletion request evidence completeness tests whether each request has documented identity, scope, legal decision, execution and response evidence, and it makes privacy-request outcomes accountable without automating a legal conclusion. Define the request, since an account cancellation, marketing opt-out and formal erasure request can have different scope.
The UK Information Commissioner's Office says erasure rights under UK GDPR apply in certain circumstances and are not absolute, and an EDPB case summary concerns failure to inform a person of completion of an erasure request; these are named legal examples, not one global deletion rule. Record jurisdiction, because applicable rights, exceptions and response periods vary and local legal review should be obtained.
Verify the requester, since the person asking may be an account user, administrator, agent or someone without authority for the records, and check identity carefully by asking only for proportionate verification rather than collecting unnecessary sensitive data. Capture scope by recording requested data categories, accounts, systems and date ranges before execution, and record the decision by preserving whether each category was erased, retained under an exception or not held.
Check retention duties, because financial, fraud-prevention or legal-hold records may require preservation despite a request. Track systems, since the primary database, analytics, backups and downstream vendors can have different deletion mechanisms, and avoid false promises: a backup deletion may follow a documented retention cycle, and the approved treatment should be explained honestly.
Check processors, because a vendor instruction sent is not proof it completed the relevant action, and a processor may report deletion complete for one system but retain logs under its own lawful basis, so keep the scope and grounds explicit rather than treating a generic complete status as a full-system purge. Preserve minimal audit proof, since a record showing the request and response may need retention but should not contain the very data unnecessarily targeted, and secure communications, because sending a detailed deletion outcome to an unverified address can reveal personal information.
Define completeness as a case with applicable identity, decision, system action, exception and requester-response evidence, and choose a unit clearly, since one request can involve several categories and either request-level completeness or required evidence items can be counted. Check actual effects, because a job may succeed technically but match the wrong customer identifier, and record timestamps, since request received, identity confirmed, decision, action and response may all differ.
Show open cases, so that waiting for a vendor or legal opinion remains visible and deadline-managed, and separate timing, because evidence completeness does not prove the organisation met the relevant response deadline. Avoid accidental deletion, since two people with similar names may own different accounts, so verify stable identifiers before any action, and check shared data, because one document may contain information about multiple people and requires careful review rather than bulk deletion.
Track contradictions, such as an account that reactivates after a deletion request, where the changed customer instruction needs verification, and review repeated requests, since a second request from the same person may change scope or provide new identity evidence, so preserve both histories and avoid merging them into a misleading one-click outcome. Audit a sample by inspecting the evidence supporting claimed completion rather than relying on a filled checklist, and report exceptions clearly, since a lawful refusal or partial action should have a recorded reason and appropriate response.
In practice
Real-world examples.
Example
A verified erasure case records the in-scope systems, deletion confirmations from each, the grounds for the few records retained and a secure reply to the requester. Every applicable evidence item is present, so the case counts as complete. A reviewer can reconstruct what happened without asking anyone.
Example
A vendor instruction was sent for a marketing platform, but there is no completion acknowledgement or audit result. That evidence item stays open, so the case is incomplete even though the main database was cleared. The team chases the vendor and records the reply.
Example
A company retains invoices for a required period under reviewed local law, and documents that exception instead of claiming full erasure. The response to the requester explains which categories were deleted and which were kept, and why. The case is complete because the exception is evidenced.
Formula
Calculation
Illustrative completeness = eligible request cases whose applicable evidence items are verified / all eligible request cases reviewed at a named stage x 100. Report partial and still-open cases separately.
Worked example. A privacy team reviews 50 eligible request cases at the closure stage. Each case needs its applicable evidence items: verified identity, scope record, decision, system actions with vendor confirmations, any exception grounds and a secure requester response.
- 41 cases have every applicable item verified.
- 5 lack a vendor completion confirmation, 3 lack proof of the requester response and 1 lacks a scope record (5 + 3 + 1 = 9, and 41 + 9 = 50).
- Completeness = 41 / 50 x 100 = 82%.
- 6 further requests still inside their handling window are not in this denominator but are listed as open, with their deadlines, and the rate says nothing about whether any deadline was met.Case study
Seen in the real world.
This entirely fictional case follows Harbor CRM, an invented software company. A privacy request was marked completed after deleting the primary account, but a downstream marketing system had no confirmation. The team checked the requester identity, contacted its approved vendor route and updated the case only after verified action and response review.
The audit sample found two other cases with the same gap. Harbor CRM then added the marketing system to its standard checklist and reported evidence completeness beside the open-case count. The case authorises no real deletion or disclosure.
Watch out
Common mistakes.
- Calling a sent vendor instruction proof data was erased.
- Assuming every record must be deleted under every jurisdiction.
- Sending detailed outcome information to an unverified requester.
Questions
People also ask.
Is deletion always absolute?
No. Applicable rights and retention exceptions depend on jurisdiction and facts.
Do backups count?
Their treatment should be documented under the applicable retention and technical plan.
Does a complete evidence file prove timeliness?
No. Compare each case with its actual legal and operational deadline separately.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related