- Requires retention disclosure at or before collection.
"at or before the point of collection"
Retention under the US CPRA is about setting a real retention period, saying it in the notice, and keeping personal information only as long as the disclosed purpose needs it.
This page shows what to disclose, how to pick a reasonable period or criteria, and what evidence teams should keep. Confirm legal and policy assumptions before implementation.
Structured answer sets in this page tree.
Cited legal and guidance references.
Retention under the US CPRA means telling consumers how long each category of personal information will be kept, or the criteria used to decide that period, and then keeping the data only for as long as is reasonably necessary and proportionate for the disclosed purpose. This page explains the core rule, the disclosure needed in the privacy notice, and the practical checks teams should use when they set or review retention periods.
The CPRA does not set one fixed number of days or months for every business. Instead, a business must disclose the length of time it intends to retain each category of personal information, including sensitive personal information, or, if that is not possible, the criteria it uses to decide that period.
The same section also says a business must not retain personal information or sensitive personal information for each disclosed purpose longer than is reasonably necessary for that purpose, and the CPPA FAQ says collection, use, and retention must be reasonably necessary and proportionate to the disclosed or expected purposes.
This US CPRA guide turns turn Retention into owners, evidence requests, review checkpoints, and reusable operating records inside Sorena.
Turn Retention into scoped questions, evidence fields, and review tasks.
Use Research Copilot to answer follow-up questions with cited source material.
Review scope, evidence, owners, and the next compliance actions with Sorena.
Start with the purpose for collecting the data, then ask how long the data is actually needed to complete that purpose and any closely related legal or operational obligations. Do not keep the data just because storage is cheap or because the system has no deletion rule yet.
A reasonable retention period should reflect the shortest period that still supports the disclosed purpose, any required backup or dispute window, and any legal hold or legal obligation that applies.
The owner should be the team that can change the privacy notice, the data map, deletion rules, and the retention schedule, usually privacy, legal, data governance, or product operations. The reviewer should confirm the period matches the disclosed purpose and the actual business process.
Keep evidence that shows the retention period, the reason for the period, the privacy notice wording, and any later review or deletion workflow update.
Check that the notice names each category of personal information and either gives the retention period or explains the criteria used to set it. If the business uses different periods for different systems, the notice should not hide that fact behind one generic statement.
Also check whether any data category is kept for a separate legal reason, such as a legal hold or a required recordkeeping rule, so the notice and the internal deletion workflow stay aligned.
"at or before the point of collection"
"approved the California Privacy Protection Agency's regulations"
"updated existing CCPA regulations"
"posting a privacy policy"