Children's social media: what changes after an age check? Features and correction
About protective settings, data collection, correction and access to advice, distinguishing California laws, Japanese policy discussions, EU guidance and the KIDS Act proposal
Read California's September 2026 child-safety laws, Japan's interim report and October 6 meeting materials, and EU guidance and the KIDS Act proposal. Distinguish age and feature restrictions while examining information collection, correction of mistakes and continued access to support.
TL;DR
- Read feature and age conditions through enacted laws, draft rules and proposals
- Examine defaults, information handling and correction after age checks separately
- Distinguish transaction counts from children’s continued access to advice and learning
The header image is AI-generated and does not depict an observed family or event.
What Is Happening
Read the September 10 signatures through separate social-media and AI protections
Debates about children and social media often focus on the age at which someone may open an account. Yet autoplay, notifications and recommendations can create different environments for users of the same age. Examining what happens after an age check connects the question of access to the design of the service itself.
On September 10, 2026, the announced the signing of several online child-safety laws. AB1709 addresses covered platform features; SB1119 addresses companion-chatbot safety. They are separate laws signed on the same day.
The announcement describes restrictions on supplying users under 16 with autoplay and certain feeds based on user history and profiles. Establishing someone's age is connected to changing the features they receive.
The also permits an under-16 user to create or maintain an account when no covered addictive feature is provided. Its feed definition includes conditional exceptions for expressly requested material, among others. Platforms limited to commercial transactions or reviews, and feeds primarily serving storage, are excluded from the covered-platform definition. An age threshold alone does not describe the law's feature restrictions and account conditions.
For SB1119, the Governor's announcement describes crisis protocols in cases of suicidal ideation, parental controls, notifications when a child disables safety settings, independent audits and annual risk assessments. This is what the signing announcement establishes; it does not mean every AI service faces the same feature restrictions as social media.
Background & Context
Check laws, implementation stages, Japanese discussions and EU proposals
Check the document's stage, even within one jurisdiction
California also has SB976, signed in September 2024. The describes requirements concerning verifiable parental consent for supplying minors with addictive feeds and certain features. It gives January 1, 2027 as the deadline to adopt regulations on age assurance and parental consent.
When checked on October 8, 2026, the guidance described the proposed regulations as under review following comments on the draft regulations, with review by the Office of Administrative Law also required. The January 1, 2027 deadline for adopting SB976 regulations is not a general start date for all AB1709 obligations. Nor should a consent provision in SB976 be assumed to exist in a different law.
A signature, adoption of implementing rules and a provision's require separate checks. Litigation may also affect enforcement of particular provisions. A signing announcement alone cannot establish that every implementation step is complete, or determine whether a particular service complies.
Japan is examining design and providers' roles
Japan's , adopted September 9, 2024, promotes incorporating effective protection into new devices from the design stage. It would be inaccurate to say Japan has paid no attention to design.
published the , which considers provider risk assessment, protection, disclosure and continuing improvement. The merits of a statutory restriction below a fixed age remain a subject for discussion. These are proposals within an ongoing review, rather than a set of newly enacted obligations.
consider the status of operating-system protection tools, participants' roles and the conditions for parents and children to understand and use them. An operating system manages a device’s basic functions. Publication of meeting materials does not establish what participants agreed or which duties were decided.
EU guidance and a new legislative proposal
recommends private-by-default accounts and disabling autoplay and notifications that contribute to excessive use by default. The guidelines inform assessment under the Digital Services Act (DSA) provision on protecting minors. Following them does not automatically guarantee compliance.
explicitly identifies the September 2026 EU KIDS Act as a proposal. It proposes stages including independent social-media accounts from age 15; these should not be presented as already enacted EU-wide obligations. Comparison requires checking both age rules and the stage of the relevant document.
Laws and implementation
California examples
- 2026 signatures
- AB1709 and SB1119
- Separate 2024 law
- SB976
- Further checks
- Rules, scope, application
Guidance and proposals
Japan and EU examples
- Japan
- Basic plan; interim report
- EU
- DSA guidance; KIDS Act proposal
- Reading check
- Advice versus obligations
Based on documents checked on October 6, 2026, with the SB976 guidance reflecting the October 8 check. This is not a ranking of systems or a determination of enforcement or service compliance.
Reading the Structure
Examine settings after verification, information handling, mistakes and support
Examine the screen after the age check
An age check should connect to the protection it is intended to activate. In a hypothetical case where a service identifies a minor but leaves autoplay unchanged, verification and protection would be disconnected. Identifying who receives the age signal and who changes notifications, recommendations or contact settings is a useful starting point for examining operations.
This is a proposed review question, not a documented failure by a particular service. Reviewers can distinguish whether a setting exists, whether protection is enabled by default and whether the user understands it. An unclear explanation of changed settings can leave users unsure what a protection tool actually does.
Separate the age condition from detailed identity information
describes proving that someone is over 18 without sharing other personal information with the service. It describes the solution as feature-ready in April 2026, which does not mean deployment for every country or user is complete.
This raises a practical question: must a service retain a person's name or entire identity document to establish an age condition? Even a method that shares less information needs scrutiny of data held by the verifier, retention and possible links to other activity. A description of the method does not establish the safety of a completed implementation.
Responsibility placed with an operating system, an app store or an individual service also changes where a user must seek help. The policy discussion does not itself justify schools or community organizations collecting identity documents. First establish which features require which level of assurance, then examine how to avoid collecting more information than that purpose needs.
Consider mistakes and access to support
Protection should also be assessed when the age determination is wrong. Can the affected person understand the reason and request correction? A review needs to consider those who cannot obtain the requested evidence or cannot comfortably ask a parent for help.
Restricting a feature and preserving access to help are related design questions. A referral to outside support may be ineffective if a restricted user cannot reach the referral page. This does not claim that the systems discussed uniformly block advice; it identifies a condition to examine when designing and assessing their operation.
Provider design
Features and information
- Assurance
- Necessary age condition
- Defaults
- Notifications, play, feeds
- Correction
- Explanation and appeal
User experience
Questions proposed here
- Understanding
- Are changes clear?
- Information
- Is collection excessive?
- Support
- Can help be reached?
Operational questions informed by the primary materials. These are not verified implementation results or measured effects.
Distinguish implementation counts from children's experiences
Counts of enabled settings or completed age checks record activity. Establishing better sleep or reduced harm requires separate evaluation. An should begin with the problem the intervention is intended to address, while also examining whether access to learning and support continues.
For a proposed trial of night-time notification limits, reviewers might examine whether the setting is active, whether users understand it, experiences of being woken by notifications and reasons for requesting changes. They should record timing, participants and other changes in daily life. A before-and-after difference alone does not establish causation. Listening to children can reveal unexpected inconvenience or interruptions to support, beyond simply counting support for a rule.
Follow correction through to restored access
A corrected age record and access restored for the user are different events.
Consider someone requesting correction after an incorrect age determination. This is an operational example, not an observed provider response. An acknowledgement does not establish that review finished, age information changed or the appropriate features became available. A correction notice alone cannot establish that the person reached needed advice again.
If the verifier and the service provider differ, users need to understand where to ask questions. Before requiring evidence at several contact points, providers could clarify what information passes between them and where correction takes effect. People unable to obtain identity documents or comfortably seek parental help also need consideration. These are review questions, rather than a universal procedure required by the laws discussed.
Correcting a setting is also distinct from handling evidence submitted for verification. Restored features do not explain how images or decision records are retained. Reviewers can examine explanations of retention, deletion and links to other activity. Keeping records needed to resolve a correction request differs from collecting unnecessary information indefinitely.
Explain the population and stages behind published counts
Counts of supplied features do not establish that children could use the protection.
Japan's interim report considers disclosure and evaluation feeding into improvement. Reading such figures requires checking whether they count people, accounts, devices or transactions. Several services used by one person must not automatically be interpreted as several protected children. Reports of changed use also require examination of participants and timing; a change alone does not establish an intervention's effect.
The proposed review would record active settings, understanding, successful correction and access to advice separately. Experiences of people who stopped partway can reveal needs hidden by completion totals. Gathering these observations should not justify excessive personal information collection. Decisions about necessary records and what is published belong in the same discussion. Comparing provider explanations with users' experiences connects document comparison to assessment of actual operation.
Related Column
Related Guide
Designing outcome indicators(このサイトの記事) distinguishes completed activities from changes experienced by users. The distinction can also inform evaluation of age assurance and protection after it.
Remaining Questions
Ask about family workload, needed connections and accountability for explanations
Safer defaults do not automatically reduce the work of families and schools. Parents still need explanations, settings may span several devices and changes can require discussion. A policy assigning responsibility to providers should examine who helps users understand the tools and correct mistakes after introduction. Differences in a family's available time or knowledge should also be considered when assessing who can actually use the protection. Providing an explanation should lead to checking whether people understood it and could ask questions when they did not.
What alternative opportunities for learning, advice and connection remain for a child whose access is restricted? Closing a screen may reduce exposure to danger while also removing a connection the person needs. Examination should ask which features are restricted and which information or contacts remain available, using children's experiences. The number of restrictions alone cannot establish success; evaluation should also ask whether necessary support has become harder to use. This includes considering where someone can describe a difficulty while an age correction is still being reviewed.
As Japan's discussion becomes more concrete, who will assess providers' explanations, and what happens when improvement does not follow? Laws, guidance and school rules have different scopes. Clear responsibilities and review conditions should connect to an operation in which children can ask questions and seek correction. The remaining task is to turn an age-assurance mechanism into an environment people understand and in which they can reach necessary support.
Reference Books
’s スマホ脳 (新潮新書) (The Smartphone Brain)(外部サイト、新しいタブで開きます), translated by (, 2020), is background reading on attention and device use. The English title above is a rendering of the Japanese title; the linked book is in Japanese. This mention draws on public publisher information and contents. It does not establish the application of 2026 laws or medical causation for particular features, which require the relevant legal texts and research.
References
Governor Newsom signs the strongest child safety chatbot and social media laws in the nation — Governor of California (2026). Governor of California
AB-1709 Covered platforms: age restriction: e-Safety Advisory Commission — California Legislature (2026). leginfo.legislature.ca.gov
Protecting Our Kids from Social Media Addiction Act (SB 976) — California Department of Justice (2026). California Department of Justice
Sixth Basic Plan for a Safe Youth Internet Environment (author translation) — Council for the Promotion of Policies for Children (author translation) (2024). Children and Families Agency
Interim Report on the Future of the Youth Internet Environment Act (author translation) — Working Group Examining the Future of the Youth Internet Environment Act (author translation) (2026). Children and Families Agency
Technical Protective Measures: Ninth Meeting, Material 1 (author translation) — Secretariat of the Working Group Examining the Future of the Youth Internet Environment Act (author translation) (2026). Children and Families Agency
Commission publishes guidelines on the protection of minors — European Commission (2025). European Commission
The EU approach to age verification — European Commission (2026). European Commission
The KIDS Act explained — European Commission (2026). European Commission
Statistics cited in this article
- 1Governor of California(September 10, 2026) Open source
- 2California Department of Justice(SB976, enacted in 2024) Open source
Questions to Reflect On
- Which features and defaults change after age assurance?
- Can an affected user understand and correct an incorrect age determination?
- Can children continue accessing advice and learning after restrictions?
Key Terms in This Article
- Cloud Computing
- A model for on-demand network access to shared computing resources such as servers and storage. Using a cloud service alone does not determine who may view information or the conditions for providing it to third parties.
- Outcome Indicator
- A measure intended to examine changes or benefits relevant to the problem a program seeks to address. Its design distinguishes outcomes from immediate activity outputs; improvement in a measure alone does not establish the program's causal effect.
- Date of application
- The date from which a provision applies to covered persons or activities. Its scope, transitional arrangements and amendments also require checking.
Previous
Japan’s Customer Harassment and Job-Seeker Sexual Harassment: Who Takes Reports?
Next
After an AI bear alert, who handles checks and safety measures?
Get new columns by email
1-2 social structure analysis columns per week. Free to subscribe.
Join ISVD's activities?
Sign up to receive the latest research and activity reports. Feel free to reach out about collaboration or project participation.
Support ISVD’s research and activities
Support ISVD’s research and publications with JPY5,000 per year. There is no automatic renewal.




