Protecting minors online: what European rules require and what could change

The available documentation does not confirm a recent announcement by a particular platform or the entry into force of a new general measure in October 2026. It does, however, provide a basis for explaining an existing European framework: on 14 July 2025, the European Commission published guidelines on protecting minors in the context of the Digital Services Act, known as the DSA. The verifiable approach, therefore, is a guide to the scope of those guidelines, not breaking news about a newly announced change. Keeping those two kinds of reporting separate helps readers understand what is established and what would still need confirmation. The publication date is a fact about the guidelines; it is not evidence that every service changed its product on that date.

The distinction matters. A recommendation published by the Commission does not, by itself, demonstrate that every platform has introduced a feature or that terms of use have changed for all families. The guidelines describe measures platforms should consider to reduce risks; they are not a record of measures already rolled out. To establish whether a specific service has changed, a verifiable communication from that service or a decision by the competent authority is needed. A careful account should not turn a general recommendation into a claim about an individual company, nor imply that users can already access a measure unless its availability has been confirmed.

According to the Commission, the guidelines concern online platforms accessible to minors, with an exception for microenterprises and small enterprises. The publication presents a non-exhaustive set of proportionate and appropriate measures addressing risks such as bullying, contact for the purposes of exploitation, harmful content, problematic behaviour and harmful commercial practices. This does not mean that every risk is present on every service, or that every measure must take the same form on every platform. The framework instead calls for measures to be considered in relation to risks and the service concerned; the description should not be read as a finding about any particular platform’s conduct.

The DSA covers different digital services—including social networks, marketplaces and app stores—and seeks a safer online environment that respects fundamental rights. The regime distinguishes obligations according to the service and the type of provider; it should not be reduced to a general ban on social media for minors. Article 28 of the DSA, in particular, establishes obligations related to the protection of minors for platforms accessible to them. Applying those provisions in a specific case requires reading the law and the guidance together with the circumstances of the service. The category of service, the applicable duties and the actual measures in place are separate questions, and the general summary does not answer them all for an individual provider.

Examples in the guidelines include setting minors’ accounts to private by default and adjusting recommender systems to reduce exposure to risks. These are service-design decisions, not controls that depend solely on parents or minors changing settings manually. The Commission also includes recommendations for addressing unwanted contact and exposure to harmful content as part of an approach to protecting minors. In explaining these recommendations, it is useful to distinguish between a protective default built into a service and an optional control that a user has to find and activate. The guidelines discuss measures for platforms to consider; they do not establish that a specific platform has implemented any particular one.

The publication also refers to risks linked to problematic or potentially addictive behaviour and harmful commercial practices. That does not support the conclusion that a particular feature—for example, infinite scrolling or notifications—has been declared illegal in every case. The criterion is to assess risk and appropriate measures, not to presume a breach simply because a feature is common or attractive to users. The guidelines are non-exhaustive: they are not a closed checklist whose partial application guarantees safety. A measure must be understood in context, and the fact that a feature appears in a discussion of risk is not, by itself, a legal finding about that feature or the service that uses it.

For families, these guidelines offer a framework for asking how minors are protected, but they do not replace checking how each account actually works. It is worth reviewing whether a private setting exists, which controls are available, how to report content or unwanted contact, and what options can limit recommendations or interactions. The presence of an option in a menu does not prove that it is turned on by default or effective in every situation. Families can use these questions to understand the controls a service says it provides, while keeping in mind that the guidelines themselves do not verify how a particular account is configured.

A practical check can separate three questions: what does the platform say it does; which settings can a family change; and what reporting or oversight channels exist? If a service announces a change, it is useful to confirm its date, the territory affected, the users included and whether it is a limited test or a general rollout. Without those details, saying that “the platform now protects minors” would go beyond the available evidence. An announcement may describe an intention, a test or a feature for only some users, so its precise wording and scope matter when assessing what families can actually expect.

Protection should not become an exclusive burden for families. Design measures and regulatory obligations also concern providers, while family tools serve as a complement. Even so, the sources cited here do not provide a comparative assessment of platforms or measured results showing a reduction in harm. It is not possible to attribute a quantified effect on minors’ everyday experience to these guidelines. Families may find practical settings useful, but that does not turn the guidelines into evidence that a particular outcome has been achieved or that one service is safer than another.

The primary source consulted establishes the date and general content of the guidelines, but it does not, by itself, demonstrate their practical implementation by each service. To support a news report about a particular platform, at a minimum one would need to locate an official announcement from that company or a public decision describing what changed, when it changed and whom it affects. If an effect is claimed, data or an evaluation with an explained methodology would also be needed. A general statement of policy cannot answer questions about availability, coverage or outcomes unless the relevant details are provided.

The Commission describes the measures as proportionate and appropriate, and presents them as recommendations within the DSA framework. That description must remain separate from a legal conclusion about whether a particular company complies with the law. An authority may assess the circumstances, risks and applicable obligations; an editorial guide cannot do so in its place. Regulatory guidance should not be confused with proof of compliance or infringement. This distinction also matters when describing the legal status of an announcement: publication of guidance is not the same thing as a finding against a provider, and an account of general principles should not suggest that such a finding has been made.

In short, there is a verifiable European framework for protecting minors on platforms and specific design recommendations, but the available research does not confirm a recent development at an individual platform. The useful takeaway for readers is twofold: understand the kinds of safeguards the Commission discusses, and demand precision when assessing announcements. Date, scope, actual availability and oversight are the details that turn a promise or recommendation into a verifiable change. Until those details are documented, reporting should distinguish what the guidelines say from what a service has demonstrably done.