Is asking a website user their age the same as asking their birthdate?
<p>COPPA says you must ask a user's age in a neutral way. Most websites make you enter your birthdate to check whether you're old enough to be using it. But what if you just simply ask the user's age? That seems to be just as neutral as asking their birthdate. Legally speaking, is that the same?</p>

<p>Assume that there are no unique sections of the site. Only 13+ users are legally allowed on any given part.</p>

<p>The <em>Children's Online Privacy Protection Rule</em>, <a href="http://www.ecfr.gov/cgi-bin/text-idx?SID=4939e77c77a1a1a08c1cbf905fc4b409&amp;node=16%3A1.0.1.3.36&amp;rgn=div5#se16.1.312_111" rel="nofollow noreferrer">16 C.F.R. 312</a> (<strong>COPPR</strong>), which is a regulation issued by the Federal Trade Commission (<strong>FTC</strong>) under the <em>Children's Online Privacy Protection Act</em>, <a href="https://www.law.cornell.edu/uscode/text/15/chapter-91" rel="nofollow noreferrer">15 U.S.C. 91</a> (<strong>COPPA</strong>), applies to:</p>
<blockquote>
<p>... any operator of a Web site or online service directed to children [<em>under 13: see §312.2</em>], or any operator that has actual knowledge that it is collecting or maintaining personal information from a child ... [§312.3]</p>
</blockquote>
<p>Many operators simply choose to block children to avoid these obligations. <strong>The purpose of age-screening is to ensure that your website is not directed to children and that you are not knowingly collecting personal information from children</strong>. Whether your website falls into this category will depend on all the facts and circumstances. Your question about a website operator's obligation to &quot;ask a user's age in a neutral way&quot; is reflected in the FTC publication <em><a href="https://www.ftc.gov/tips-advice/business-center/guidance/complying-coppa-frequently-asked-questions" rel="nofollow noreferrer">Complying with COPPA: Frequently Asked Questions</a></em>, which states:</p>
<blockquote>
<p>If you choose to block children under 13 on your general audience site or service, you should take care to <strong>design your age screen in a manner that does not encourage children to falsify their ages</strong> 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.</p>
<p>In designing a neutral age-screening mechanism, you should consider:</p>
<ul>
<li><p>Making sure the data entry point allows users to enter their age accurately.  An example of a neutral age-screen would be a system that allows a user freely to enter month, day, and year of birth.  A site that includes a drop-down menu that only permits users to enter birth years making them 13 or older, would not be considered a neutral age-screening mechanism since children cannot enter their correct ages on that site.</p>
</li>
<li><p>Avoiding encouraging children to falsify their age information, for example, by stating that visitors under 13 cannot participate or should ask their parents before participating. In addition, simply including a check box stating, “I am over 12 years old” would not be considered a neutral age-screening mechanism.</p>
</li>
</ul>
<p>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.  <strong>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.</strong>  <em>See</em>, <em>e.g.</em>, the FTC’s COPPA cases against <a href="https://www.ftc.gov/enforcement/cases-proceedings/122-3158/path-inc" rel="nofollow noreferrer"><em>Path, Inc.</em></a>, <a href="https://www.ftc.gov/enforcement/cases-proceedings/1023036/playdom-inc" rel="nofollow noreferrer"><em>Playdom, Inc.</em></a> and <a href="https://www.ftc.gov/enforcement/cases-proceedings/082-3071/sony-bmg-music-entertainment-general-partnership-subsidiary" rel="nofollow noreferrer"><em>Sony BMG Music Entertainment</em></a>.</p>
</blockquote>
<p>None of the three cases cited in the last paragraph deal directly with the situation you have asked about, but they contain useful factual examples of how the law is actually applied, as well as a detailed legal complaint filed by the FTC which precisely sets out the legal basis for the defendants' alleged violations.</p>
<p>For example, the FTC's <a href="https://www.ftc.gov/enforcement/cases-proceedings/122-3158/path-inc" rel="nofollow noreferrer">case against <em>Path, Inc.</em></a> involved allegations that the operators of the <a href="https://en.wikipedia.org/wiki/Path_(social_network)" rel="nofollow noreferrer">Path social network</a> had violated various federal laws, including COPPR. The case was settled on <a href="https://www.ftc.gov/sites/default/files/documents/cases/2013/02/130201pathincdo.pdf" rel="nofollow noreferrer">terms</a> that Path admitted no wrongdoing but agreed to pay an $800,000 penalty. Count III of the FTC's <a href="https://www.ftc.gov/sites/default/files/documents/cases/2013/02/130201pathinccmpt.pdf" rel="nofollow noreferrer">complaint</a> sets out the COPPR allegations. Basically, Path asked users for their date of birth but then failed to actually block users under 13 or obtain verifiable parental consent.</p>
<p>In <a href="https://www.ftc.gov/enforcement/cases-proceedings/122-3158/path-inc" rel="nofollow noreferrer"><em>Path, Inc.</em></a>, <a href="https://www.ftc.gov/enforcement/cases-proceedings/1023036/playdom-inc" rel="nofollow noreferrer"><em>Playdom, Inc.</em></a> and <a href="https://www.ftc.gov/enforcement/cases-proceedings/082-3071/sony-bmg-music-entertainment-general-partnership-subsidiary" rel="nofollow noreferrer"><em>Sony BMG Music Entertainment</em></a>, it was clear that the defendants had actual knowledge that they were collecting information from children. These were not cases involving operators who were found to be subject to COPPR because their age-screening mechanism was not robust enough. However, it is difficult to go wrong by following the advice of the federal regulator.</p>
<p>The FTC says that an example of a neutral age-screen is one that allows a user freely to enter month, day and year of birth, and that a screen which only allows users to specify an age of 13 or older is not neutral. Your question falls in between these two extremes. There is no rule which makes it absolutely mandatory to ask for a full date of birth. What matters is that your website is not directed to children and that you are not knowingly collecting information from children. Obviously, it's safer to err on the side of caution and take the approach recommended by the FTC. If you don't want to follow the FTC's advice, you should take other active steps to ensure that your website is not directed to children and that you are not collecting personal information from children.</p>

united-states internet coppa