Data retention and deletion

Status: Built, runs on simulator

Retention time limits are unset, and the available backend does not automatically delete data.

Stage Two's privacy inventory labels its deletion rules as intended behaviour. Q-045 records the missing periods. A column saying “case closed plus retention” is not evidence of a running deletion job or an agreed deadline.

Different records have different limits

An account record, an encrypted document, a signed agreement, an audit entry and a chain transaction cannot be treated as one interchangeable dataset. The source describes an intended off-chain account-deletion request while retaining chain records, commitments, amounts, contracts under legal retention and the audit log. That request flow is not automated.

The privacy map lists these classes and intended readers. It also distinguishes server-key encryption from material encrypted for a chosen attestor. Deleting one stored copy does not establish that every intended recipient has deleted theirs.

Decisions before an operating promise

Kunal must set retention time limits and ownership. Counsel must determine required legal retention. The implementation then needs a tested request, verification and deletion process with an accurate explanation of what persists. The docs will not publish a deletion deadline until those decisions and the actual workflow agree.

A backer's public payment history and an issuer's private evidence have different visibility and persistence. Account deletion cannot be described as erasing a public chain record.