COPPA
Design notices, parental consent and limited data collection for covered online services.
Colorado Privacy Act (CPA) and implementing rules
Work out which Colorado consumer rules apply and test recognized opt-out signals in a real browser.
Controllers conducting business in Colorado or targeting its residents who meet the applicable data-volume or sale-linked threshold, subject to exemptions and later amendments.
Documented CPA scope, notices, rights handling and assessments for covered heightened-risk processing.
Use current Colorado rules and amendments for specialized contexts, such as minors or biometrics. The California analysis and response workflow may require changes for Colorado.
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.
Colorado Privacy Act 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 Count covered data and document thresholds · Privacy counsel + data owners [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.
A retailer sees a recognized opt-out signal on its Colorado checkout site. The marketing engineer records which advertising or sale-related tags stop firing and verifies that server-side audiences respect the same choice.
Compare California scope, request rules and preference-signal treatment.
Colorado requires covered controllers to honor recognized mechanisms for applicable processing, including targeted advertising and sale.
Official reference (opens in a new tab)Checklist, instructions and 8 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Count covered data and document thresholds | Privacy counsel + data owners | Before launch and on material changes | Set a start date | Coverage memo; Processing inventory | Open |
| Test rights and universal opt-outs | Privacy operations + web engineering | Before putting covered advertising or sale into use | Set a start date | Rights request playbook; Preference signal tests | Open |
| Assess higher-risk processing | Privacy lead + product owner | Before covered heightened-risk processing | Set a start date | Assessment register; Consent records | Open |
| Review providers and keep evidence current | Procurement + privacy operations | At procurement and on change | Set a start date | Supplier terms; Evidence index | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Count Colorado consumers under the law’s definitions, trace sales and discounts, and distinguish exempt records from covered processing.
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.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Publish clear routes for consumer rights and appeals. Validate the recognized signal in the browser, then check downstream tags and vendor calls after the signal is received.
Fictional details. Use the same fields with evidence from your work.
A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.
Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Document purpose, risks and safeguards. Review sensitive data consent and purpose limitation. Gather evidence for profiling, targeted advertising or sale where applicable.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
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.
Review processor contracts, record who acts on opt-outs, and rerun tests after changes to domains, tags, providers or sign-in behavior.
Fictional details. Use the same fields with evidence from your work.
The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.
Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.
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.