CCPA / CPRA
Determine California scope and operationalize consumer rights, opt-outs and covered assessments.
Children’s Online Privacy Protection Rule · 16 CFR Part 312
Design notices, parental consent and limited data collection for covered online services.
Operators of commercial child-directed online services and other covered operators with actual knowledge of collecting personal information from children under 13.
Verifiable parental consent flows, parent rights, retention schedules and a security program where required.
Assess child-directed and mixed-audience status, embedded third parties and each exception. Review the amended rule’s disclosure and retention requirements.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
COPPA kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Assess audience and collection · Product counsel + product lead [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Assess audience and collection | Product counsel + product lead | Before design or launch | Set a start date | Applicability memo; Data and SDK map | Open |
| Implement notices and parental permission | Product + privacy operations | Before covered collection | Set a start date | Notices; Consent workflow; Exception register | Open |
| Minimize, secure and delete data | Security + engineering | Before production and ongoing | Set a start date | Retention policy; Security program; Vendor review | Open |
| Operate parental rights and review changes | Privacy operations + product | On request and at material changes | Set a start date | Rights log; Review evidence; Change decisions | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Determine audience and actual knowledge, inventory identifiers and embedded SDKs, and identify information collected by third parties.
Fictional details. Use the same fields with evidence from your work.
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
Fictional details. Use the same fields with evidence from your work.
An engineer can trace collection to deletion, and a reviewer can see every crossing or third-party handoff.
Use the worksheet to design the diagram. Share the diagram with the people confirming scope, transfers or controls.
Provide required direct and online notices. Implement verifiable parental consent, separate disclosure permission where required, and documented exceptions.
Fictional details. Use the same fields with evidence from your work.
A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.
Send approved text to the publishing owner and give support teams the version and effective date.
Fictional details. Use the same fields with evidence from your work.
You can demonstrate what the person saw, how they acted and how the decision was honored.
Provide the consent log and tested withdrawal flow to privacy operations and downstream system owners.
Fictional details. Use the same fields with evidence from your work.
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.
Review necessity and retention by purpose. Document security controls, service provider assurances and deletion processes.
Fictional details. Use the same fields with evidence from your work.
A system operator can apply the rule and show evidence of deletion, exception or hold.
Send authorized rules to system and vendor owners and file the verified disposition evidence.
Fictional details. Use the same fields with evidence from your work.
A person who receives the plan can tell when to act, what to check and where to save the result.
Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.
Fictional details. Use the same fields with evidence from your work.
Each provider and contract record links to an actual function and all required identifiers are present.
Use the verified register in supplier reviews and put required submissions in the authority’s prescribed format.
Test review, withdrawal and deletion channels. Review changes in audience, SDKs, purposes, recipients and consent requirements.
Fictional details. Use the same fields with evidence from your work.
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Fictional details. Use the same fields with evidence from your work.
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.