[openai-blog] Advancing youth safety and wellbeing in EMEA
OpenAI announced new youth safety measures for its services in Europe, the Middle East, and Africa on 5 May 2026, including age verification requirements and content restrictions for users under 18 [source].
The company stated it will implement age assurance technology to verify user age during account creation in EMEA markets. Users identified as minors will be placed into a restricted mode that limits certain features, including image generation and voice interactions. OpenAI said the measures respond to regulatory requirements under the EU's Digital Services Act and similar frameworks in the region.
The announcement follows months of scrutiny over AI providers' handling of youth safety. Regulators in multiple European jurisdictions have questioned whether existing guardrails adequately protect minors from harmful content generation or inappropriate model outputs. OpenAI did not specify which age verification methods it will deploy or whether existing accounts will be subject to retroactive verification.
The restricted mode for under-18 users will also disable custom instructions and memory features, according to the post. OpenAI stated these limitations aim to reduce exposure to potentially harmful content while maintaining educational utility. The company did not provide data on how many EMEA users are currently minors or how the changes will affect existing usage patterns.
The measures apply only to EMEA regions. OpenAI has not announced equivalent restrictions for users in North America or other markets. The company said it is working with child safety organisations and regulators to refine the approach, but did not name specific partners or provide a timeline for full implementation beyond "coming months."
Why this is an AI incident
Launch-archive bulk classification (10 May 2026). Source signal originates from a real AI provider, regulator, or model-comparison probe; the harm or behavioural change described would not have occurred without the AI system being deployed in the role described. Editor reviewing the archive may amend the rationale per-wire.
Counterfactual "but-for" test per the Editor's Guide.