CCR §7012 Notice at Collection Drafting Requirements
The notice at collection must (a) identify the categories of PI to be collected, (b) identify the purposes for which categories of PI will be used and whether they are sold or shared, (c) identify whether categories of s
5
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Plain-language drafting evidence (reading level) · Data governance / DLP tooling
governing documentDocuments that govern the control
- Layered notice templates · Policy repository / GRC workspace
- Translation for languages used in solicitation · Policy repository / GRC workspace
- Accessibility compliance · Policy repository / GRC workspace
- Pre-collection delivery proof · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Notice not in language used to solicit consumer
- Retention criteria omitted
- Notice delivered after collection
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet1798.100(c) Data Minimisation, Necessity and Proportionality · CCR §7025 Opt-Out Preference Signal Configuration