OUT-LAW ANALYSIS 5 min. read

KIDS Act: the plans for enforcement

Child using a smartphone late at night in bed

EU policymakers have decided to lean on existing enforcement structures rather than introduce a new EU child safety regulator. Denis Borisov/iStock.


The choice of EU policymakers to rely on existing enforcement structures to underpin the proposed new KIDS Act presents added complexity for providers of online services and AI systems in-scope of the plans.

Rather than creating a new EU child safety regulator, the KIDS Act proposal leans on three pre-existing enforcement mechanisms under the Digital Services Act (DSA), AI Act and General Data Protection Regulation (GDPR). Which mechanism applies would primarily depend on the type of provider and service and the issue in question, but this deliberate architectural choice could give rise to cases where providers face centralised enforcement of their KIDS Act compliance by the European Commission and by multiple national regulators.

For example, a platform which hosts social networking, an AI companion and video games could in theory face KIDS Act enforcement from the European Commission, national AI Act authorities and GDPR supervisory authorities. This brings risks of fragmentation, gaps and overlap. It could also lead to debates between authorities as to which has jurisdiction over any given case.

Below, we break down in more detail how policymakers envisage the KIDS Act being enforced.


Read more on the EU KIDS Act proposals


Building on existing enforcement structures

The DSA, AI Act and the GDPR already govern matters pertaining to child online safety in the EU to some extent. The KIDS Act proposal builds on the existing requirements by, among other things, codifying obligations to design services and systems with child safety in mind and providing for a graduated user-age-based system of access restrictions.

In enforcement terms, rather than add to an already complicated picture, the European Commission’s intention is to make use of the existing mechanisms provided for in the DSA, AI Act and the GDPR.

In terms of the DSA, a two-track system of enforcement applies, under which ‘very large online platforms’ (VLOPs) and ‘very large online search engines’ (VLOSEs) are subject to the direct oversight of the European Commission, while for all other online intermediaries in scope of the DSA, enforcement is at EU member state level.

This two-track system is to be imported into the KIDS Act and would apply to services that are already within scope of the DSA and envisaged to fall in scope of the KIDS Act proposal. Those services include online social networking services, video-sharing platform services, online games and app stores.

According to the proposal, some of these services would, for KIDS Act purposes, be considered to be provided by VLOPs. In those circumstances, before their services come into contact with children under the new regime and within 30 days from the date the KIDS Act enters into force, existing VLOPs would have to submit a compliance plan to the Commission showing how they intend to meet their obligations. VLOPs designated after the Kids Act enters into force would have four months to do so. The plan would need to be verified by independent auditors and be produced at the providers’ own expense.

On the one hand, this would give the VLOP the opportunity essentially to prospectively agree with the Commission that their services are compliant with the KIDS Act, reducing the risk of enforcement at a later point. On the other hand, it would place significant pressure on the VLOP to obtain agreement as a precursor to being able to offer their services to under-18s.

In terms of AI systems, AI companions and general conversational chatbots are in-scope of the KIDS Act proposal. Their compliance with the child online safety obligations would be subject to the AI Act’s enforcement regime.

Like with the DSA, responsibilities for enforcement under the AI Act are split between a centralised EU body – the AI Office – and designated national regulators. Perhaps most notably, the national regulators will have duties to oversee compliance with the rules applicable to ‘high-risk’ AI systems when those rules take effect, while the AI Office has direct enforcement powers in respect of providers of general-purpose AI models and AI systems integrated into VLOPs and VLOSEs.

For VLOPs and AI systems falling within the European Commission’s direct oversight, an expedited procedure would apply to KIDS Act infringement proceedings. Under those plans, it is envisaged that the Commission would share its preliminary findings with providers within 30 working days, and adopt a final decision within 90 working days, of opening those proceedings.

Over and above this, the KIDS Act proposal provides for national data protection authorities to take on the role of monitoring the processing of personal data necessary to comply with the KIDS Act.

In practice, that would involve data protection authorities overseeing the processing of personal data that service providers collect for the purposes of meeting their obligations around age assurance, in relation to which specific data protection standards would apply.

All providers of online social networking services, video-sharing platform services, online games, AI companions and general conversational chatbots, which do not have an establishment in the EU, would be required to designate a legal representative in one of the EU member states they offer their services or systems in. Those providers would therefore have some influence over the national authorities they would need to engage with over KIDS Act compliance.

Measures to ensure close cooperation and coordination between the European Commission and the various national authorities that would hold enforcement powers under the proposed new KIDS Act are included in the draft legislation.

One specific way this is envisaged is in respect of cross-border “incidents affecting the protection of minors”. The Commission would be responsible for coordinating the assessment of those incidents and for calling upon the expertise and resources of national authorities for this purpose, with cooperation envisaged between states and the Commission over knowledge sharing. It is also anticipated that voluntary arrangements would be put in place to “facilitate a rapid response in the event of an incident affecting the protection of minors in the Union or in significant parts of it”.

Ultimately, though, national authorities would be prohibited from taking “decisions which run counter to a decision adopted by the Commission” under the KIDS Act, according to the proposal.

Sanctions

Sanctions for non-compliance vary under the DSA, AI Act and GDPR. For services in-scope of the DSA’s enforcement regime, fines of up to 6% of a provider’s total worldwide annual turnover could be imposed, while the maximum fine that can be imposed under the AI Act is 7% of global annual turnover or €35 million, whichever is highest. For GPDR infringements, providers could face fines of up to €20 million or 4% of their annual global turnover, whichever is highest.

The KIDS Act proposal further contains anti-circumvention obligations on all providers, non-compliance with which could result in fines of up to 6% of worldwide annual turnover for the most serious infringements.

How enforcement will be paid for

An annual supervisory fee would be payable by providers of services or systems that fall subject to the European Commission’s direct supervision under the proposed KIDS Act. For providers that have multiple services in-scope of the proposal, a fee would be payable on a per service or system basis.

The fee would be set with reference to the costs incurred by the Commission in performing its various tasks of supervision, monitoring, investigation, and enforcement under the KIDS Act and would be capped at no more than 0.03% of a provider’s worldwide annual net income in the preceding financial year.

Co-written by Pauline Greiner of Pinsent Masons.

We are processing your request. \n Thank you for your patience. An error occurred. This could be due to inactivity on the page - please try again.