KOHEN AVOCATS · PARIS, FRANCE
pbskids: What should parents check about information collected by online games?

Hassan Kohen is a Paris-based lawyer admitted to the Paris Bar (Avocat au Barreau de Paris). Initial strategic analysis: €80 incl. VAT, personal reply within 24 hours.

100% confidential · Legal professional privilege · No obligation

Article generated by artificial intelligence, through a process designed and supervised by the firm

Sources: U.S. court opinions and official U.S. government publications, read for this article

Maître Hassan KOHEN, avocat au Barreau de Paris
Hassan KOHEN
Attorney at the Paris Bar

pbskids: What should parents check about information collected by online games?

Speak to a lawyer 06 89 11 34 45

Parents looking for children’s games may reasonably ask a question that appears before the first screen loads: what information will the service collect, and who can use it? PBS KIDS describes its site as offering educational games and videos. The discussion that follows is general in scope: it describes checks useful in comparable situations and makes no findings about PBS KIDS’ practices or legal obligations.

Start with the operator, the child’s age, and the kind of information requested. Federal law provides particular protections for children under 13 when a covered operator collects personal information through a child-directed online service or has actual knowledge that it collects such information from a child. The definition of a covered operator has limits, including an exclusion for certain nonprofit entities. A familiar children’s brand does not, by itself, answer whether that federal rule applies to every entity involved in a particular game.

Before a child plays, look for the privacy notice, the identity of the service providing the game, any third-party features, and any request for a parent’s permission. Keep a copy of the screen and the notice if something is unclear. If information has already been collected, check the available review and deletion procedures. Also distinguish a parent’s authorization to collect a child’s information from agreement to contractual terms: they are different questions and can have different consequences.

I. What should a parent check before a child uses an online game?

A. Identify the service, the information, and the applicable federal rule

Begin with the screen the child actually uses. A page may host a game itself, embed a game from another provider, or direct a user to an app operated by someone else. Write down the site’s name, the exact game or app, the device, and whether the child is asked to create an account. If an adult account is involved, note who created it and whether the child uses the service through that account. These details help identify which privacy notice and terms may matter; a general description of a platform is not a substitute for the notice attached to the specific service.

The federal Children’s Online Privacy Protection Act, or COPPA, defines a child as a person under 13 and describes which commercial operators fall within its scope. Its text is available in the 2024 United States Code edition of 15 U.S.C. §§ 6501–6505; the current federal rule supplies the operational details discussed below. An operator’s coverage depends on the statute and rule, not just on the fact that a child visits a site. The statutory definition excludes a nonprofit entity that is otherwise exempt from section 5 of the Federal Trade Commission Act. A nonprofit label alone, however, does not resolve the status or conduct of every separate service provider involved.

Under the federal definitions in 16 C.F.R. § 312.2, information may be collected passively as well as by asking a child to type it. The definition of personal information includes, in specified circumstances, a persistent identifier that can recognize a user over time and across different websites or online services. It also covers a child’s image or voice in a photo, video, or audio file, and certain geolocation and biometric information. A nickname that functions as online contact information can matter too. These categories do not mean that every game gathers every kind of information.

For a practical first pass, look at four separate features: what the child enters, what a device sends automatically, whether the child can communicate or publish, and whether another organization receives information. A game that asks for a first and last name presents a different question from one that uses a device identifier. A voice feature raises a different question from a saved game score. A public chat or user profile may expose information beyond the household. The right next step is to identify the feature and read the notice that describes it, rather than assume that all data is collected in the same way.

The federal rule in 16 C.F.R. § 312.3 addresses a covered operator of a service directed to children and a covered operator with actual knowledge that it collects or maintains personal information from a child. Its general obligations include notice, verifiable parental consent, parental review and limits on information demanded for an activity. Other provisions contain exceptions and conditions. The rule is not a blanket federal prohibition on children using online games, and it does not establish that a particular operator is covered merely because its content interests families.

A parent’s checklist can therefore be short without being superficial. Identify the operator named in the notice. Look for a section on children or users under 13. Compare the information the notice lists with the account and game screens. Check whether the service names or categorizes other recipients and explains the purpose of sharing. If the child moves to an external app or site, read that service’s own notice before treating it as part of the same arrangement. Keep the date of the version you reviewed, because the notice visible later may differ from the one presented when an account was opened.

In Hubbard v. Google LLC, No. 19-cv-07016-SVK (N.D. Cal. January 13, 2025), the federal district court in the Northern District of California on January 13, 2025 allowed some children’s privacy claims to proceed at the pleading stage while dismissing other claims and the claims against channel owners. The court evaluated the complaint’s allegations for that motion; it did not decide that every allegation had been proved. The decision shows why a family should preserve the particular service, account and notice involved, rather than assume that every participant in an online service has the same role.

That ruling is a district-court decision applying several states’ laws to a particular amended complaint. It is not a nationwide finding that a parent is entitled to money whenever a child uses a website. The court distinguished privacy loss from economic loss under the statutes it analyzed, and it dismissed some claims. A family assessing a different situation should separate what is known from what the notice suggests and from what remains uncertain. An account record, a screenshot and a copy of the relevant policy are useful because they describe different pieces of the same experience.

B. Read the notice and distinguish permission from a contract

When federal COPPA applies and consent is required, the parent should be able to tell what is being authorized before deciding. 16 C.F.R. § 312.4 specifies the contents of direct and online notices. The direct notice for obtaining consent must identify the items of personal information the operator intends to collect, how it intends to use them, and potential disclosure opportunities. Where information will be disclosed to third parties, the notice must identify the recipients or their specific categories and the purposes of disclosure. The rule also requires information about how a parent can provide verifiable consent.

Read the notice as a set of decisions, not as a single label saying that the service is safe. Is the request for an email address needed to establish a parent’s account, or is it for communication with the child? Does a voice feature record a child’s voice, and if so, what does the notice say about its use? Does the service describe behavioral advertising, contextual advertising, or neither? Are names and screen names visible to other users? Is a service provider acting only to support the service, or is another use described? If the notice does not explain a feature in terms you can match to the screen, save the question and ask the operator to clarify it before making a choice.

Under 16 C.F.R. § 312.5, a covered operator generally must obtain verifiable parental consent before collecting, using or disclosing a child’s personal information, including for a material change to practices previously authorized. The rule requires a method reasonably calculated, in light of available technology, to ensure that the person providing consent is the child’s parent. It lists several possible methods. It also requires a separate option for consent to certain third-party disclosures, except where the disclosure is integral to the service. Whether an exception applies depends on the rule’s specific conditions.

For example, the federal rule describes a limited exception for collecting online contact information solely to answer a child’s specific request once, subject to restrictions on use, disclosure and deletion. It also addresses a persistent identifier used solely to support internal operations, with a required notice and restrictions on other uses. These are not general permissions to reuse information for any purpose. If a notice relies on an exception, compare the described purpose and handling with the actual feature. If the relevant conditions are unclear, do not assume the exception either applies or fails.

A parent’s decision about data collection is distinct from accepting account terms. A privacy notice describes information practices; a contract may also contain payment, dispute-resolution or other provisions. The same screen can mention both, but one should not be treated as a substitute for the other. Before clicking, identify who is accepting what, save the displayed version of the terms, and check whether the child’s access is tied to an adult’s account. A screenshot of the screen immediately before a click can show the button, surrounding language and links together.

In A.A. v. Roku Inc., No. 25-cv-06284-NW (N.D. Cal. May 14, 2026), the federal district court in the Northern District of California on May 14, 2026 ordered arbitration of claims brought for minors after considering their guardians’ agreement and the circumstances of the accounts. The complaint alleged unlawful data practices; the arbitration order did not decide those allegations. The order shows that a parent should read the dispute terms of the account used by a child and preserve the version accepted, while recognizing that whether a child is bound turns on the applicable law and facts.

The court addressed a particular record and a California-law theory concerning nonsignatories. It did not hold that every parental account agreement binds every child, and its decision is not a ruling on the consent required by COPPA. Conversely, a separate permission to collect data does not automatically settle an arbitration question. Keep copies of the privacy consent, the account terms and any subsequent updates as separate records. If a household has more than one adult account, record which account the child actually used instead of relying on a later guess.

II. What can a parent do if information has already been collected?

A. Use review and deletion choices and preserve the relevant record

First, locate the privacy notice that applied to the service and the procedure it gives for a parent’s request. For a covered operator, 16 C.F.R. § 312.6 provides for a parent to obtain a description of categories collected, review information collected from the child, refuse further use or future collection, and direct deletion. The operator’s means of review must verify that the requester is the child’s parent and must not be unduly burdensome. The rule also permits termination of a child’s service in the circumstances it specifies, subject to its limits.

Make the request specific enough to locate the right account. Identify the child and account through the operator’s stated process, the game or app, the approximate period of use, and the desired response: review, deletion, refusal of future collection, or a combination. Do not include more sensitive information than the process reasonably requires. Save a copy of what was sent, any confirmation, and the response. If several services are involved, use separate requests so that the answer can be connected to the operator that received it.

Before deleting an account, consider whether you need a record of the account settings, purchase history, notice or prior communications. A deletion request and the voluntary closure of an account may use different controls. A household can keep copies of its own records without publishing a child’s identifying information. If a service explains that an identity check is necessary, review the proposed method and ask how verification information will be handled. Do not send identity documents to an address found in an unrelated message without first checking the service’s own published process.

The federal rule also limits the information a covered operator may require for participation. 16 C.F.R. § 312.7 prohibits conditioning a child’s participation in a game, prize or other activity on disclosure of more personal information than is reasonably necessary to participate. A parent can compare the requested field with the activity: is the game asking for information to save progress, enable a communication feature, or perform some other function? The answer depends on the actual feature and the operator’s explanation, not on a universal list of fields that every game may or may not request.

Security is another distinct question. 16 C.F.R. § 312.8 requires covered operators to maintain reasonable procedures for confidentiality, security and integrity of children’s personal information. It also sets requirements for a written information security program and reasonable steps concerning other entities that collect, maintain or receive information as described in the rule. The presence of a privacy notice alone does not tell a parent whether those requirements apply or have been met. An account setting, a notice and an operator’s actual security practices are different kinds of information.

When reviewing settings, distinguish disabling a feature from deleting previously collected information. Turning off a microphone, for example, can change what a device can capture going forward; it does not by itself establish what a service already stored or whether another copy exists. Similarly, removing an app from a device is not necessarily the same action as submitting a deletion request to the operator. Check the service’s instructions for each step and keep the response. If the service offers several profiles, identify the profile used by the child rather than assume that one account-wide switch controls all of them.

A school account deserves its own review. A child may use the same type of educational game through a classroom and at home, with different account holders and notices. Ask the school what service it selected, how the child signs in, and what written information it has provided about the arrangement. Then compare the documents with the operator’s notice. Do not assume that a school’s use of a service resolves every question about a parent’s data choices or that the home account operates under the same terms.

If the information you receive is incomplete, describe the missing item precisely. For example, a response listing account fields may not explain whether a voice feature was enabled; a notice about advertising may not identify the account used on a particular device. Ask about the particular feature, profile and period. Keep the original answer as well as any clarification, so the record shows what was explained at each stage. A question about a possible practice is not proof that it happened.

B. Separate regulatory reports, individual claims, and settlement notices

If the answer raises concern about a covered service, the next route depends on the question. A request to review or delete information asks the operator to perform a specific action. A report to a regulator describes facts for an agency to consider. An individual legal claim requires its own legal basis, applicable jurisdiction and facts. A settlement notice concerns a defined group and a particular proceeding. These routes are not interchangeable, and sending one type of request does not automatically accomplish the others.

Federal COPPA enforcement is principally assigned to the Federal Trade Commission and certain other authorities, with provision for state attorneys general in the statute. In the Hubbard ruling discussed above, the Northern District of California explained that COPPA itself does not provide a private right of action, while the court considered other state-law claims. A parent therefore should not assume that a private demand for money can be brought directly under COPPA merely because a federal rule is relevant. Other claims depend on their own requirements and on the law governing the facts.

A practical report should identify what is directly known: the service, the feature used, the child’s age at the relevant time, the notice or screen seen, the request made, and the response received. If a parent suspects information was shared, identify what supports that concern and what remains uncertain. Screenshots, account notices and communications can be more useful than broad labels. Keep the child’s identifying details out of public posts and use the recipient’s established process for submitting any sensitive information.

State rules and remedies may differ. The Hubbard court examined consumer-protection claims under multiple states’ laws and reached different conclusions about the alleged loss and available relief. That makes the child’s state, the operator’s conduct, the type of claimed injury and the remedy sought important questions. It does not make the court’s analysis a single nationwide state-law standard. Where a family has moved or used a service in more than one state, record where and when the relevant activity occurred rather than assume that one state’s rules automatically govern every part of the matter.

In A.B. v. Google LLC, No. 23-cv-03101-PCP (N.D. Cal. October 23, 2026), the federal district court in the Northern District of California on October 23, 2026 granted final approval of a class settlement concerning alleged collection of children’s information. The order states that the settlement and order are not admissions of wrongdoing or liability. Its defined class, allocation and release show why a recipient should compare any settlement notice with the court’s actual order before assuming that a payment or release applies to a different child or service.

For any settlement notice, find the court and case number, the class definition, the relevant service and period, and the current stage of the proceeding. Check whether a person is included or excluded and what the order says about the claims released. Do not infer a finding of liability from a settlement approval. The existence of a settlement in one proceeding does not establish that a family using another service is part of that class or entitled to the same payment. A notice may be old, amended or unrelated to the household’s actual account; the court document and the notice should be read together.

Where a contract refers disputes to arbitration, the first task is to identify the actual agreement and who accepted it. Preserve the account-opening screen, the terms then available, later updates and the date of any acceptance. In a dispute involving a child, the identity of the account holder, the child’s relationship to that person, and how the service was used can matter. The A.A. order illustrates one result on one record; it does not eliminate possible differences in other records or jurisdictions. A privacy consent screen alone is not a complete account of the contract-formation question.

Finally, make a clear chronology for your own use. Put the date of the child’s use beside the version of the notice, the account or profile used, the feature involved and each request or response. Mark unknown facts as unknown. If a notice says a practice changed, keep both versions if available; a current policy does not necessarily describe an earlier session. This organized record helps separate a decision you can make now, such as changing settings, from a question that depends on information the operator or an authority has not yet supplied.

Conclusion

For a child’s online game, the useful starting point is the particular service and feature: identify the operator, understand what information is requested or collected, and read the notice and any parental consent request. Federal COPPA protections apply when their conditions are met, including the definition of a covered operator; the rules also provide specified review and deletion choices. Keep account terms separate from data consent, preserve the relevant screens and responses, and assess any regulatory report, individual claim or settlement against its own facts and applicable law.

📄 Official circular