Start hereAssess audience and collection
~84 days leftOpen step
Guide library
Regulation North America

COPPA

Children’s Online Privacy Protection Rule · 16 CFR Part 312

Design notices, parental consent and limited data collection for covered online services.

Who it applies to

Operators of commercial child-directed online services and other covered operators with actual knowledge of collecting personal information from children under 13.

What you’ll produce

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.

Check official publications for this guide
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the 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.

What to review each week

Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.

Kickoff brief to share with your team

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.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
The whole journeyabout 84 days across 4 steps
  1. 01Assess audience and collectionProduct counsel + product lead · ~14 days
  2. 02Implement notices and parental permissionProduct + privacy operations · ~28 days
  3. 03Minimize, secure and delete dataSecurity + engineering · ~28 days
  4. 04Operate parental rights and review changesPrivacy operations + product · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 11 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Assess audience and collectionProduct counsel + product leadBefore design or launchSet a start dateApplicability memo; Data and SDK mapOpen
Implement notices and parental permissionProduct + privacy operationsBefore covered collectionSet a start dateNotices; Consent workflow; Exception registerOpen
Minimize, secure and delete dataSecurity + engineeringBefore production and ongoingSet a start dateRetention policy; Security program; Vendor reviewOpen
Operate parental rights and review changesPrivacy operations + productOn request and at material changesSet a start dateRights log; Review evidence; Change decisionsOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Assess audience and collection

    Who Product counsel + product lead When Before design or launch

    Determine audience and actual knowledge, inventory identifiers and embedded SDKs, and identify information collected by third parties.

    What to produce

    Applicability memoMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    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.

    Data and SDK mapDiagram worksheet

    Gather first

    • System and vendor inventory
    • Examples of live transactions or data events
    • Approved boundaries and information categories

    How to prepare it

    1. Sketch an entry point, storage location, processing system and recipient for each flow. Label arrows with what moves and in which direction.
    2. Show trust boundaries, geographic locations, contracts or interconnections that matter. Include administrative access, backups and deletion paths where relevant.
    3. Walk through a real end-to-end transaction with engineering and operations. Save an accessible diagram and keep the reviewed flow register beside it.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Source
    Web checkout
    Destination
    Billing API in EU region
    Data and purpose
    Order reference and billing email to send the receipt
    Protocol and boundary
    HTTPS, crosses from public network into hosted production
    Owner and validation
    Billing owner, validated against request logs on 2026-11-12

    Check before handing it over

    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.

  2. 02

    Implement notices and parental permission

    Who Product + privacy operations When Before covered collection

    Provide required direct and online notices. Implement verifiable parental consent, separate disclosure permission where required, and documented exceptions.

    What to produce

    NoticesMemo

    Gather first

    • Approved data map and purposes
    • Applicable disclosures and languages
    • Actual rights, consent and contact channels

    How to prepare it

    1. Write the information a person needs at the point of collection or disclosure. Use the applicable legal checklist to cover who, why, what, recipients, retention and choices.
    2. Match every promise to the real product and supplier configuration. Draft any short collection notice alongside the longer policy and use language appropriate to the audience.
    3. Have privacy and product owners check the draft against the live journey. Publish the approved version, record where it appears and test all contact and choice links.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Audience and moment
    Customer account contact, on the invoice email form
    Plain wording
    We use your billing email to send receipts and help with billing questions.
    Choices and contact
    Link to the applicable privacy request channel.
    Supporting record
    Processing activity P-014 and retention schedule FS-04
    Publish and verify
    Legal approval, web form URL, version and date

    Check before handing it over

    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.

    Consent workflowSpreadsheet

    Gather first

    • Approved consent language and purpose IDs
    • User interface or paper form
    • Audit event and withdrawal behavior

    How to prepare it

    1. Record the exact consent version, the purpose, the decision and its timestamp. Link to the interface or form shown to the person.
    2. Use an internal reference to the person or parent. Limit access and avoid placing underlying identity documents in the log.
    3. Exercise refusal and withdrawal. Verify that each downstream system stops relying on consent when required, and record the result.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Subject reference
    Account reference C-018
    Purpose and notice version
    Optional product updates, notice v4
    Decision and timestamp
    Opted in, 2026-11-02 14:12 UTC
    Capture channel
    Account preferences, unchecked by default
    Withdrawal and effect
    2026-11-12, active list updated, ticket P-123

    Check before handing it over

    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.

    Exception registerMemo

    Gather first

    • Agenda or decision request
    • Current performance measures and findings
    • Proposed actions and participants

    How to prepare it

    1. Write what decision is needed and list the reports or records the decision maker reviewed. Capture the date, people and decision authority.
    2. Record the decision, alternatives considered, any remaining risk and exactly who will do what by when.
    3. Send notes for factual review. File the approved record and add actions to the working tracker so progress reaches the next review.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Item
    Approve a fix for the missing access-removal retry.
    Inputs reviewed
    September test results and IAM incident root-cause notes.
    Decision
    Approve automatic retry plus daily reconciliation.
    Action and due date
    Platform lead to ship and test by 2026-11-28.
    Residual risk and follow-up
    Manual review remains until rollout. Check at December meeting.

    Check before handing it over

    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.

  3. 03

    Minimize, secure and delete data

    Who Security + engineering When Before production and ongoing

    Review necessity and retention by purpose. Document security controls, service provider assurances and deletion processes.

    What to produce

    Retention policySpreadsheet

    Gather first

    • Record categories and storage map
    • Legal and business retention needs
    • Deletion, archival and legal-hold process

    How to prepare it

    1. List each record type, storage system, owner and event that starts the retention period. Document the rationale and any applicable hold or exception.
    2. Select and test the deletion, return or archive procedure. Account for backups, vendors and logs, and keep evidence of what was disposed of and when.
    3. Have owners and legal sign off. Schedule reviews and flag cases where a system cannot yet apply the approved schedule.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record class
    Support conversation metadata
    Retention trigger
    Case closes
    Rule and basis
    Internal schedule RS-12, check contractual and legal retention requirements.
    Disposal method
    Scheduled purge with restricted job evidence. Legal hold overrides deletion.
    Owner and check
    Support operations, monthly export and purge reconciliation

    Check before handing it over

    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.

    Security programMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    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.

    Vendor reviewSpreadsheet

    Gather first

    • Signed contracts and supplier inventory
    • Critical functions, service relationships and subprocessors
    • Reporting instructions and data dictionary when applicable

    How to prepare it

    1. Identify the contracting entity, supplier identifier, service, dates and location. Map dependencies to critical functions and distinguish direct providers from subcontractors.
    2. Gather evidence on security, continuity, location, access and exit. In a required reporting register, use the current authority workbook and allowed identifiers.
    3. Reconcile records against contracts and procurement data, and validate reference keys. Send missing or inconsistent elements to the supplier and record the final approval.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Arrangement ID
    ICT-018, managed database hosting
    Contract and provider
    Enter signed agreement reference and verified legal entity identifier.
    Service and function
    Managed database supporting invoicing. Record entity and function reference.
    Location and subcontractors
    Check documented data locations and supplier chain.
    Evidence and status
    Contract verified, subcontractor fields under review.

    Check before handing it over

    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.

  4. 04

    Operate parental rights and review changes

    Who Privacy operations + product When On request and at material changes

    Test review, withdrawal and deletion channels. Review changes in audience, SDKs, purposes, recipients and consent requirements.

    What to produce

    Rights logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    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.

    Review evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    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.

    Change decisionsMemo

    Gather first

    • Agenda or decision request
    • Current performance measures and findings
    • Proposed actions and participants

    How to prepare it

    1. Write what decision is needed and list the reports or records the decision maker reviewed. Capture the date, people and decision authority.
    2. Record the decision, alternatives considered, any remaining risk and exactly who will do what by when.
    3. Send notes for factual review. File the approved record and add actions to the working tracker so progress reaches the next review.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Item
    Approve a fix for the missing access-removal retry.
    Inputs reviewed
    September test results and IAM incident root-cause notes.
    Decision
    Approve automatic retry plus daily reconciliation.
    Action and due date
    Platform lead to ship and test by 2026-11-28.
    Residual risk and follow-up
    Manual review remains until rollout. Check at December meeting.

    Check before handing it over

    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.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes