coppa news

Home » Articles » Verifiable Parental Consent: Accepted Methods

Verifiable parental consent, or VPC, is the heart of COPPA. If your website or app is directed to children under 13, or you know you’re collecting personal information from a child under 13, you generally need a parent’s verifiable consent before you collect, use or disclose that information. The question I hear most often is a simple one: what actually counts as “verifiable”?

The answer has shifted over the years. The FTC finalized amendments to the COPPA Rule in January 2025, they took effect in June 2025, and most operators had until April 22, 2026 to comply. Among other changes, the amended Rule writes several consent methods into its text that used to be approved one application at a time. Here’s where things stand now.

The standard: reasonable efforts

The Rule doesn’t demand certainty. It asks operators to make reasonable efforts, taking into account available technology, to ensure that the person giving consent is actually the child’s parent. It then lists methods that meet that standard. A method that isn’t on the list can still be used if it has been approved, either by the FTC through its formal application process or by an FTC-approved Safe Harbor program for that program’s members.

The methods the Rule lists

1. A signed consent form

The parent signs a consent form and returns it by mail, fax or electronic scan. It’s the oldest method and still one of the most reliable, but it’s slow, and many parents never get around to finishing it.

2. A card or online payment transaction

The parent uses a credit card, debit card or other online payment system in connection with a transaction, and the payment system notifies the primary account holder of each discrete transaction. The transaction part matters: collecting a card number without one isn’t the same thing. This method fits naturally when the parent is paying for a subscription anyway.

3. A toll-free call or video conference

The parent calls a toll-free number or joins a video conference staffed by trained personnel. It works, but staff cost money, and it doesn’t scale well for a free app with a lot of sign-ups.

4. Government-issued ID checked against databases

The parent’s government-issued ID is checked against databases of that information, and the ID has to be deleted from your records promptly once verification is done. Holding ID data creates its own security risk, so build the deletion into the process instead of relying on someone to remember it.

5. Knowledge-based authentication

The parent answers a set of dynamic, multiple-choice questions that are hard to guess and difficult enough that a child 12 or younger in the household couldn’t reasonably work out the answers. This method was approved through the FTC’s application process years ago, and the amended Rule now lists it directly.

6. Face match to a verified photo ID

The parent submits a government-issued photo ID, which is verified as authentic, along with an image of their face, and facial recognition technology compares the two. Trained personnel confirm the match, and the ID and the images have to be deleted promptly afterward. Like knowledge-based authentication, this was approved by the FTC before it was written into the Rule.

7. Email plus

If you don’t disclose children’s personal information to anyone, you can use an email from the parent coupled with additional steps. The Rule gives examples: sending a confirmatory email to the parent after you receive consent, or getting a postal address or phone number and confirming by letter or phone call. You also have to tell the parent they can revoke the consent they gave. This is the old “sliding scale” idea: the lower the risk of the use, the lighter the method.

8. Text plus

This one is new. Under the same no-disclosure condition, you can use a text message to the parent coupled with additional steps, such as a confirmatory text, a letter or a phone call, and again tell the parent they can revoke consent. The amended Rule also counts a parent’s mobile number as online contact information when it’s used only to text the parent about consent. For mobile-first products this is a real practical change, since for many families a text gets seen much faster than an email.

When you don’t need consent first

The Rule also has a short list of exceptions where you can collect limited information before, or without, parental consent. These are the ones that come up most often:

  • Collecting a parent’s online contact information to send the direct notice and ask for consent. If consent doesn’t come within a reasonable time, you have to delete it.
  • Responding once to a specific request from a child, and then deleting the contact information.
  • Collecting a persistent identifier solely to support the internal operations of the site or app, with no behavioral advertising or profiling, and saying so in your privacy notice.
  • Collecting an audio file of a child’s voice, and no other personal information, solely to respond to the child’s request, then deleting it immediately.

Each exception comes with conditions, and they’re narrower than a lot of companies assume.

Separate consent for sharing with third parties

This is the change I expect to catch the most operators. If you disclose children’s personal information to third parties, for example for targeted advertising, the amended Rule requires you to let parents consent to your collection and use of the information without consenting to the disclosure. You need separate verifiable consent for the disclosure unless it’s integral to the nature of your service. A single “I agree” that bundles everything doesn’t cut it anymore. And because email plus and text plus are only available to operators who don’t disclose, sharing data pushes you toward the heavier methods above.

Choosing a method

There’s no single right answer, but these questions narrow it down fast:

  • Do you disclose children’s information to anyone? If yes, email plus and text plus are off the table.
  • Is the parent paying anyway? A card transaction may add very little friction.
  • What data does the method create, and how fast can you delete it? ID checks and face matching come with deletion requirements and real security exposure.
  • Will parents actually finish it? A method that’s valid on paper but abandoned by most families just means fewer users, or pressure to cut corners.
  • Are you in a Safe Harbor program? Your program may have approved methods of its own.

Whatever you pick, write it down. The amended Rule also requires a written information security program and a written data retention policy, and your consent records belong in that picture. Your privacy policy has to match what you actually do, which is where a lot of sites slip; I go through the usual problems in privacy policy mistakes on child-directed sites. The Links page points to the law, the Rule and the FTC’s FAQs.

My take

VPC has always been where good intentions run into friction. Writing the newer methods into the Rule is welcome, because it gives smaller developers options they can build on without filing an application first. But the bigger gap hasn’t moved. General-audience services can still avoid all of this by not knowing who their users are, the same problem I ran into years ago reporting underage accounts on YouTube. And penalties have historically been small next to the number of kids affected, as my look at the average COPPA fine showed.

COPPA’s consent requirements also stop at 13, which surprises a lot of parents. More on that in Teens over 13: does COPPA still apply?

This is commentary, not legal advice. How COPPA applies depends on the details of your product, so talk to a lawyer who works on children’s privacy before you choose or change a consent method.

Keep reading


October 2026
M T W T F S S
« May   Nov »
 1234
567891011
12131415161718
19202122232425
262728293031