A woman in her thirties opens Instagram to answer a message from her sister and hits a step asking her to establish her age by some means other than typing in a birthday. She has had the account for years, she is obviously an adult, and the step exists because of a legal settlement about children. Under the agreement, Meta applies one or more age assurance methods to each Facebook and Instagram user in the settling states within one year of the effective date [3], which makes this a retrofit across an installed base rather than a change to the signup form [5].
What is pitched is teen safety. What gets built is an age bucket attached to every account, 18+, 13-17 or under 13 [7], assigned by a third party's licensed method or one Meta develops itself [4], with accounts that have not been assessed yet dropped into Default Protections until they are [8]. Techdirt argues the setup threatens anonymity and privacy for everyone using the products [17] and that the same document requires Meta to collect, analyse and retain more information about its teen users [10]. Both can be true, because the mechanism is measurement. You cannot demonstrate to an attorney general that a 15-year-old was treated as a 15-year-old without keeping the record that she is 15. The under-13 rule shows the same pattern: banned on paper since Meta opened to the public in 2006 [15], it now becomes an obligation to detect and delete those accounts [16].
The teen restrictions come off only when a parent turns them off, and the price of that switch is a supply of detail about the teen's usage and online community flowing to the parent, per Techdirt's reading [11]. Add the clause it reads as letting attorneys general enforce Meta's own "age inappropriate content" categories, the same categories Meta has struggled to administer without sweeping up sexuality, sexual and reproductive healthcare, and abortion medication [12], and over-blocking becomes the cheap engineering default.
The 52 in the headline is worth doing on paper: 50 states minus Florida, New Mexico and Texas, plus D.C., plus American Samoa, Guam, the Northern Mariana Islands and Puerto Rico [13][14]. An obligation scoped by jurisdiction has to know which jurisdiction the user is in, so location inference now feeds age enforcement, and three states sit outside the config. Meta's own preference is visible in the text, which has it considering age signals from Google and Apple operating systems and app stores [9]; it has argued before that this job belongs to the platforms rather than to individual services [18].
For anyone else running an age gate, two axes decide what it costs you. First, does an unresolved check degrade the account or lock it. Second, does the check run once or keep running. Degrade-and-run-once is a form field. Lock-and-recheck is a support organisation, because every false negative is a paying adult who cannot get in and must prove a fact about herself to a model that has already decided otherwise. Meta is being moved toward the second corner for its entire base in 52 jurisdictions. The forcing function to carry into your own review: for each data field your compliance work adds, name the field it retires. If the answer is none, what you have built is more collection with a legal justification attached.
