Notice at collection
The privacy disclosure shown when data is collected, telling people what you take, why, how long, and whether it is sold or shared.
What it is
A notice at collection is the short, timely disclosure shown at or before personal information is collected. Under California's CCPA, it tells people the categories collected, the purposes for collecting or using them, whether the business sells or shares them, and the retention period or the criteria used to set it, with a link to the fuller privacy policy. It may be layered: the form gets the essential facts and a link opens the detail.
Put it where collection happens: beside account creation, above an upload, in an app permission flow, on a paper form, or in a recorded phone script. Write it against the actual fields and downstream uses. If you later collect another category or use data for a materially different purpose, update the notice before that new collection or use.
Gotcha: timing is the feature. A footer privacy-policy link discovered after someone presses Submit is not notice at collection, and a generic 'we may use your data to improve services' sentence does not identify the real purposes. Do not make people surrender unrelated consent just to acknowledge that they saw a disclosure.
Ask AI for it
Write and implement a CCPA notice at collection for this flow under California Civil Code 1798.100(a). Map every form field, automatic data point, and SDK event to a statutory category, business purpose, retention period or criteria, and sale or sharing status. Produce a short notice beside the collection point plus a detailed linked layer, add the Civil Code 1798.135 'Do Not Sell or Share My Personal Information' link whenever a mapped field feeds a sale or share, and use the HTML aria-describedby attribute to associate the notice with the form. Ensure it appears before submission, works with keyboard and screen readers, and mark unknown facts with bracketed TODOs instead of inventing them.