On this page
Do not borrow one retention period for every record
The Federal Trade Commission (FTC), the U.S. consumer-protection agency, advises businesses to keep sensitive information only as long as they have a business need and to adopt a written retention policy identifying what is kept, how long, how it is secured and how it is disposed of. This is guidance, not a single statutory retention period for all customer information.
For a business actually covered by the California Consumer Privacy Act (CCPA), section 1798.100 requires the retention length or criteria at collection and restricts keeping information longer than reasonably necessary for its disclosed purpose. California coverage and exemptions, tax or other record duties, and actual preservation requirements still need assessment.
Follow one expired customer export
Fictional example: the company’s approved process says a temporary booking export expires when reconciliation is completed. A staff member removes the live download link, but the export also sits in a vendor workspace. The management question is whether the approved action reached that copy. No particular retention period is recommended here.
| Record or copy | What the disposal record should establish |
|---|---|
| Live booking record | Purpose, applicable retention criterion and whether a separate retention duty remains. |
| Temporary reconciliation export | Completion trigger, copy holder, disposal instruction and confirmation for that copy. |
| Vendor workspace copy | Named party, contract instruction and evidence of its actual disposal step. |
| Archive or backup | Applicable retention process, eventual disposal treatment and what happens if data returns to active use. |
Describe what the evidence really proves
A disposal log should identify the dataset or copy without copying its contents into the log, the approved basis, action date, performer and confirmation. A supplier’s statement that “records are deleted” may not tell you whether it means the active account, exported files or every relevant copy. Ask for the scope and any remaining protected retention.
California’s separate consumer-request deletion rule has a qualified archived/backup delay. That provision is not a blanket exemption for keeping any routine archive forever. Routine retention approval and an individual deletion request are distinct processes. Keep private customer records and disposal evidence in restricted company systems; ELN needs the assigned task, not the files.
Scope
- No universal retention timetable, deletion certification or preservation decision. Actual legal holds, required records, vendor copies and applicable California scope remain unassessed.
Next step
Use Launch planner to assign the dataset retention decision, vendor confirmation and next review. Keep the copy-level disposal log separately; the planner does not delete records or certify destruction.
Sources & review notes
Federal Trade Commission
Passage, dates and research notes
official-guidance · Selected source provisions read across the data-owner guides: Guide sections Take Stock, Scale Down, Pitch It and Plan Ahead; full substantive guide read with retention/disposal guidance used
AI-assisted review of actual retained primary body, limited to the selected provisions above and the precise per-page evidence readScope. Source text does not decide actual business coverage, validate a supplier, perform requests or grant general security/privacy/legal clearance. Inaccessible/gated candidates are excluded.
California Legislature; California Privacy Protection Agency official consolidation
Passage, dates and research notes
statute · Selected source provisions read across the data-owner guides: Sections 1798.140(d),(i),(j),(ag) and1798.145 selected scope/role/exemption provisions | Sections 1798.140(d),(i),(j),(ag),1798.100(d) and1798.145 selected business/consumer/role and exemption provisions | Sections 1798.100(a)–(c),1798.140(d),(i) and1798.145 selected scope/exemption provisions | Section 1798.100(a)(3),(c) and1798.140(d),(i); retention notice/necessity and coverage | Sections 1798.140(d),(i) and1798.145 selected scope/exemption provisions | Sections 1798.105,1798.140(d),(i) and1798.145 selected coverage/exemption provisions | Sections 1798.106,1798.140(d),(i) and1798.145 selected scope/exemption provisions | Sections 1798.100,1798.110,1798.130(a)(2),1798.140(d),(i); access and portable/readily usable format provisions within coverage | Sections 1798.120,1798.140(d),(i),(ad),(ah); sale/sharing and coverage definitions | Sections 1798.121,1798.140(ae),(d),(i) and1798.145 selected scope/exemption provisions | Sections 1798.100(d),1798.140(d),(i),(j),(ag) and1798.145 selected coverage/role/exemption provisions
AI-assisted review of actual retained primary body, limited to the selected provisions above and the precise per-page evidence readScope. Source text does not decide actual business coverage, validate a supplier, perform requests or grant general security/privacy/legal clearance. Inaccessible/gated candidates are excluded.
California Privacy Protection Agency
Passage, dates and research notes
regulation · Selected source provisions read across the data-owner guides: Sections 7050(a)–(f) and 7051(a)–(c), printed pages58–62; allowed internal improvement, other-client boundary, specific contracts and oversight | Sections 7012(g),7050(d)–(g),7051 and7053; multiple collection businesses and distinct recipient contracts | Sections 7002(a)–(f) and7012(a)–(f); necessity, reasonable expectations, new purposes and notice content/placement | Section 7022(d)–(f); request-specific backup delay and retained-exception limits, used only to distinguish that mechanism | Sections 7060(a)–(h),7061(a)–(b),7062 and7063; verification principles, account/non-account and authorised-agent distinctions | Sections 7022(a)–(h),7050(c),7051(a)(8)–(9),(b); deletion, downstream notices, backups, exceptions, response and contract support | Sections 7023(a)–(k),7060(h); full correction provision, persistent accuracy, source notification, alternative deletion and disputed-field verification | Section 7024(a)–(l), full request-to-know provision including restricted identifiers, delivery, period, vendor assistance and categories | Sections 7025(a)–(f),7026 and7060(b); qualifying signals, browser/profile scope, conflicting settings/incentives and verification prohibition | Section 7027(a)–(m), full sensitive-information limit provision including methods, 15-business-day fulfilment, downstream instructions and permitted purposes | Sections 7050(a)(2),(c)–(f),7051(a)–(c); permitted subcontracting and required downstream terms
AI-assisted review of actual retained primary body, limited to the selected provisions above and the precise per-page evidence readScope. Source text does not decide actual business coverage, validate a supplier, perform requests or grant general security/privacy/legal clearance. Inaccessible/gated candidates are excluded.
Detailed rule records (1)
Set a retention basis and disposal process; CCPA-covered data cannot be retained longer than reasonably necessary for the disclosed purpose.
Protecting Personal Information: A Guide for Business California Consumer Privacy Act, effective January 1, 2026 California Consumer Privacy Act Regulations, effective January 1, 2026Bookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.