Also, his class had a WhatsApp group chat in which school info was shared. This was kind of weird because it meant that all 12 year olds in the group must have cheated their dates of birth, because otherwise they could not have had a WhatsApp account
https://www.ftc.gov/business-guidance/resources/complying-co...
>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:
>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 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.
>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.
Is "allowed" the right word, given "This document [...] is not binding", "guidance" and "should consider"?
On an unrelated note:
> 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.
So if 12-year-olds learn about a website they don't want their parents to ever visit, they just have to preemptively try to visit it from the same computer and tell the truth?