On this page
A field needs a purpose before a designer adds it
The California Consumer Privacy Act (CCPA) requires a covered business’s collection, use, retention and sharing to be reasonably necessary and proportionate to the stated purposes. Its California-resident, business-threshold, affiliation and exemption conditions must be checked; this is not a rule that every U.S. startup has the same privacy form.
The California Privacy Protection Agency (CPPA) regulations tie the purpose to reasonable consumer expectations, the type and amount of information, collection context and disclosures. Consent for an additional purpose does not remove the separate necessity and proportionality assessment.
Review one service booking form
Fictional example: a home-maintenance operator is designing a booking form. The table is a management review, not a legal determination that the listed fields are permitted or prohibited. Ask the person who wants a field to explain what fails if it is omitted.
| Proposed field | Specific review question | Possible design decision to assess |
|---|---|---|
| Service address | Is it needed to visit the property? | Collect for the booked job; explain its use. |
| Preferred contact method | Which channel is needed to confirm the booking? | Allow an appropriate choice rather than collect every contact channel by default. |
| Full date of birth | What booking function requires the complete date? | Remove or narrow unless an actual necessary purpose is established. |
| Free-text health notes | What genuinely needed information might people enter? | Review the request wording and data need before inviting sensitive details. |
Put the explanation where collection happens
The regulations require the notice at or before collection and list its required categories, purposes, sale/sharing treatment, retention period or criteria and links. For a webform, a conspicuous nearby notice link is one described approach. Sending someone to the start of a long policy so they must search for the required information does not meet the specified direct-section approach. Sale and sharing have defined CCPA meanings; assess the actual disclosure rather than ordinary everyday labels.
If the team later adds a category or an incompatible purpose, revisit the collection and consent requirements before release. Keep a dated record of the field, purpose, necessity decision, notice version and approver. A visually optional field still needs an assessed purpose; making it optional is not a complete legal analysis.
Scope
- Selected CCPA collection requirements only. Actual coverage, necessity, consent, exemptions and any sector-specific collection duties require the proposed form and business facts.
Next step
Use Launch planner to assign the form-purpose review and notice approval before customer collection begins. Keep the field register and notice versions in your own files; ELN is not a form or privacy-notice generator.
Sources & review notes
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)
Collection must be reasonably necessary/proportionate for the applicable purpose; provide the required notice at or before collection.
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.