Why COPPA is the clearest US law on fingerprinting
Most privacy laws reach device fingerprinting through interpretation: courts and regulators must decide whether a fingerprint falls within the law's definition of personal data. COPPA does not require that interpretive leap. The rule at 16 CFR 312.2 defines 'personal information' to expressly include 'a persistent identifier that can be used to recognize a user over time and across different websites or online services, such as a customer number held in a cookie, an Internet Protocol (IP) address, a processor or device serial number, or unique device identifier'. A device or browser fingerprint - which is precisely a persistent identifier that tracks a device across sites and sessions - is covered by the text of the definition.
This makes COPPA the US law where the fingerprinting question has the clearest statutory answer: on any platform directed to children under 13, or where the operator has actual knowledge it is dealing with a child under 13, a fingerprint is personal information and is subject to the parental consent regime unless a specific exception applies.
The FTC has enforced COPPA aggressively since 2013, when the persistent-identifier language was added to the rule. The agency treats COPPA violations as per-violation civil penalties; total exposure in major enforcement actions has reached tens of millions of dollars. Operators who deploy fingerprinting on child-directed services without satisfying the parental consent requirement are in the FTC's highest-risk enforcement category.
Who COPPA covers: directed-to-children vs actual knowledge
COPPA applies to two categories of operator. First, operators of websites or online services 'directed to children' under 13. The FTC evaluates whether a service is directed to children based on a totality-of-circumstances test: subject matter, visual content, use of animated characters, music or activities appealing to children, presence of child celebrities, advertising directed to children, and whether child-oriented sites link to the service (16 CFR 312.2).
Second, operators of general-audience services who have 'actual knowledge' that a particular user is a child under 13. Actual knowledge can be established by age data collected during sign-up, by direct disclosure from a parent, or by signals that a reasonable operator would treat as constructive notice. The FTC has found actual knowledge in cases where an operator received parental reports that children were using the service.
Mixed-audience platforms - services that are not primarily directed at children but attract a meaningful child audience - occupy a grey zone. The FTC's guidance allows mixed-audience platforms to age-screen users and apply COPPA only to the portion of the audience that self-identifies or is identified as under 13. However, this requires a functioning age-gate and separate data flows for the child-identified segment.
The verifiable parental consent requirement
16 CFR 312.5(a) requires operators to obtain verifiable parental consent before collecting, using, or disclosing personal information from children under 13. 'Verifiable' is defined in 16 CFR 312.2: the method used must be 'reasonably calculated, in light of available technology, to ensure that the person providing consent is the child's parent'.
The FTC has approved several consent methods over the years, including direct contact by a parent via toll-free telephone, e-mail with a digital certificate, credit or debit card verification, and other methods submitted for FTC approval. The key requirement is that the method must verify the parent's identity, not merely collect a checkbox affirmation from whoever is on the device - a distinction that matters because children can fill in consent forms themselves.
For persistent identifiers specifically, obtaining verifiable parental consent before the fingerprint is first collected is the required sequence. An operator cannot collect the fingerprint first and then seek consent. The parental consent must precede the collection act, which means the fingerprinting code cannot run until after consent is verified.
The internal-operations exception: what it covers and what it does not
16 CFR 312.5(c) creates an exception to the parental consent requirement for persistent identifiers used 'for the sole purpose of providing support for the internal operations of the website or online service'. The rule defines 'support for internal operations' to include: maintaining or analyzing the functioning of the website; performing network communications; authenticating users or security; legal compliance and safety activities; and certain frequency-capping activities.
Critically, 16 CFR 312.5(c) also requires that the persistent identifier collected under the internal-operations exception must not be used to 'contact a specific individual, including through behavioral advertising, to amass a profile on a specific individual, or for any other purpose'. This is a use limitation, not just a purpose limitation: even if the initial collection qualifies under the internal-operations exception, any downstream use of the identifier for advertising or profiling destroys the exception for the original collection.
The 2025 amendments to the COPPA Rule made explicit what had been implicit in FTC enforcement: personalized advertising is not a permitted internal-operations purpose. An operator who deploys fingerprinting under the internal-operations exception and then passes the fingerprint to an ad-tech vendor for targeting has violated COPPA regardless of the original collection justification. The exception is narrower than many operators assume.
COPPA internal-operations exception: permitted and prohibited fingerprinting purposes
| Fingerprinting purpose | Internal-operations exception available? | Parental consent required? | Statutory basis |
|---|---|---|---|
| Security and fraud detection: recognizing a previously flagged device attempting account takeover | Yes | No (if solely for this purpose) | 16 CFR 312.5(c)(7) - safety activities; support for internal operations |
| Authentication: verifying that a returning device matches the account's enrolled device set | Yes | No (if solely for authentication) | 16 CFR 312.5(c)(2) - authenticating users |
| Frequency capping: limiting the number of times a specific non-targeted ad is shown to a device | Yes (for contextual/non-targeted ads only) | No (if ad is not personalized) | 16 CFR 312.5(c)(6) - frequency capping of non-targeted advertising |
| Personalized or behavioral advertising: passing the fingerprint to an ad network for targeting | No | Yes - verifiable parental consent required | 16 CFR 312.5(c) exclusion; 2025 amendment making personalized advertising explicit |
| Analytics and product improvement: using the fingerprint to build usage profiles or session stitching | No | Yes - verifiable parental consent required | 16 CFR 312.5(c) - 'amass a profile' prohibition |
| Cross-site tracking: linking a child's activity across multiple websites or services | No | Yes - verifiable parental consent required | 16 CFR 312.2 - 'across different websites or online services' language in definition |
| Legal compliance: retaining an identifier to demonstrate age verification for a specific child's record | Yes | No (if solely for legal compliance record-keeping) | 16 CFR 312.5(c)(5) - legal compliance |
| Network communications and maintenance: technical identifiers needed only to route a single session | Yes | No (if not retained past the session) | 16 CFR 312.5(c)(1) - maintaining or analyzing functioning of the website |
The 2025 COPPA Rule amendments
The FTC finalized amendments to the COPPA Rule in 2024 and 2025, with several provisions directly relevant to fingerprinting. The most significant changes for fingerprinting operators are: (1) personalized advertising is now explicitly named as a purpose that requires verifiable parental consent - it cannot qualify under the internal-operations exception; (2) the definition of 'support for internal operations' was narrowed to make clear that data minimization applies within each permitted category, meaning operators cannot over-collect under one permitted purpose to enable a non-permitted one; (3) third-party ad networks and other recipients who receive personal information from COPPA-covered operators are independently covered as 'operators' if they have actual knowledge the data originated from a child-directed service.
The third-party coverage point is particularly significant for fingerprinting: an ad-tech vendor or analytics SDK that receives a device fingerprint collected from a child-directed site is itself a COPPA operator once it has actual knowledge of the source. This creates shared liability exposure that extends to the SDK or vendor supply chain, not just the first-party site operator.
FTC enforcement actions relevant to persistent identifiers and fingerprinting
- YouTube / Google (2019): FTC and New York AG settlement totaling $170 million - at the time the largest COPPA penalty ever assessed. Google's YouTube was found to have collected persistent identifiers from viewers of child-directed channels for behavioral advertising without parental consent. The settlement required YouTube to segregate child-directed content and apply COPPA-compliant data handling to it, including restricting persistent identifier collection.
- TikTok / Musical.ly (2019): $5.7 million settlement with FTC for collecting personal information from children under 13 - including persistent identifiers - without verifiable parental consent. The case established that the FTC will pursue platforms that know or should know they have a significant under-13 user base.
- Amazon / Alexa (2023): $25 million FTC settlement finding that Amazon retained children's voice recordings and associated geolocation data longer than necessary, and used that data to improve its voice recognition algorithm in violation of parents' deletion requests and COPPA deletion obligations. The case extended COPPA's reach to voice-derived persistent identifiers and retention practices.
- Kurbo by WW (2022): $1.5 million settlement finding that the Kurbo app collected height, weight, and birthdate from children under 13 and used that data to generate persistent user profiles without verifiable parental consent. The FTC applied the internal-operations exception narrowly, finding that profile-building for the app's core feature set still required consent.
- General FTC posture: the FTC's 2023 policy statement on commercial surveillance explicitly cited fingerprinting and device identifiers as enforcement priorities for child-directed services. The agency described persistent-identifier collection without parental consent as a pattern it would pursue regardless of whether the site was technically 'directed to children' under the traditional totality-of-circumstances test, where operators had actual knowledge of under-13 users.
How Benny the Doorman fits into a COPPA-aware deployment
On a child-directed service or any platform where under-13 users are present, Benny's fingerprinting calls must be structured to comply with COPPA's parental consent requirement before the fingerprint is collected. For security and authentication use cases that qualify under the internal-operations exception, Benny can operate without prior parental consent - provided the fingerprint is used solely for that security purpose and is not passed to any advertising, analytics, or profiling pipeline.
For any other use - including session-stitching, analytics, or ad-targeting - verifiable parental consent must be obtained before Benny is initialized for that user. This is an operator obligation: Benny provides the fingerprint signal; the operator's consent-management infrastructure determines whether and when Benny may run for a given user on a COPPA-covered platform.
Operators building mixed-audience platforms should structure their integration so that Benny is conditionally initialized only after age verification has determined the user is not under 13, or after verifiable parental consent has been confirmed for under-13 users who are permitted to use the service. This is an architectural pattern, not a configuration option in Benny itself.
Frequently asked questions
Is browser fingerprinting regulated under COPPA?
Yes. COPPA's implementing rule at 16 CFR 312.2 defines 'personal information' to include 'a persistent identifier that can be used to recognize a user over time and across different websites or online services'. A device or browser fingerprint is precisely this kind of identifier. On any website or online service directed to children under 13, or where the operator has actual knowledge it is collecting from a child under 13, a fingerprint is personal information and is subject to COPPA's parental consent requirement.
Does COPPA cover device fingerprinting?
Yes. The FTC's persistent-identifier definition in 16 CFR 312.2 covers any technique that produces a cross-session or cross-site identifier, including device fingerprinting, canvas fingerprinting, and audio-context fingerprinting. The rule lists cookies, IP addresses, and device serial numbers as examples but the list is not exhaustive. Any fingerprinting technique that produces a stable, persistent device identifier falls within the definition.
Is a device fingerprint personal information under COPPA?
Yes, explicitly. 16 CFR 312.2 defines personal information to include persistent identifiers that can recognize a user over time and across different websites or services. A device fingerprint satisfies this definition on its face. Operators cannot argue that a fingerprint is not personal information under COPPA in the way that argument is sometimes available under other privacy frameworks that rely on identification thresholds.
Can I use fingerprinting on a kids' site without parental consent?
Only in the narrow circumstances covered by the internal-operations exception in 16 CFR 312.5(c). Fingerprinting used solely for security, fraud detection, authentication, legal compliance, network maintenance, or non-targeted frequency capping may qualify for the exception. Fingerprinting for behavioral advertising, product analytics, user profiling, or cross-site tracking requires verifiable parental consent. The exception is destroyed if the fingerprint is passed to any advertising or profiling pipeline, even after a security-purpose collection.
What is the COPPA internal-operations exception?
16 CFR 312.5(c) allows operators to collect and use persistent identifiers without parental consent when used 'for the sole purpose of providing support for the internal operations of the website or online service'. Permitted purposes include maintaining site functionality, authentication, security, fraud detection, legal compliance, and frequency capping of non-targeted ads. The exception has a hard limit: the identifier cannot be used to contact the individual, to build a profile, or for behavioral advertising. The 2025 COPPA Rule amendments made personalized advertising an explicitly excluded purpose.
What verifiable parental consent methods does the FTC accept under COPPA?
16 CFR 312.5(b) requires that the consent method be 'reasonably calculated, in light of available technology, to ensure that the person providing consent is the child's parent'. FTC-approved methods include direct contact by telephone or video call, signed consent forms sent by postal mail or fax, credit or debit card verification, government-issued ID checks, digital certificates or electronic signatures, and knowledge-based authentication questions. A simple checkbox or email confirmation is not verifiable parental consent under the rule.
Does a mixed-audience site have to comply with COPPA for all users?
No. A general-audience site that attracts some children under 13 can implement age screening at registration and apply COPPA-compliant data handling only to users who are identified as under 13. The FTC's guidance permits mixed-audience operators to maintain separate data flows for child-identified users, provided the age gate is functioning and the child-directed segment receives full COPPA treatment. Operators cannot rely on a nominal age gate if they have signals that users are misrepresenting their age.
Are third-party SDKs and ad networks subject to COPPA if they receive children's fingerprints?
Yes, under the 2025 amendments. A third party that receives personal information - including fingerprints - from a COPPA-covered operator, with actual knowledge that the data originated from a child-directed service, is itself treated as an operator under COPPA. This means ad-tech vendors and analytics SDKs that receive device fingerprints from child-directed platforms cannot rely solely on a contractual disclaimer. The FTC has signaled that it will pursue both first-party operators and downstream recipients in enforcement actions involving children's persistent identifiers.
Tooling
Benny the Doorman is built for this compliance posture.
Free, cookieless fingerprinting that defers to your consent management platform, runs on Indian infrastructure, and ships with a DPA addendum sized for the jurisdiction above.
Last reviewed 2026-07-12

