Data that law requires to be kept must be explained separately

What it is

Deleting the account does not mean every byte can vanish from every system at once. Accounting, tax, anti-money-laundering, communications, and health rules can require specific records to be kept for a statutory period. Explaining them separately means those classes, the kind of rule, and what happens when the period ends sit apart from “ordinary personal data will be deleted within N days,” not mixed into one “we will delete your data as soon as we can.” This entry is only that statutory exception. Whether the entry is findable, whether export ran, copies in third-party hands, cooling-off, and whether the identifier can be re-registered are not this topic.

Why it happens

People hear delete as an immediate empty. Statutory retention turns some records into “the account is gone, the record remains.” Mixed into the ordinary deadline, people demand “why is the invoice still there” before the period ends, or conversely believe everything must be kept for seven years. A separate list makes the exception a checkable set: invoices, transaction logs, identity-verification files—each mapped to a kind of duty, not an empty “compliance requires.” Copy must also say who can still access during retention (usually legal and audit, not the recommender), or “deleted but still there” is read as continued profiling. Deletion at period-end is a second clock and must sit beside the ordinary deletion clock, not only the first sentence.

Studying it

Before confirm, ask people to list “gone soon” versus “kept by law,” against the real retention list.

Independent variables: statutory items in their own block, classes and periods named, access scope stated. Dependent variables: match between recap and the real list, tickets after deletion because “the bill is still there,” reading statutory retention as marketing profiles still running.

Do not cite unverified statutory year-counts as universal numbers in the study; periods vary by jurisdiction and line of business. The manipulation is “said separately or not,” not “is seven years correct.” Counsel’s list is the comparison standard. Labs read carefully; the field should be judged by the block that remains if the long legal text stays collapsed.

Where it stops holding

A pure tool with no statutory duty can say “no personal data we must keep by law”; keeping the separate block is still useful so people do not guess. Periods differ by place; using the world’s longest period for everyone creates needless fear. An active investigation or lawsuit may add a temporary freeze; notify when it happens, do not write it into every deletion notice as a threat. Backup-rotation delay that is not statutory belongs on the ordinary timeline; stuffing it into the statutory block dilutes the block.

Applying it

• Beside the ordinary deletion deadline, a “kept because the law requires it” block: classes, until when, deleted at end, accessed only for compliance in between.
• The list shares a source with counsel’s duty table; do not write “relevant laws and regulations” without classes.
• Update the block when the account’s location changes; do not ship one global maximum list.
• Verify: before confirm, people name at least one class that will be kept and one that will not, against the current list. After deletion, spot-check that recommenders and marketing systems cannot read the retention store. Advance a test clock to period-end and confirm statutory items enter the deletion queue.

Related

• Within the group: H6.14.2 Data already shared with third parties is not undone by this deletion · H6.14.3 Deletion usually has a cooling-off window during which the request can be withdrawn · H6.14.4 Whether the old identifier can be re-registered after deletion needs an explicit policy
• Adjacent: H6.08 Account deletion · H8.14 Content lifecycle and archiving
• Search terms: statutory retention · legal hold · right to erasure exceptions