

Yeah I think the charitable way to read the law is that it requires OS, applications, etc to implement a standardized system for setting, requesting, and receiving age bracket data of a user. It doesn’t require anyone to use it. By defining user as under 18 for the purpose of this section it means nothing in the section applies to users over 18.
I get protesting about this because implementation is not trivial and there’s no time to do so. But creating a standard and all OS’s, websites, and relavent applications adopting that standard isn’t a bad thing (unrelated apps like text editors should clearly be exempt). It would make it way harder for kids to circumvent parental controls on a device.



Plus they also allow a user to present an age bracket of “over 18” despite defining users as under 18. I think they just did a bad job of clearly scoping it. It should be clear that it’s a tool for a parent to use and that it’s merely requiring that software implement age signaling all the way from OS to website to application. A default OS configuration should have no age defined and nothing should require an age to be defined. But if a parent does define an age then that signal should be honored.