Start hereDecide applicability and choose a route
~49 days leftOpen step
Guide library
Regulation North America

COPPA Safe Harbor

FTC COPPA Safe Harbor membership, program approval and oversight

Choose an FTC-approved Safe Harbor program for a children’s online service, prepare for its review, or apply to run a program under 16 CFR 312.11.

Issuing authority
U.S. Federal Trade Commission
Timing
The Commission issues a written determination on a program application within 180 days of filing following public notice and comment. Operators plan to their chosen program’s intake schedule and comprehensive annual review. Programs update their public list every six months, submit their annual report, and file the first triennial technology capability report no later than April 22, 2028.
Reviewed
Inside this guide
5 steps · 5 templates

Who it applies to

There are two routes. Website and app operators apply to an approved program for specified services. An industry group or other applicant seeking to run a Safe Harbor program submits self-regulatory guidelines to the FTC. Review the underlying COPPA Rule for child-directed services and operators with actual knowledge that they collect personal information from a child under 13.

What you’ll produce

For a member, a scoped review decision and calendar for reassessment. For a program, FTC-approved guidelines and evidence that independent review, complaints, discipline and reporting operate.

The FTC lists six approved Safe Harbor organizations. Match any listing to the particular website or online service. Member fees and timelines depend on the program and scope, so request a breakdown for onboarding, annual reviews, changes and remediation. In its 2015 TRUSTe order, the FTC said its complaint alleged more than 1,000 missed recertifications across privacy seal programs between 2006 and 2013. The settlement required $200,000 and additional COPPA program reporting and recordkeeping.

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 Safe Harbor 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  Decide applicability and choose a route · Privacy counsel + product owner or program sponsor [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.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Are you seeking review of a service or applying to run a Safe Harbor program?
  • Which named products, sites and versions will the decision cover?
  • What data, vendors and consent flows will the reviewer need to see?

Worked scenario

A learning app asks two approved programs for eligibility and itemized quotes. The privacy lead discovers an analytics SDK is active on a child sign-up route before the consent decision. Engineering documents and corrects the behavior, verifies it with a test account, and submits the scoped evidence for independent review.

What to read next

  • COPPA

    Use the underlying COPPA guide to plan notices, parental consent and data handling.

DATES AND TRIGGERS

Official milestones

See the deadline calendar
The whole journeyabout 49 days across 5 steps
  1. 01Decide applicability and choose a route, Privacy counsel + product owner or program sponsor, about 5 days
  2. 02Build the operator evidence file, Privacy officer + engineering + vendor management, about 12 days
  3. 03Submit, resolve findings and confirm membership scope, Operator privacy lead + Safe Harbor reviewer, about 10 days
  4. 04Submit guidelines for FTC approval, Safe Harbor applicant + counsel + independent review lead, about 15 days
  5. 05Maintain oversight, reporting and membership records, Program director + review team + compliance reporting owner, about 7 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 5 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Decide applicability and choose a routePrivacy counsel + product owner or program sponsorBefore launch, joining a program or preparing an FTC applicationSet a start dateApplicability and route memoOpen
Build the operator evidence filePrivacy officer + engineering + vendor managementBefore membership review and after material product changesSet a start dateOperator review evidence packOpen
Submit, resolve findings and confirm membership scopeOperator privacy lead + Safe Harbor reviewerAt intake, during remediation and at the annual reviewSet a start dateMembership and remediation recordOpen
Submit guidelines for FTC approvalSafe Harbor applicant + counsel + independent review leadBefore representing the program as FTC approvedSet a start dateFTC program application packageOpen
Maintain oversight, reporting and membership recordsProgram director + review team + compliance reporting ownerEach annual, six-month and triennial cycle as applicableSet a start dateProgram reporting and oversight calendarOpen
0 of 5 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

    Decide applicability and choose a route

    Who Privacy counsel + product owner or program sponsor When Before launch, joining a program or preparing an FTC application

    Identify each service, intended audience, actual knowledge, data collected and location. Match the service to approved membership options, or designate a program applicant for a Section 312.11 submission. Record fees and the approval boundary.

    What to produce

    Applicability and route memoDecision memo and product inventory

    Gather first

    • Service list
    • Audience research
    • Data inventory
    • COPPA Rule
    • FTC approved organization list
    • Program quotes

    How to prepare it

    1. List each site, app and edition with audience and data collection facts. Ask counsel to record the applicability basis and unresolved cases.
    2. For operator membership, compare current guidelines, eligibility, planned review dates, recurring charges and the services covered. For program approval, name the applicant and accountable sponsor.
    3. Approve a route and record which sites, editions and legal entities are included. Share the timeline and owner.

    Worked example

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

    Worked route example
    An educational game’s US child experience qualifies for program intake. A separate classroom tool needs another scope decision because its users and collection flows differ.

    Check before handing it over

    The reader can distinguish FTC program approval from the operator’s membership decision.

    Send the approved scope to legal, the reviewer and product owners.

  2. 02

    Build the operator evidence file

    Who Privacy officer + engineering + vendor management When Before membership review and after material product changes

    Prepare the data map, current notices, parental consent and deletion tests, disclosures and provider safeguards. Compare SDK and vendor activity with written descriptions. Correct issues and keep dated retests.

    What to produce

    Operator review evidence packEvidence index with data flow map and test results

    Gather first

    • Product scope
    • Current privacy notices
    • Consent workflows
    • SDK inventory
    • Vendor terms
    • Retention and deletion policy

    How to prepare it

    1. Map each data field by collection point, purpose, recipient, consent rule, retention trigger and accountable owner.
    2. Capture product screenshots and controlled test results for notice, consent, access, deletion and applicable disclosures. Include vendor evidence and compare actual events to the data map.
    3. Record and correct discrepancies. Give each approved artifact a reference, version, period and access controls for submission.

    Worked example

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

    Worked evidence example
    The test account shows an analytics event before the consent decision. The privacy lead assigns a fix and keeps a clean retest proving the event is withheld in the reviewed build.

    Check before handing it over

    The reviewer can trace real product behavior to each policy statement without accessing child records.

    Submit the approved pack using the program’s process.

  3. 03

    Submit, resolve findings and confirm membership scope

    Who Operator privacy lead + Safe Harbor reviewer When At intake, during remediation and at the annual review

    Submit the package through the program’s approved channel. Assign findings, show remediation and capture the exact decision and covered services. Check the program’s public listing and approved seal language.

    What to produce

    Membership and remediation recordFindings tracker and product scope register

    Gather first

    • Program rules
    • Intake confirmation
    • Reviewer findings
    • Approved product list
    • Seal terms

    How to prepare it

    1. Record each finding, impacted feature, responsible owner, due date and evidence required for closure.
    2. Attach the program decision, approved product scope and review owner. Check that public claims and any seal refer to the covered product.
    3. Schedule annual review and keep a channel for decisions about product and vendor changes, complaints and withdrawal.

    Worked example

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

    Worked scope example
    The program decision covers the mobile app and its parent portal. Marketing removes a footer seal from an unrelated product page until it has separate confirmation.

    Check before handing it over

    Membership claims match the program’s written decision and each finding has an owner.

    Share the review schedule and approved claims with affected teams.

  4. 04

    Submit guidelines for FTC approval

    Who Safe Harbor applicant + counsel + independent review lead When Before representing the program as FTC approved

    Use Section 312.11 to map equivalent or greater protections, independent assessment, disciplinary procedures and reporting. Assemble the proposed guidelines, strengths and comparisons, and assessment and enforcement explanations. Track public comment and the written determination.

    What to produce

    FTC program application packageGuidelines, crosswalk and program operating manual

    Gather first

    • Section 312.11
    • Draft guidelines
    • Review routine
    • Complaint policy
    • Discipline procedures
    • Reporting plans

    How to prepare it

    1. Map each substantive COPPA requirement to draft guidance and the test that proves its protection. Review coverage with counsel.
    2. Document independent comprehensive annual assessment and enforcement, including reviewer independence, complaint intake, discipline decisions and evidence retention.
    3. Assemble the materials required by the rule, review factual and confidentiality claims, and track notice, comments, responses and written determination.

    Worked example

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

    Worked discipline example
    A draft rule defines who decides on suspension after a repeated material finding and how an operator can respond. The application attaches the process and an example decision record.

    Check before handing it over

    The FTC can review the guidelines, the proof of oversight and the procedure for enforcing them.

    Give the final determination and approved guidelines to program operations.

  5. 05

    Maintain oversight, reporting and membership records

    Who Program director + review team + compliance reporting owner When Each annual, six-month and triennial cycle as applicable

    Schedule comprehensive annual member reviews, discipline follow-up, member list refreshes and annual FTC reporting. Set an owner for the triennial technology report. Maintain records and test that public lists match approved scope.

    What to produce

    Program reporting and oversight calendarCalendar, review log and member listing reconciliation

    Gather first

    • Approved guidelines
    • Member roster
    • Product scope records
    • Annual assessments
    • Disciplinary and complaint records

    How to prepare it

    1. Assign annual member reassessments, annual FTC reporting, six-month member listing updates and the triennial technology report to named owners and backups.
    2. Reconcile each service and operator against signed membership decisions. Preserve additions, departures, decisions and any disciplinary outcomes.
    3. Have a second reviewer check completeness and sensitive information handling. Retain the dated published list and report receipt.

    Worked example

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

    Worked reporting example
    Two services were removed as a member exited. The program archives the prior listing, removes only the two covered services and records the departure for annual reporting.

    Check before handing it over

    The public list, internal membership and FTC report reconcile for the review period.

    Give dated receipts and unresolved findings to the program director.

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