The following FAQs are intended to supplement the compliance materials available on the FTC website. In addition, you may send questions or comments to the FTC staff’s COPPA mailbox, CoppaHotLine@ftc.gov. This document represents the views of FTC staff and is not binding on the Commission. To view the Rule and compliance materials, go to the FTC's Children’s Privacy page for businesses. This document serves as a small entity compliance guide pursuant to the Small Business Regulatory Enforcement Fairness Act.
Some FAQs refer to a document called a Statement of Basis and Purpose. A Statement of Basis and Purpose is a document an agency issues when it promulgates or amends a rule that explains the rule’s provisions and addresses comments received in the rulemaking process. A Statement of Basis and Purpose was issued when the COPPA Rule was promulgated in 1999, and another Statement of Basis and Purpose was issued when the Rule was revised in 2013.
A. GENERAL QUESTIONS ABOUT THE COPPA RULE
B. COPPA ENFORCEMENT
C. PRIVACY POLICIES AND DIRECT NOTICES TO PARENTS
D. WEBSITES AND ONLINE SERVICES DIRECTED TO CHILDREN, INCLUDING MIXED AUDIENCE SITES AND SERVICES
E. THIRD PARTIES, SUCH AS AD NETWORKS AND PLUG-INS, COLLECTING PERSONAL INFORMATION ON SITES DIRECTED TO CHILDREN
F. PHOTOS, VIDEOS, AND AUDIO RECORDINGS
G. GEOLOCATION DATA
H. GENERAL AUDIENCE AND TEEN SITES OR SERVICES
I. VERIFIABLE PARENTAL CONSENT
J. EXCEPTIONS TO PRIOR PARENTAL CONSENT
K. PARENTAL ACCESS TO CHILDREN'S PERSONAL INFORMATION
L. DISCLOSURE OF INFORMATION TO THIRD PARTIES
M. REQUIREMENT TO LIMIT INFORMATION COLLECTION
N. COPPA AND SCHOOLS
O. COPPA SAFE HARBOR PROGRAMS
Congress enacted the Children’s Online Privacy Protection Act (COPPA) in 1998. COPPA required the Federal Trade Commission to issue and enforce regulations concerning children’s online privacy. The Commission’s original COPPA Rule became effective on April 21, 2000. The Commission published an amended Rule on January 17, 2013. The amended Rule took effect on July 1, 2013.
The primary goal of COPPA is to place parents in control over what information is collected from their young children online. The Rule was designed to protect children under age 13, while accounting for the dynamic nature of the Internet. The Rule applies to operators of commercial websites and online services (including mobile apps and IoT devices, such as smart toys) directed to children under 13 that collect, use, or disclose personal information from children, or on whose behalf such information is collected or maintained (such as when personal information is collected by an ad network to serve targeted advertising). The Rule also applies to operators of general audience websites or online services with actual knowledge that they are collecting, using, or disclosing personal information from children under 13, and to websites or online services that have actual knowledge that they are collecting personal information directly from users of another website or online service directed to children. Operators covered by the Rule must:
The Rule applies to operators of commercial websites and online services (including mobile apps and IoT devices) directed to children under 13 that collect, use, or disclose personal information from children. It also applies to operators of general audience websites or online services with actual knowledge that they are collecting, using, or disclosing personal information from children under 13. The Rule also applies to websites or online services that have actual knowledge that they are collecting personal information directly from users of another website or online service directed to children.
The Rule defines personal information to include:
The FTC has a comprehensive website that provides information to the public on a variety of agency activities. The Children’s Privacy section includes a variety of materials regarding COPPA, including all proposed and final Rules, public comments received by the Commission in the course of its rulemakings, guides for businesses, parents, and teachers, information about the Commission-approved COPPA safe harbor programs, and FTC cases brought to enforce COPPA. Many of the educational materials on the FTC website also are available in hard copy free of charge at www.bulkorder.ftc.gov.
The first thing you should do is read the FTC’s Children’s Privacy guidance materials. If, after reviewing the FTC’s online materials, you continue to have specific COPPA questions, please send an email to our COPPA hotline at CoppaHotLine@ftc.gov.
If you want to help law enforcement potentially spot a pattern of violations requiring law enforcement action, you may report that to the FTC online. You also may call our toll free telephone number at (877) FTC-HELP to report to a live operator. Please note that the FTC does not resolve individual consumer disputes. If you have a complaint about someone violating the COPPA Rule and need individual help, you should contact your State Attorney General.
COPPA applies to personal information collected online by operators of both websites and online services. The term “online service” broadly covers any service available over the Internet, or that connects to the Internet or a wide-area network. Examples of online services include services that allow users to play network-connected games, engage in social networking activities, purchase goods or services online, receive online advertisements, or interact with other online content or services. Mobile applications that connect to the Internet, Internet-enabled gaming platforms, connected toys, smart speakers, voice assistants, voice-over-Internet protocol services, and Internet-enabled location-based services also are online services covered by COPPA.
No. COPPA only applies to personal information collected online from children, including personal information about themselves, their parents, friends, or other persons. However, the Commission’s 1999 Statement of Basis and Purpose notes that the Commission expects that operators will keep confidential any information obtained from parents in the course of obtaining parental consent or providing for parental access pursuant to COPPA. See 64 Fed. Reg. 59888, 59902 n.213.
In enacting the Children’s Online Privacy Protection Act, Congress determined to apply the statute’s protections only to children under 13, recognizing that younger children are particularly vulnerable to overreaching by marketers and may not understand the safety and privacy issues created by the online collection of personal information.
Although COPPA does not apply to teenagers, the FTC is concerned about teen privacy and does believe that strong, more flexible, protections may be appropriate for this age group. See FTC Report: Protecting Consumer Privacy in an Era of Rapid Change: Recommendations for Businesses and Policymakers (Mar. 2012), at 29, 60. The FTC also has issued a number of guidance documents for teens and their parents. These educational materials are available at www.OnguardOnline.gov.
Yes. The Rule governs the online collection of personal information from children by a covered operator, even if children volunteer the information or are not required by the operator to input the information to participate on the website or service. The Rule also covers operators that allow children publicly to post personal information. Finally, the Rule defines “collection” to include the passive tracking of children’s personal information through a persistent identifier, and not just active collection. See 16 C.F.R. § 312.2 (definition of “collection”).
No. COPPA is meant to give parents control over the online collection, use, or disclosure of personal information from children. It was not designed to protect children from viewing particular types of content wherever they might go online. If you are concerned about your children seeing inappropriate materials online, you may want to consider a filtering program or an Internet Service Provider that offers tools to help screen out or restrict access to such material. Information about such tools is available at ConnectSafely.org and Stay Safe Online’s advice about parental controls, and from operating system developers.
No. COPPA covers operators of general audience websites or online services only where such operators have actual knowledge that a child under age 13 is the person providing personal information. The Rule does not require operators to ask the age of visitors. However, an operator of a general audience site or service that chooses to screen its users for age in a neutral fashion may rely on the age information its users enter, even if that age information is not accurate. In some circumstances, this may mean that children are able to register on a site or service in violation of the operator’s Terms of Service. If, however, the operator later determines that a particular user is a child under age 13, COPPA’s notice and parental consent requirements will be triggered.
Importantly, however, a website or online service may be deemed directed to children even if its Terms of Service prohibits children from using the site or service. In determining whether a particular site or service is directed to children, the FTC will consider the factors set forth in the Rule. See 16 C.F.R. 312.2 (definition of “Web site or online service directed to children”); see also FAQs Section D.
Information about the FTC’s COPPA enforcement actions can be found by clicking on the Cases link on the FTC’s Children’s Privacy page. Parents, consumer groups, industry members, and others that believe an operator is violating COPPA may report that to the FTC online or call our toll free telephone number at (877) FTC-HELP.
A court can hold operators who violate the Rule liable for civil penalties of up to $53,088 per violation. The amount of civil penalties the FTC seeks or a court assesses may turn on a number of factors, including the egregiousness of the violations, whether the operator has previously violated the Rule, the number of children involved, the amount and type of personal information collected, how the information was used, whether it was shared with third parties, and the size of the company. The determination of the appropriate civil penalty will vary on a case-by-case basis. In some cases, the FTC has elected to seek no civil penalty, while in other cases, the penalties have been millions of dollars. Information about the FTC’s COPPA enforcement actions, including the amounts of civil penalties obtained, can be found by clicking on the Cases link on the FTC’s Children’s Privacy page.
Yes. COPPA gives states and certain federal agencies authority to enforce compliance with respect to entities over which they have jurisdiction. For example, New York has brought several COPPA enforcement actions. See https://ag.ny.gov/press-release/2019/ag-james-google-and-youtube-pay-record-figure-illegally-tracking-and-collecting (Sept. 2019); https://ag.ny.gov/press-release/2018/ag-underwood-announces-record-coppa-settlement-oath-formerly-aol-violating (Dec. 2018); https://ag.ny.gov/press-release/2016/ag-schneiderman-announces-results-operation-child-tracker-ending-illegal-online (Sept. 2016). In addition, some federal agencies, such as the Office of the Comptroller of the Currency and the Department of Transportation, are responsible for handling COPPA compliance for the specific industries they regulate.
First, until you get your website or online service into compliance, you must stop collecting, disclosing, or using personal information from children under age 13.
Second, carefully review your information practices and your online privacy policy. In conducting your review, look closely at what information you collect, how you collect it, how you use it, whether the information is necessary for the activities on your site or online service, whether you have adequate mechanisms for providing parents with notice and obtaining verifiable consent, whether you have adequate methods for parents to review and delete their children’s information, and whether you employ adequate data security, retention, and deletion practices.
Educational materials aimed at operators of websites and online services are available in the Children’s Privacy section of the FTC’s Business Center, including Children’s Online Privacy Protection Rule: Six Step Compliance Plan for Your Business. See also Marketing Your Mobile App: Get it Right From the Start. These materials can provide you with helpful guidance. You might also choose to consult with one of the Commission-approved COPPA Safe Harbor Programs or seek the advice of counsel.
COPPA expressly states that the law applies to commercial websites and online services and not to nonprofit entities that otherwise would be exempt from coverage under Section 5 of the FTC Act. In general, because many types of nonprofit entities are not subject to Section 5 of the FTC Act, these entities are not subject to the Rule. However, nonprofit entities that operate for the profit of their commercial members may be subject to the Rule. See FTC v. California Dental Association, 526 U.S. 756 (1999). Although nonprofit entities generally are not subject to COPPA, the FTC encourages such entities to post privacy policies online and to provide COPPA’s protections to their child visitors.
As a matter of federal policy, all websites and online services operated by the Federal Government and contractors operating on behalf of federal agencies must comply with the standards set forth in COPPA. See OMB Guidance for Implementing the Privacy Provisions of the E-Government Act of 2002 (Sept. 2003).
Foreign-based websites and online services must comply with COPPA if they are directed to children in the United States, or if they knowingly collect personal information from children in the U.S. The law’s definition of “operator” includes foreign-based websites and online services that are involved in commerce in the United States or its territories. As a related matter, U.S.-based sites and services that collect information from foreign children also are subject to COPPA.
COPPA applies only to those websites and online services that collect, use, or disclose personal information from children. However, the FTC recommends that all websites and online services - particularly those directed to children - post privacy policies online so visitors can easily learn about the operator’s information practices. See Mobile Apps for Kids: Disclosures Still Not Making the Grade (Dec. 2012) and Mobile Apps for Kids: Current Privacy Disclosures are Disappointing (Feb. 2012).
Section 312.4(d) of the Rule identifies the three categories of information that you must disclose in your online privacy policy:
No. The Rule requires that privacy policies must be “clearly and understandably written, complete, and must contain no unrelated, confusing, or contradictory materials.” See 16 C.F.R. § 312.4(a) (“General principles of notice”).
The Rule provides that, if there are multiple operators collecting information through your site (including via plug-ins), you may list the name, address, phone number, and email address of one operator who will respond to all inquiries from parents regarding all of the operators’ privacy policies and use of children’s information, as long as the names of all the operators are also listed in this online notice. See 16 C.F.R. § 312.4(d)(1). If you wish to keep your online privacy policy simple, you may include a clear and prominent link in the privacy policy to the complete list of operators, as opposed to listing every operator in the policy itself. You must ensure, however, that your privacy policy signals parents to, and enables them easily to access, this list of operators. See .com Disclosures: How to Make Effective Disclosures in Digital Advertising (Mar. 2013), at ii.
The Rule defines “personal information” to include persistent identifiers, such as a customer number held in a cookie, an IP address, a processor or device serial number, or a unique device identifier that can be used to recognize a user over time and across different websites or online services. Therefore, you will need to disclose in your privacy policy (see FAQ C.2), and in your direct notice to parents (see FAQ C.9), your collection, use or disclosure of such persistent identifiers unless (1) you collect no other “personal information,” and (2) such persistent identifiers are collected on or through your site or service solely for the purpose of providing “support for the internal operations” of your site or service. For more detailed information about activities considered support for internal operations, see FAQs J.5-8, below.
The Rule requires that the operator post a clearly and prominently labeled link to the online privacy policy on the home or landing page or screen of the website or online service, and at each area of the site or service where personal information is collected from children. This link must be in close proximity to the requests for information in each such area. 16 C.F.R. § 312.4(d). In addition, an operator of a general audience website or online service that has a separate children’s area must post a link to its notice of information practices with regard to children on the home or landing page or screen of the children’s area. See 16 C.F.R. § 312.4(d).
In the case of an app, the link to the privacy policy must be on the home page of the app. The Rule does not mandate that a privacy policy be posted at the point of purchase, such as in the app store. However, there is a substantial benefit in providing greater transparency about the data practices and interactive features of child-directed apps at the point of purchase and we encourage it as a best practice. In fact, the FTC Staff Report, Mobile Apps for Kids: Disclosures Still Not Making the Grade (Dec. 2012), notes that “information provided prior to download is most useful in parents’ decision-making since, once an app is downloaded, the parent already may have paid for the app. . .” See p. 7. In addition, if a child-directed app were designed to collect personal information as soon as it is downloaded, it would be necessary to provide the direct notice and obtain verifiable consent at the point of purchase or to insert a landing page where a parent can receive notice and give consent before the download is complete.
The Rule states that the “operator must post a prominent and clearly labeled link to an online notice of its information practices with regard to children on the home or landing page or screen of its Web site or online service, and, at each area of the Web site or online service where personal information is collected from children.” 16 C.F.R. § 312.4(d). In the 1999 Statement of Basis and Purpose, the Commission explained that “‘clear and prominent’ means that the link must stand out and be noticeable to the site’s visitors through use, for example, of a larger font size in a different color on a contrasting background. The Commission does not consider ‘clear and prominent’ a link that is in small print at the bottom of the home page, or a link that is indistinguishable from a number of other, adjacent links.” See 64 Fed. Reg. 59888, 59894. A link that is at the bottom of the page may be acceptable if the manner in which it is presented makes it clear and prominent.
In the 1999 Statement of Basis and Purpose, the Commission noted that “operators are free to combine the privacy policies into one document, as long as the link for the children’s policy takes visitors directly to the point in the document where the operator’s policies with respect to children are discussed, or it is clearly disclosed at the top of the notice that there is a specific section discussing the operator’s information practices with regard to children.” See 64 Fed. Reg. 59888, 59894 n.98. This advice remains in effect. Operators should also ensure that the link for the children’s portion of the privacy policy appears on the home page or screen of the children’s area of the site or service, and at each area where personal information is collected from children. See 16 C.F.R. § 312.4(d).
The Rule requires operators to make reasonable efforts, taking into account available technology, to ensure that a parent of a child receives direct notice of the operator’s practices with regard to the collection, use, or disclosure of personal information from children, including notice of any material changes to practices to which the parent previously consented. The Rule provides a very detailed roadmap of what information must be included in your direct notice in four specific instances.
First: Where an operator collects the name or online contact information of a parent or child in order to obtain a parent’s verifiable consent prior to the collection, use, or disclosure of a child’s personal information. In this case, the direct notice must:
Second: Where an operator voluntarily seeks to provide notice to a parent of a child’s online activities that do not involve the collection, use or disclosure of personal information. In this case, the direct notice must:
Third: Where an operator intends to communicate with the child multiple times via the child’s online contact information and collects no other information. In this case, the direct notice must:
Fourth: Where the operator’s purpose for collecting a child’s and a parent’s name and online contact information is to protect a child’s safety and the information is not used or disclosed for any other purpose. In this case, the direct notice must:
No. As described in FAQ C.9 above, the Rule makes clear that the direct notice to parents must contain certain key information within the four corners of the notice itself, depending on the purpose for which the information is being collected. Therefore, you may not simply link to a separate online notice. Note, however, that the Rule requires that each direct notice you send also contain a link to your online privacy policy. The intention is to help ensure that the direct notice functions as an effective “just-in-time” message to parents about an operator’s information practices, while also directing parents online to view any additional information contained in the operator’s online notice.
Unless one of the limited exceptions applies (see FAQ I.2), the Rule requires that you send parents the direct notice prior to the collection of any personal information from the child. The limited exception to this is that you may collect the parent’s online contact information for the sole purpose of sending the parent the direct notice. Alternatively, you may provide the direct notice to the parent through other means, such as through the device onto which the app is downloaded, if the mechanisms both (1) provide such notice and obtain the parent’s consent before any collection of personal information and (2) are reasonably designed to ensure that it is the parent who receives the notice and provides the consent.
The Rule sets out a number of factors for determining whether a website or online service is directed to children. These include:
See 16 C.F.R. § 312.2 (definition of “Web site or online service directed to children,” paragraph (1)).
As described in FAQ E.1 below, the Rule also considers a website or online service to be “directed to children” where it has actual knowledge that it is collecting personal information directly from users of another website or online service that is directed to children. See 16 C.F.R. § 312.2 (definition of “Web site or online service directed to children,” paragraph (2)).
It depends. COPPA applies to commercial websites and online services that are directed to children. If the content you post on the platform is directed to kids, and personal information is collected by you or on your behalf (such as a persistent identifier used to serve targeted advertising), you will be deemed an operator of an online service that needs to comply with COPPA. By the same token, if the platform has actual knowledge that your content is directed to children and is collecting personal information, it will also need to comply with COPPA.
The Rule sets out a number of factors for determining whether a website or online service is directed to children (See FAQ D.1). The FTC staff recognizes that the determination of whether content is child-directed will be clearer in some contexts than in others. We can, however, provide some general guidance.
Unfortunately, the FTC cannot provide an opinion on whether a specific site or service is directed to children. If you continue to have questions about whether your content is directed to children, consider contacting an attorney or consulting one of the COPPA Safe Harbor programs - self-regulatory groups that offer guidance on how operators can comply with the law.
It depends. Because of its very nature, in most instances, a website or online service (such as an app) directed to children must treat all visitors as children and provide COPPA’s protections to every such visitor. This means that for the most part, a website or online service directed to children may not screen users for age.
However, the Rule provides a narrow exception for a site or service that may be directed to children under the criteria set forth in FAQ D.1 above, but that does not target children as its primary audience (sometimes referred to as “mixed audience”). If your site or service targets children under age 13, but children under 13 are not your primary audience (e.g., your site also targets adults or older teens), you can take advantage of this exception. You can implement an age screen; for users who indicate they are children under 13, you can ensure that you do not collect personal information from those users, or you can obtain verifiable parental consent. It is important to emphasize that the “mixed audience” category is a subset of the “directed to children” category, and a general audience site does not become “mixed audience” just because some children use the site or service.
An operator of a site or service meeting this standard may age-screen its users if it: (1) does not collect personal information from any visitor prior to collecting age information, and (2) prevents the collection, use, or disclosure of personal information from visitors who identify themselves as under age 13 without first complying with the Rule’s notice and parental consent provisions. See 16 C.F.R. § 312.2 (definition of “Web site or online service directed to children,” paragraph (3)). Keep in mind that unlike a general audience website or service, as an operator of a website or online service directed to children, you may not block children from participating in the website or online service.
As the operator, you should carefully analyze who your intended audience is, the actual audience, and in many instances, the likely audience for your website or online service. In making these determinations, you should keep in mind the factors for a “Web site or online service directed to children” contained in paragraph (1) of 16 C.F.R. § 312.2. See FAQ D.1 and D.3 above. You may also get a better sense of your site or service once it has been in operation, and may need to make some changes accordingly.
No. If your site is “mixed audience” (i.e., it falls within the definition of a “Web site or online service directed to children” as set forth in paragraph (3) of 16 C.F.R. § 312.2), then you may age screen your users, but you may not block children from participating altogether. Instead, the Rule permits you to use an age screen in order to differentiate between users under age 13 and other users. You may decide to offer different activities, or functions, to your users depending upon age, but you may not collect personal information from users who have indicated they are under 13 without first obtaining verifiable parental consent.
In designing your age screen, you should ask age information in a neutral manner, making sure the data entry point allows users to enter their age accurately and does not default to an age 13 or over. An example of a neutral age screen would be a system that allows a user freely to enter the month and year of birth. Avoid encouraging children to falsify age information by, for example, stating that certain features will not be available to users under age 13. In addition, consistent with long standing Commission advice, FTC staff recommends using technical means, such as a cookie, to prevent children from back-buttoning to enter a different age.
No. Requiring a child to answer a question he or she is unlikely to be able to answer, without more, is inadequate for determining the age of the user. There are many children under 13, for example, that can perform complex math problems, and some users over 13 that may have difficulty with those same complex problems. You may, however, use a math problem in addition to asking the age of the user, as described in FAQ D.7 above.
The Rule does not require you to inform third parties of the child-directed nature of your site or service, and doing so, without more, will not relieve you of your obligations under COPPA. Remember, you are responsible for the collection of personal information from your users, no matter who is doing the collection; therefore, you will need to do more than simply identify yourself to third parties. As a child-directed property, absent an exception under the Rule (see FAQ I.2 below), you must: (1) not collect or allow any other entity to collect personal information from your visitors; or (2) provide notice and obtain prior parental consent before collecting or allowing any entity to collect personal information from your visitors, as well as provide all of the other COPPA protections. In addition, Commission staff recommends that operators of child-directed websites or services signal their status to third parties and you may arrange with the third party collecting the personal information to provide adequate COPPA protections.
There are a number of questions you must find answers to before you enter into an arrangement with any entity to serve advertising to run on your child-directed sites and services. These include:
You should make informed decisions before you permit advertising to run on your sites and services. Depending on what advertising choices you make, you may be required to notify parents in your online privacy policies and in a direct notice, and obtain verifiable parental consent, before you permit advertising to occur. Remember that the Rule holds you liable for the collection of information that occurs on or through your sites and services, even if you yourself do not engage in such collection.
Yes. As the operator of a child-directed app, you must conduct an inquiry into the information collection practices of every third party that can collect information via your app. You need to determine each third party’s information collection practices so that you can make an informed decision as to whether its presence on your app will require you to give parents notice and obtain their consent prior to their collection of personal information from children. See FAQ D.9 above.
Yes. The COPPA rule defines “collection” to include requesting, prompting, or encouraging a child to submit personal information online, and enabling a child to make personal information publicly available in identifiable form. In addition, under the COPPA Rule, “disclosure” includes making a child’s personal information publicly available in identifiable form through an email service or other means, such as a social network. You must get verifiable parental consent before enabling children to share personal information in this manner, even through third parties on your app. This is true unless an exception applies. (See Section I, Exceptions to Prior Parental Consent). However, in the situation you describe — where a child can email a painting and a message or post content on his or her social networking page through your app — no exception applies.
The circumstances under which you will be deemed to have acquired “actual knowledge” that you have collected personal information directly from users of a child-directed site or service will depend a lot on the particular facts of your situation. In the 2013 Statement of Basis and Purpose, the Commission set forth two cases where it believes that the actual knowledge standard will likely be met:
Under the first scenario, any direct communications that the child-directed provider has with you that indicate the child-directed nature of its content would give rise to actual knowledge. In addition, if a formal industry standard or convention is developed through which a site or service could signal its child-directed status to you, that would give rise to actual knowledge. Under the second scenario, whether a particular individual can obtain actual knowledge on behalf of your business depends on the facts. Prominently disclosing on your site or service methods by which individuals can contact your business with COPPA information - such as: 1) contact information for designated individuals, 2) a specific phone number, and/or 3) an online form or email address - will reduce the likelihood that you would be deemed to have gained actual knowledge through other employees. (See also FAQ E.2 below).
It’s unlikely the receipt of a list of purportedly child-directed websites alone would constitute actual knowledge. You would have no duty to investigate. It's possible, however, that you will receive screenshots or other forms of concrete information that do give you actual knowledge that the website is directed at children. If you receive information and are uncertain whether the site is child-directed, you may ordinarily rely on a specific affirmative representation from the website operator that its content is not child-directed. For this purpose, a website operator would not be deemed to have provided a specific affirmative representation if it merely accepts a standard provision in your Terms of Service stating that, by incorporating your code, the first party agrees that it is not child directed.
Such a system could provide more certainty for you. If the system requires the first-party site to affirmatively certify whether it is “child-directed” or “not child-directed,” and the site signals that it is “not child-directed,” you may ordinarily rely on such a representation. Such reliance is advisable, however, only if first parties affirmatively signal that their sites or services are “not child-directed." You could not set that option for them as the default.
Remember, though, that you may still be faced with screenshots or other concrete information that gives you actual knowledge of the child-directed nature of the website despite a contradictory representation by the site. If, however, such information is inconclusive, you may ordinarily continue to rely on a specific affirmative representation made through a system that meets the criteria above.
Yes. The Rule considers photos, videos, and audio recordings that contain a child’s image or voice to be personal information. This means that prior to posting photos, videos, and audio recordings that contain a child’s image or voice, operators covered by COPPA must either (i) prescreen and delete from children’s submissions any photos, videos, or audio recordings of themselves or other children or (ii), first give parents notice and obtain their consent prior to permitting children to upload any photos, videos, or audio recordings of themselves or other children.
COPPA applies to photos, videos, and audio files that contain children’s images or voices. It also applies to geolocation data contained in these files sufficient to identify street name and name of city or town. Finally, it applies to any persistent identifiers collected via the children’s upload of their photos. Therefore, in order to offer an app without parental notice and consent, the operator must take the following steps:
An operator of a site directed to children does not need to notify parents or obtain their consent if it blurs the facial features of children in photos before posting them on its website. See 2013 Statement of Basis and Purpose, 78 Fed. Reg. 3972, 3982 n.123. The same goes for a site that has actual knowledge it has collected the photos from children. Before posting such photos, however, the operator must also remove any other personal information they contain, such as geolocation metadata, and ensure that it is not using or disclosing persistent identifiers collected from children in a manner that violates the Rule.
COPPA only covers information collected online from children. It does not cover information collected from adults that may pertain to children. Thus, COPPA is not triggered by (1) an adult uploading photos of children on a general audience site, (2) an adult uploading photos of children in the non-child directed portion of an otherwise child-directed website (e.g., a parent’s corner), or (3) an age-screened user (age 13 or older) uploading photos of children on a mixed audience site or service.
However, operators of websites or online services that are primarily directed to children (as defined by the Rule) must assume that the person uploading a photo is a child and they must design their systems either to: (1) give notice and obtain prior parental consent, or (2) remove any child images and metadata prior to posting.
No. You are not collecting personal information simply because your app interacts with personal information that is stored on the device and is never transmitted.
It depends. Audio files of a child’s voice, like photographs and videos containing a child’s image, are personal information in and of themselves and require verifiable parental consent. However, the Commission has issued an enforcement policy statement that states that when an operator collects an audio file containing a child’s voice solely as a replacement for written words, such as to perform a search or fulfill a verbal instruction or request, and only maintains the file for the brief time necessary for that purpose, the FTC will not take an enforcement action against the operator for failing to obtain parental consent. The operator must, however, provide a clear online notice of its collection, use, and deletion policy regarding these audio files. The Commission reasoned that, where an operator collects an audio file in these circumstances, there is little risk that the file will be used to contact an individual child.
There are limitations on this non-enforcement policy. First, this policy is not applicable when the operator requests information via voice that otherwise would be considered personal information under the Rule, such as a name. Second, as described above, the operator must provide clear notice of its information, use, and deletion policy for these audio files in its privacy policy. Third, the operator may not make any other use of the audio file in the brief period before the file is destroyed. Finally, this policy does not affect the operator’s COPPA compliance requirements in any other respect. In other words, if the operator is collecting other types of personal information, it must obtain verifiable parental consent.
Yes. COPPA covers the collection of geolocation information, not just its use or disclosure.
COPPA is designed to notify parents and give them the choice to consent. Therefore, it is not sufficient to provide such notification and choice to the child user of a website or service. If the operator intends to collect geolocation information, the operator will be responsible for notifying parents and obtaining their consent prior to such collection.
COPPA does not require an operator to notify parents and obtain their consent before collecting the type of coarse geolocation services described. However, the operator should be quite certain that, in all instances, the geolocation information it collects is more general than that sufficient to identify street name and name of city or town.
COPPA covers the collection of geolocation information “sufficient” to identify street name and name of city or town. COPPA applies even if the child is not asked to provide an actual street address. For example, COPPA would apply if an app collects the user’s longitude and latitude. Similarly, the Commission alleged that COPPA applied in United States v. InMobi Pte Ltd., where the company collected wireless network identifiers to infer the child’s precise location without providing notice or obtaining verifiable parental consent.
The Rule does not require operators of general audience sites to investigate the ages of visitors to their sites or services. See 1999 Statement of Basis and Purpose, 64 Fed. Reg. 59888, 59892. However, operators will be held to have acquired actual knowledge of having collected personal information from a child where, for example, they later learn of a child’s age or grade from a concerned parent who has learned that his child is participating on the site or service.
COPPA applies to websites and online services that are directed to children under 13. However, although you may intend to operate a “teen service,” in reality, your site may attract a substantial number of children under 13, and thus may be considered a “Web site or online service directed to children” under the Rule. Just as the Commission considers several factors in determining whether a site or service is directed to children, you too should consider your service’s subject matter, visual content, character choices, music, and language, among other things. If your service targets children as one of its audiences - even if children are not the primary audience - then your service is “directed to children.” If children are not your primary audience, however, you may employ a neutral age screen in order to provide COPPA’s protections to only those visitors who indicate they are under age 13. See Section D above for more information on mixed audience sites. Note that sites or services directed to children cannot use the age screen to block children under age 13. See FAQ D.4 above. Once you identify child visitors, you may choose to:
Yes. COPPA does not require you to permit children under age 13 to participate in your general audience website or online service, and you may block children from participating if you so choose. By contrast, you may not block children from participating in a website or online service that is directed to children as defined by the Rule, even if the website or online service is also directed to users age 13 or older. See FAQ D.4 above.
If you choose to block children under 13 on your general audience site or service, you should take care to design your age screen in a manner that does not encourage children to falsify their ages to gain access to your site or service. Ask age information in a neutral manner at the point at which you invite visitors to provide personal information or to create a user ID.
In designing a neutral age-screening mechanism, you should consider:
In addition, consistent with long standing Commission advice, FTC staff recommends using a cookie to prevent children from back-buttoning to enter a different age. Note that if you ask participants to enter age information, and then you fail either to screen out children under age 13 or to obtain their parents’ consent to collecting these children’s personal information, you may be liable for violating COPPA. See, e.g., the FTC’s COPPA cases against Path, Inc., Playdom, Inc., Sony BMG Music Entertainment, and Yelp.
Under the Rule’s one-time response exception (16 C.F.R. § 312.5(c)(3)) you are permitted to send a response to the child, via the child’s online contact information, without sending notice to the parent or obtaining parental consent. However, you must delete the child’s online contact information from your records promptly after you send your response. You may not use the child’s online contact information to re-contact the child (or for any other purpose), or disclose the child’s online contact information. Note that if you choose not to respond to the child’s inquiry, you must still immediately delete the child’s personal information from your records. Additionally, such an email may give you actual knowledge that you have collected personal information from a child (e.g., if you had previously collected the child’s email address as part of a website registration process). In such a circumstance, you would need to take steps to ensure that you are complying with COPPA, such as obtaining parental consent or immediately deleting any personal information collected from the child.
In determining whether a website or online service is directed to children, you should carefully consider the factors set forth in the Rule, including the subject matter of the game, visual content, use of animated characters or child-oriented activities and incentives, music or other audio content, age of models, presence of child celebrities or celebrities who appeal to children, language or other characteristics of the website or online service, and whether advertising promoting or appearing on the site or service is directed to children. You should also consider any competent and empirical evidence regarding your audience composition, and who your intended audience is. The Commission considers the totality of the circumstances in determining whether a website or online service is directed to children, and no single factor is determinative. If after considering these factors you determine that your site or service is directed to children, then you can separately determine whether your site falls in the “mixed audience” subcategory - i.e., whether children are not your primary audience.
Importantly, “mixed audience” sites or services are a subcategory of “directed to children.” In other words, a website or online service that is appealing to all ages and not specifically directed at children is not deemed “mixed audience” simply because some children may use the site or service. In determining whether your site or service is mixed audience, you should consider your intended audience (are you marketing to under 13 users, such as through selling related toys, for example). You should also determine whether your site or service involves child-oriented activities, such as a dress up game, and whether you have empirical evidence as to the actual users of your video game site. If you continue to have questions about whether your content is mixed audience, consider contacting an attorney or consulting one of the COPPA Safe Harbor programs - self-regulatory groups that offer guidance on how operators can comply with the law.
The COPPA Rule applies to an operator of a general audience website if it has actual knowledge that a particular visitor is a child. If a child posts personal information on a general audience site or service but does not reveal her age, and if the operator has no other information that would lead it to know that the visitor is a child (such as the child posting that she attends an elementary school), then the operator would not be deemed to have acquired “actual knowledge” under the Rule and would not be subject to the Rule’s requirements.
Even where the child does reveal age-identifying information, if no one in your organization is aware of the post, then you may not have the requisite actual knowledge under the Rule. However, you may be considered to have actual knowledge where a child announces her age under certain circumstances, for example, if you monitor user posts, if a responsible member of your organization sees the post, or if someone alerts you to the post (e.g., a concerned parent who learns that his child is participating on your site). Where an operator knows that a particular visitor is a child, the operator must either meet COPPA’s notice and parental consent requirements or delete the child’s information.
The Rule provides generally that an operator must obtain verifiable parental consent before collecting any personal information from a child, unless the collection fits into one of the Rule’s exceptions described in various FAQs herein. See 16 C.F.R. § 312.5(c).
As a general rule, operators must get verifiable parental consent before collecting personal information online from children under 13. Certain, limited exceptions let operators collect certain personal information from a child before obtaining parental consent. See 16 C.F.R. § 312.5(c). These exceptions include:
It depends. First, you should determine whether the information you collect falls within one of the Rule’s limited exceptions to parental consent outlined in FAQ I.2 above. If you fall outside of one of those exceptions, you must notify parents and obtain their consent. However, if you only use the information internally, and do not disclose it to third parties or make it publicly available, then you may obtain parental consent through use of the Rule’s “email plus” mechanism, as outlined in FAQ I.4 below. See 16 C.F.R. § 312.5(b)(2).
You may use any number of methods to obtain verifiable parental consent, as long as the method you choose is reasonably calculated to ensure that the person providing consent is the child’s parent. The Rule sets forth several non-exhaustive options, and you can apply to the FTC for pre-approval of a new consent mechanism, as set out in FAQ I.12 below.
If you are going to disclose children’s personal information to third parties, or allow children to make it publicly available (e.g., through a social networking service, online forums, or personal profiles) then you must use a method that is reasonably calculated, in light of available technology, to ensure that the person providing consent is the child’s parent. Specific methods identified in the Rule or otherwise approved by the Commission include:
It depends. The general rule is that any parental consent mechanism “must be reasonably calculated, in light of available technology, to ensure that the person providing consent is the child’s parent.” The Rule lists several methods that automatically meet this standard, one of which is the use of a credit card, debit card, or other online payment system in connection with a monetary transaction. Importantly, the listed methods are not exhaustive; you may use other methods as long as they are “reasonably calculated” to ensure that the consent is being provided by the parent. Although collecting a 16-digit credit or debit card number alone would not satisfy the method listed in the Rule, there may be circumstances in which collection of the card number - in conjunction with implementing other safeguards - would suffice to meet the standard for verifiable parental consent. For example, you could supplement the request for credit card information with special questions to which only parents would know the answer and find supplemental ways to contact the parent.
No. By providing appropriate notice and obtaining consent in connection with the Rule’s proper use of a credit card or government identification, the operator will be deemed to fulfill its obligation under the Rule.
Many operators find it useful to offer a choice of consent methods for those parents who cannot, or will not, use their primary consent mechanism. At the very least, you might consider offering one alternate method that parents might be more comfortable with, such as a print-and-send form.
Once you have notified a parent and obtained verifiable consent, providing a password or a PIN number is a good way to confirm a parent’s identity for any future contact you might have with that parent. Remember that if you change your information practices in a material way in the future, you will have to send a new parental notice and obtain an updated consent to the new practices. Obtaining an updated consent may be easier if you have given the parent a password or a PIN number in your initial consent process.
In addition, the Rule requires you to give a parent access to any personal information you have collected from the child. Before you provide that information, you will need to confirm that the person requesting the information is the child’s parent. Again, providing the parent a password or a PIN number makes it easier to confirm the parent’s identity if the parent requests access to the child’s personal information.
The Rule requires an operator to give parents the option to consent to the collection and use of a child’s personal information without consenting to the disclosure of such information to third parties. See 16 C.F.R. § 312.5(a)(2). However, an operator need provide this choice only where the disclosure of the information is not inherent in the activity to which the parent is consenting.
You should note that the Rule’s definition of “disclosure” is broader than merely “releasing” personal information to third parties. Under the Rule, “disclosure” includes “[m]aking personal information collected by an operator from a child publicly available in identifiable form by any means, including but not limited to a public posting through the Internet, or through a personal home page or screen posted on a website or online service; a pen pal service; an electronic mail service; a message board; or a chat room.” See 16 C.F.R. § 312.2.
In the case of social networking sites, chat rooms, message boards, and other similar online services, sharing personal information is a central feature of the site. Therefore, in these cases, you are not required to give parents the choice to allow you to collect and use their children’s personal information, but not disclose it to third parties. However, you must clearly disclose your information collection, use, and disclosure practices in your direct notice and online privacy policy so that parents can make an informed decision about their children’s participation in your site or service.
Yes. The Commission recognized in the 2013 Statement of Basis and Purpose that common consent mechanisms, such as one done through an app store or other platform, could benefit operators (especially smaller ones) and parents if they offer a proper means for providing notice and obtaining verifiable parental consent, as well as ongoing controls for parents to manage their children’s accounts. See 78 Fed. Reg. 3972, 3989. When using a common consent method, however, you must ensure that COPPA requirements are being met. For example, you must make sure that the third party is obtaining consent in a way that is reasonably calculated, in light of available technology, to ensure that the person providing consent is the child’s parent. The mere entry of an app store account number or password, for example, without other indicia of reliability (e.g., knowledge-based authentication questions or verification of government identification), does not provide sufficient assurance that the person entering the account or password information is the parent, and not the child. In addition, as the operator, you are responsible for ensuring that your direct notice accurately and completely reflects your information collection practices.
The Rule permits you to collect the parent’s “online contact information,” defined as an email address, an IM user identifier, a VOIP identifier, a video chat user identifier, or other substantially similar identifier. A mobile phone number is not online contact information and therefore cannot be collected from the child as part of the consent initiation process. However, once you have connected with the parent via the parent’s online contact information, you may request a parent’s mobile phone number in order to further communicate with him or her.
Yes. The Rule provides a mechanism for interested parties to file a written request for Commission approval of parental consent methods not currently enumerated in 16 C.F.R. § 312.5(b). See 16 C.F.R. § 312.12(a). See FTC’s Verifiable Parental Consent page for information on previous requests.
The Commission recognized this concern in the 2013 Statement of Basis and Purpose, noting that, “just as the Commission has done for COPPA safe harbor applicants, it would permit those entities that voluntarily seek approval of consent mechanisms to seek confidential treatment for those portions of their applications that they believe warrant trade secret protection. In the event an applicant is not comfortable with the Commission’s determination as to which materials will be placed on the public record, it will be free to withdraw the proposal from the approval process.” See 78 Fed. Reg. 3972, 3992.
The Commission recognized in the 2013 Statement of Basis and Purpose that platform methods of parental consent could benefit operators (especially smaller ones) and parents, and has made clear that operators may use one so long as it meets the Rule’s notice and consent requirements. See 78 Fed. Reg. 3972, 3989. To the extent you are simply providing a verifiable parental consent mechanism - and are therefore not an “operator” under COPPA - you will not be liable under COPPA for failing to investigate the privacy practices of the operators for whom you obtain consent. At the same time, you should also evaluate your potential liability under Section 5 of the FTC Act. For example, it could be a deceptive practice to misrepresent the level of oversight you provide for a child-directed app.
Yes, if you properly design your contest. You may use the “one time contact” exception if you collect children’s online contact information, and only this information, to enter them in the contest, and then only contact such children once when the contest ends to notify them if they have won or lost. At that point, you must delete the online contact information you have collected.
If, however, you expect to contact the children more than one time, you must use the “multiple-contact” exception, for which you must also collect a parent’s online contact information and provide parents with direct notice of your information practices and an opportunity to opt out. In either case, the Rule prohibits you from using the children’s online contact information for any other purpose, and requires you to ensure the security of the information, which is particularly important if the contest runs for any length of time.
If you wish to collect any information from children online beyond online contact information in connection with contest entries - such as collecting a winner’s home address to mail a prize - you must first provide parents with direct notice and obtain verifiable parental consent, as you would for other types of personal information collection beyond online contact information. If you do need to obtain a mailing address and wish to stay within the one-time exception, you may ask the child to provide his parent’s online contact information and use that identifier to notify the parent if the child wins the contest. In your prize notification message to the parent, you may ask the parent to provide a home mailing address to ship the prize, or invite the parent to call a telephone number to provide the mailing information.
If you simply answer the child’s question and then delete the child’s email address (and do not otherwise maintain or store the child’s personal information in any form), then you fall into the Rule’s “one-time contact” exception and do not need to obtain parental consent.
The answer depends on how you design your e-card or forward-to-a-friend system. Any system providing any opportunity to reveal personal information other than the recipient’s email address requires you to obtain verifiable consent from the sender’s parent (not email plus), and does not fall within one of COPPA’s limited exceptions. This means that if your e-card/forward-to-a-friend system permits personal information to be disclosed either in the “from” or “subject” lines, or in the body of the message, then you must notify the sender’s parent and obtain verifiable parental consent before collecting any personal information from the child.
In order to take advantage of COPPA’s “one-time contact exception” for your e-cards, you may only collect the recipient’s email address (and, if desired, the sender or recipient’s first name); you may not collect any other personal information either from the sender or the recipient, including persistent identifiers that track the user over time and across sites. Moreover, in order to meet this one-time contact exception, your e-card system must not allow the sender to enter her full name, her email address, or the recipient’s full name. Nor may you allow the sender to freely type messages either in the subject line or in any text fields of the e-card.
Finally, you should send the e-card immediately and automatically delete the recipient’s email address immediately after sending. If you choose to retain the recipient’s email address until some point in the future (e.g., until the e-card is opened by the recipient, or you allow the sender to indicate a date in the future when the e-card should be sent), then this collection parallels the conditions for the Rule’s “multiple contact exception” for obtaining verifiable parental consent. In this scenario, you must collect the sender’s parent’s email address and provide notice and an opportunity to opt out to the sender’s parent before the e-card is sent. See 1999 Statement of Basis and Purpose, 64 Fed. Reg. 59888, 59902 n.222.
If you plan to retain the child’s email address in retrievable form after the initial collection, to be used, for example, to email children reminders of their passwords, then you must provide notice to parents and the opportunity to opt out under the Rule’s multiple-contact exception. See 16 C.F.R. § 312.5(c)(4).
However, you may collect a child’s email address to be used to authenticate the child for purposes of generating a password reminder without first providing parental notice and giving a parent the opportunity to opt out if you meet the following conditions: (1) you do not collect any personal information from the child other than the child’s email address; (2) the child cannot disclose any personal information on your website; and (3) you immediately and permanently alter the email address (e.g., through “hashing”) such that it can only be used as a password reminder and cannot be reconstructed into its original form or used to contact the child. You should explain this process in a clear and conspicuous manner, both at the point of collection and in your site’s online privacy policy, so that your users and their parents are informed about how the email addresses will be used. This will prevent confusion by visitors and others who may otherwise assume that your site is improperly collecting and retaining email addresses without any form of parental notice.
“Support for the internal operations of the Web site or online service,” as defined in 16 C.F.R. 312.2, means activities necessary for the site or service to maintain or analyze its functioning; perform network communications; authenticate users or personalize content; serve contextual advertising or cap the frequency of advertising; protect the security or integrity of the user, website, or online service; ensure legal or regulatory compliance; or fulfill a request of a child as permitted by § 312.5(c)(3) and (4). The Commission has separately noted that encompassed within the activities necessary for the site or service to maintain or analyze its functioning are intellectual property protection, payment and delivery functions, spam protection, optimization, statistical reporting, and debugging. See 2013 Statement of Basis and Purpose, 78 Fed Reg. 3972, 3981. Persistent identifiers collected for the sole purpose of providing support for the internal operations of the website or online service do not require parental notice or consent, so long as no other personal information is collected and the persistent identifiers are not used or disclosed to contact a specific individual, including through behavioral advertising; to amass a profile on a specific individual; or for any other purpose.
Yes. A child-directed site and a third-party plug-in collecting persistent identifiers from users of that child-directed site can both rely upon the Rule’s “support for internal operations” exception where the only personal information collected from such users are persistent identifiers for purposes outlined in the “support for internal operations” definition. The persistent identifier information collected by the third-party plug-in may in some instances support only the plug-in’s internal operations; in other instances, it may support both its own internal operations and the internal operations of the child-directed site.
Yes. Where you, a service provider, or a third party collects persistent identifier information from users of your child-directed site to perform analytics encompassed by the Rule’s “support for internal operations” definition, and the information is not used for any other purposes not covered by the support for internal operations definition, then you can rely upon the Rule’s exemption from parental consent.
No. The term “support for internal operations” does not include behavioral advertising. The inclusion of personalization within the definition of support for internal operations was intended to permit operators to maintain user driven preferences, such as game scores, or character choices in virtual worlds. “Support for internal operations” does, however, include the collection or use of persistent identifiers in connection with serving contextual advertising on the child-directed site.
The information you collect from the child’s device used to send push notifications is online contact information - it permits you to contact the user - and is therefore personal information under the Rule. To the extent the child has specifically requested push notifications, however, you may be able to rely on the “multiple-contact” exception to verifiable parental consent, for which you must also collect a parent’s online contact information and provide parents with direct notice of your information practices and an opportunity to opt-out. See FAQ I.2. Importantly, in order to fit within this exception, your push notifications must be reasonably related to the content of your app. If you want to combine this online contact information with other personal information collected from the child, you cannot rely on this exception and must provide parents with direct notice and obtain verifiable parental consent prior to sending push notifications to the child.
In determining whether you must provide notice and obtain verifiable parental consent, you will need to evaluate whether any exceptions apply. Section 312.5(c)(8) of the Rule has an exception to its notice and consent requirements where:
If the third-party operator meets all of those requirements, and if your site doesn't collect personal information (except for that covered by an exception), you don't need to provide notice or obtain consent.
This exception doesn't apply to types of plug-ins where the third party collects more information than a persistent identifier — for example, where the third party also collects user comments or other user-generated content. In addition, a child-directed website can’t rely on this exception to treat particular visitors as adults and track their activities.
If your inclusion of the plug-in satisfies all the criteria of section 312.5(c)(8) outlined above and/or satisfies another exception to the notice and consent requirements in the Rule (see, for example, the “support for internal operations" exception discussed in FAQ J.5 and J.6 above), you do not have to provide notice and obtain verifiable parental consent.
No. In fact, the Rule specifically states that operators should retain personal information collected online from a child for only as long as is reasonably necessary to fulfill the purpose for which the information was collected. As the Commission noted in the 1999 Statement of Basis and Purpose, “if a parent seeks to review his child’s personal information after the operator has deleted it, the operator may simply reply that it no longer has any information concerning that child.” See 64 Fed. Reg. 59888, 59904.
The Rule requires you to provide parents with a means of reviewing any personal information you collect online from children. Although the Rule provides that the operator must ensure that the requestor is a parent of the child, it also notes that if you follow reasonable procedures in responding to a request for disclosure of this personal information, you will not be liable under any federal or state law if you mistakenly release a child’s personal information to a person other than the parent. See 16 C.F.R. § 312.6(a)(3)(i) and (b).
Before sharing information with such entities, you should determine what the service providers’ or third parties’ data practices are for maintaining the confidentiality and security of the data and preventing unauthorized access to or use of the information. Your expectations for the treatment of the data should be expressly addressed in any contracts that you have with service providers or third parties. In addition, you must use reasonable means, such as periodic monitoring, to confirm that any service providers or third parties with which you share children’s personal information maintain the confidentiality and security of that information.
Yes. If a parent revokes consent and directs you to delete the personal information you had collected from the child, you may terminate the child’s use of your service. See 16 C.F.R. § 312.6(c).
Yes. The applicable Rule provision is not limited to games or prize offerings, but includes “another activity.” See 16 C.F.R. § 312.7. This means that you must carefully examine the information you intend to collect in connection with every activity you offer in order to ensure that you are only collecting information that is reasonably necessary to participate in that activity. This guidance is in keeping with the Commission’s general guidance on data minimization. There are some sites or services, however, where the sharing of personal information is a central feature, such as social networking sites or chat rooms. This provision does not prohibit these types of sites from allowing children to share personal information. See FAQ I.9.
Yes. Many school districts contract with third-party website operators to offer online programs solely for the benefit of their students and for the school system - for example, homework help lines, individualized education modules, online research and organizational tools, or web-based testing services. In these cases, the schools may act as the parent’s agent and can consent under COPPA to the collection of kids’ information on the parent’s behalf. However, the school’s ability to consent for the parent is limited to the educational context - where an operator collects personal information from students for the use and benefit of the school, and for no other commercial purpose. Whether the website or app can rely on the school to provide consent is addressed in FAQ N.2. FAQ N.5 provides examples of other “commercial purposes.” Importantly, operators should not state in Terms of Service or anywhere else that the school is responsible for complying with COPPA, as it is the responsibility of the operator to comply with the Rule.
In order for the operator to rely on consent obtained from the school under COPPA instead of the parent, the operator must provide the school with the same type of direct notice regarding its practices as to the collection, use, or disclosure of personal information from children as it would otherwise provide to the parent. In addition, the operator, upon request from the school, must provide the school a description of the types of personal information collected; an opportunity to review the child’s personal information and the right to have the information deleted; and the opportunity to prevent further use or online collection of a child’s personal information. As long as the operator limits use of the child’s information to the educational context authorized by the school, the operator can presume that the school’s authorization is based on the school’s having obtained the parent’s consent. However, as a best practice, schools should consider making such notices available to parents, and consider the feasibility of allowing parents to review the personal information collected. See FAQ N.4. Schools also should ensure operators delete children’s personal information once the information is no longer needed for its educational purpose.
In addition, schools and operators should consider their obligations under the Family Educational Rights and Privacy Act (FERPA), which gives parents certain rights with respect to their children’s education records. FERPA provides parents with rights to access their student’s education records, protect against unauthorized disclosures of the personally identifiable information from those records, and other related rights. FERPA is administered by the U.S. Department of Education (ED) and applies to educational agencies and institutions that are funded by a program administered by ED. The school’s agreement with a third party operator must also be reviewed under the school official exception or other applicable exception under FERPA. For general information on FERPA, see https://studentprivacy.ed.gov/. Schools and operators also must comply with the Individuals with Disabilities Education Act and Protection of Pupil Rights Amendment (PPRA), which are also administered by ED. See https://studentprivacy.ed.gov/ and https://sites.ed.gov/idea/; see also FAQ N.5 for more information on the PPRA.)
Student data may be protected under state law, too. For example, California’s Student Online Personal Information Protection Act, among other things, places restrictions on the use of K-12 students’ information for targeted advertising, profiling, or onward disclosure. States such as Oklahoma, Idaho, and Arizona require educators to include express provisions in contracts with private vendors to safeguard privacy and security or to prohibit secondary uses of student data without parental consent.
Where a school has contracted with an operator to collect personal information from students for the use and benefit of the school, and for no other commercial purpose, the operator is not required to obtain consent directly from parents under COPPA, and can presume that the school’s authorization for the collection of students’ personal information is based upon the school having obtained the parents’ consent. However, the operator must provide the school with full notice of its collection, use, and disclosure practices in the same way that it is otherwise required to do for a parent.
If, however, an operator intends to use or disclose children’s personal information for its own commercial purposes in addition to the provision of services to the school, it will need to obtain parental consent. Operators may not use the personal information collected from children based on a school’s consent for another commercial purpose because the scope of the school’s authority to act on behalf of the parent is limited to the school context.
Where an operator gets consent from the school rather than the parent, the operator’s method must be reasonably calculated, in light of available technology, to ensure that a school is actually providing consent, and not a child pretending to be a teacher, for example.
As a best practice, we recommend that schools or school districts decide whether a particular site’s or service’s information practices are appropriate, rather than delegating that decision to the teacher. Many schools have a process for assessing sites’ and services’ practices so that this task does not fall on individual teachers’ shoulders. School districts and schools have separate specific obligations under FERPA. See https://studentprivacy.ed.gov for more information.
As a best practice, the school should consider providing parents with a notice of the websites and online services whose collection it has consented to on behalf of the parent under COPPA. Schools can identify, for example, sites and services that have been approved for use district-wide or for the particular school.
In addition, the school may want to make the operators’ direct notices regarding their information practices available to interested parents. Many school systems have implemented Acceptable Use Policies for Internet use (AUPs) to educate parents and students about in-school Internet use. The school could maintain this information on a website or provide a link to the information at the beginning of the school year. There are separate parent notification requirements under FERPA. See https://studentprivacy.ed.gov for more information.
In deciding whether to use online technologies with students, a school should be careful to understand how an operator will collect, use, and disclose personal information from its students. Among the questions that a school should ask potential operators are:
Schools also should keep in mind that under the Protection of Pupil Rights Amendment, Local Educational Agencies (LEAs) must adopt policies and must provide direct notification to parents at least annually regarding the specific or approximate dates of, and the rights of parents to opt their children out of participation in, activities involving the collection, disclosure, or use of personal information collected from students for the purpose of marketing or selling that information (or otherwise providing the information to others for that purpose).
To be considered for COPPA safe harbor status, an industry group or other person must submit its self-regulatory guidelines to the FTC for approval. The Rule requires the Commission to publish the safe harbor application in the Federal Register seeking public comment. The Commission then is required to make a written determination on the application within 180 days after its filing.
COPPA safe harbor applications must contain:
The Rule sets forth the key criteria the FTC will consider in reviewing a safe harbor application:
See 16 C.F.R. § 312.11.
Information about applying for FTC approval of a safe harbor program is provided in Section 312.11 of the Rule and online at the COPPA Safe Harbor Program portion of the FTC’s Business Center website. In addition, you may send an email to CoppaHotLine@ftc.gov, and a member of the FTC staff will help answer your questions.
Information about the applicants who have sought safe harbor status can be found online at the COPPA Safe Harbor Program portion of the FTC’s Business Center website. The site includes each organization’s applications and guidelines, along with comments submitted by the public, and the basis for the Commission’s written determination of each application.
The National Small Business Ombudsman and 10 Regional Fairness Boards collect comments from small businesses about federal compliance and enforcement activities. Each year, the Ombudsman evaluates the conduct of these activities and rates each agency’s responsiveness to small businesses. Small businesses can comment to the Ombudsman without fear of reprisal. To comment, call toll-free 1-888-REGFAIR (1-888-734-3247) or go to www.sba.gov/ombudsman.
[Note: Edited January 2025 to reflect Inflation-Adjusted Civil Penalty Maximums.]
Link nội dung: https://hnou.edu.vn/the-programme-invited-viewers-to-write-in-with-their-ideas-a23466.html