A committee draft circulating in Brussels would move age assurance from a national option to a platform-level obligation, with a compliance date eighteen months after entry into force. The text is 42 pages, and the operative language sits in a single paragraph that defines who is responsible when a third-party vendor fails.
The draft keeps the vendor model but shifts liability. A platform that uses a certified provider is presumed compliant unless it had reason to doubt the provider's performance; a platform that builds its own is assessed directly. That asymmetry is deliberate, and it is the reason three large operators have already started certification conversations.
The timeline in the text
Publication of the final text, then six months for the certification framework, then twelve months for platforms to comply. Operators reading the annex say the certification framework is the bottleneck, not the platform work, because no certification body has yet been designated in most member states.
The draft also touches retention. Refusal records must be kept for twelve months, verification records for six, and neither may be retained beyond that without a documented legal basis. Operators that currently keep everything indefinitely will need a deletion schedule, which is a systems change rather than a policy change.
What is not in the text matters as much. There is no harmonised definition of “reasonable steps”, no fee cap on certification, and no mutual recognition clause, which means a platform serving five member states may face five assessments.
Key takeaways
- The draft makes age assurance a platform obligation with an 18-month compliance window.
- Using a certified vendor creates a presumption of compliance; building in-house does not.
- Retention is specified: 12 months for refusals, six for verifications, with no mutual recognition.