Regulation · United Arab Emirates · Child Digital Safety

UAE Child Digital Safety — under-18s, by design.

Federal Decree-Law No. 26 of 2025 establishes the UAE's first dedicated regime for protecting children in digital environments. The law operates on two parallel tracks — distinct obligations for digital platforms (gaming, social media, live-streaming, e-commerce) and for internet service providers. The strictest provisions target children under 13, where verifiable parental consent and a near-total prohibition on data collection apply. The law is in force from 1 January 2026, with full compliance required by 1 January 2027.

In force 1 January 2026Federal Decree-Law 26 / 2025
Compliance deadline 1 January 2027One-year grace period
"Child" definition Under 18Heightened protections under 13
Implementing regulations PendingPenalties & enforcement to be specified
01 — Compliance trajectory

In force now. Deadline 1 Jan 2027.

The compliance window is short. The law took effect 1 January 2026. Affected entities have one year to come into compliance — meaning operational obligations land 1 January 2027, with implementing regulations and the Cabinet platform classification expected during the grace period. Practitioners should treat the year as build time, not headroom.

Issued
Late 2025 Federal Decree-Law No. 26 of 2025 issued by the UAE Government.
In force
1 January 2026 Law takes effect. One-year grace period begins for in-scope entities.
Implementing regs
During 2026 Cabinet platform classification, Administrative Penalties Regulation, TDRA standards expected.
Compliance deadline
1 January 2027 Full operational compliance required for all in-scope entities.
02 — Two parallel tracks

Digital platforms and ISPs. Different obligations.

The Child Digital Safety Law is structurally bifurcated. Digital platforms — gaming, social media, live-streaming, e-commerce, and similar consumer-facing digital services — carry one set of obligations focused on age verification, content moderation, advertising restrictions and data protection for children. ISPs carry a parallel but narrower set focused on network-level filtering and infrastructure-level safe-access measures. Most groups operating in or into the UAE need to map their entities to one or both tracks.

Track 01

Digital Platforms

Gaming, social media, live-streaming, e-commerce, and other consumer-facing digital services. Obligations are user-facing, age-aware, and content-aware. Platform classification by Cabinet decision will determine the proportionality of each obligation to platform risk profile.

P-01 Privacy by defaultDefault privacy settings calibrated for child users — lowest data exposure as the starting state.
P-02 Age verificationEffective and reasonable mechanisms, proportionate to platform risk classification.
P-03 Content blocking & filteringTools to block, filter, and age-rate content. Enforcement of platform-side age restrictions.
P-04 Advertising regulationRestrictions on targeted electronic advertising directed at children, including profiling-based ad targeting.
P-05 Gambling & commercial gaming prohibitionChildren must not be able to participate in, create accounts for, or access online commercial gaming or betting.
P-06 Parental controls & reporting toolsFunctional parental control mechanisms; child-accessible reporting tools for harmful content.
Track 02

Internet Service Providers

Network-level obligations on entities licensed by the TDRA to provide internet access in the UAE. The ISP track is narrower than the platform track — focused on infrastructure-level filtering and supervised-access support — but applies independently of any platform-side compliance.

I-01 Network-level content filteringActivate content filtering systems on the network to support compliance with prohibitions on harmful content for children.
I-02 Safe and supervised accessTake necessary measures to enable safe and supervised internet access by children — including parental control compatibility.
I-03 Support for parental controlsNetwork-level provisioning of parental control measures and compliance with TDRA-issued standards.
I-04 Regulator cooperationCooperation with the TDRA, the Child Digital Safety Council and other competent authorities. Reporting obligations as set by TDRA standards.

A single corporate group can sit on both tracks. A telco offering broadband (ISP track) plus a content streaming service (platform track) carries dual obligations under the same Decree-Law, with separate compliance discipline for each. Many Gulf and regional telecoms groups will fall into this category by virtue of vertical integration.

03 — Who's in scope

Extra-territorial. Scope is broad.

The Child Digital Safety Law has explicit extra-territorial reach. It applies to digital platforms and ISPs operating in the UAE, and equally to those targeting users in the UAE — even with no UAE legal presence. Foreign platforms with material UAE user bases are squarely in scope, and the Implementing Regulations will set the basis for enforcement actions including service blocking, suspension, or closure.

UAE-based digital platform In scope

Any digital platform — gaming, social media, live-streaming, e-commerce, content sharing, similar — established in the UAE and accessible to or used by children. Carries the full digital platform obligations track. Subject to forthcoming Cabinet platform classification system.

CDS Law · Track 01 obligations
UAE-licensed ISP In scope

Any ISP licensed by the TDRA to provide internet access services in the UAE. Carries the ISP obligations track — network-level filtering, supervised-access support, parental control infrastructure, regulator cooperation.

CDS Law · Track 02 obligations
Foreign platform targeting UAE users Extra-territorial

Platforms with no UAE legal presence but with a material UAE user base or with content directed at UAE users. Squarely in scope. Combination of extra-territorial reach, mandatory cooperation, and service-blocking enforcement creates significant exposure even without UAE establishment.

CDS Law · Extra-territorial reach
Vertically integrated telco / digital group Both tracks

Groups operating both ISP services and consumer-facing digital platforms — common in Gulf and regional telcos. Both obligation tracks apply; compliance must be designed independently per track and reconciled at the group level. Common scenario for major regional groups.

Both tracks · Group-level compliance
04 — Under 13 — heightened protection

The age-13 line is the strictest provision.

While the law applies to all under-18s, the strictest provisions kick in at age 13. Below 13, the regime moves from "protective controls" to "near-total restriction" on platform data handling. Verifiable parental consent becomes the only viable basis for processing; commercialisation of children's data is prohibited; and the obligations apply directly to digital platforms regardless of jurisdiction. This is the most demanding provision in the entire UAE privacy framework — stricter than anything in Federal PDPL, DIFC or ADGM.

CDS Law · Children under 13

Strictest line in UAE privacy law.

Four interlocking restrictions. The age-13 boundary is the operational threshold every digital platform with UAE users needs to identify, verify, and manage as a hard cut-off in product flows.

01
Verifiable parental consent Personal data processing of children under 13 requires verifiable parental consent — not the child's own consent. The verification mechanism must be effective; standard click-through cannot satisfy this requirement.
02
Prohibition on commercialisation Strict prohibition on collecting, processing, or selling personal data of children under 13. The line on data sale is absolute — no consent-based exception. This is the most restrictive provision in the entire UAE privacy framework.
03
Targeted advertising prohibited Targeted electronic advertising directed at children — including under-13 profiling-based targeting — is prohibited. Contextual non-personalised advertising remains possible; behavioural and personalised advertising is not.
04
Commercial gaming hard cut-off Children of any age must not access online commercial gaming or betting platforms — directly or indirectly through advertising, promotion, or data-based exploitation. Platform-side enforcement and ISP-side network blocking expected.
05 — Multi-regulator governance

No single regulator. Layered authority.

Unlike the Federal PDPL — which sits with the UAE Data Office — the Child Digital Safety Law distributes regulatory authority across multiple bodies. The TDRA holds authority over ISPs and standards-setting; competent authorities (typically media, child protection and cybersecurity bodies) supervise platforms in their respective remits; and the Child Digital Safety Council coordinates the overall framework. Practitioners should expect compliance interactions with multiple authorities, not one.

Layer 01 TDRA

Telecommunications and Digital Government Regulatory Authority. Issues policies and standards for ISP compliance under the law. Supervises ISP-track obligations — network filtering, parental control infrastructure, supervised-access measures. The primary regulator for the ISP track.

Layer 02 Competent Authorities

Authorities responsible for child affairs, media, and cybersecurity. Each supervises platform obligations within their respective remits. A gaming platform might engage with media authority; a social-media platform with cybersecurity authority; a financial e-commerce platform with multiple authorities. Allocation of authority is content- and sector-driven.

Layer 03 Child Digital Safety Council

Chaired by the Minister of Family. Advisory and coordinating body bringing together federal entities, local entities, and the private sector. Proposes strategic policies and initiatives, ensures alignment with international standards. Not a direct enforcement body — sits above the operational regulators in a coordination role.

Layer 04 UAE Federal PDPL overlay

Federal Decree-Law No. 45 of 2021 — Personal Data Protection Law. The CDS Law's data-protection obligations explicitly align with the broader Federal PDPL framework. Where children's personal data is processed, both laws apply concurrently. The under-13 protections are stricter than anything in Federal PDPL — when both apply, the stricter standard prevails.

Layer 05 Cabinet platform classification

Forthcoming Cabinet decision. Will classify digital platforms by risk profile — determining the proportionality of obligations like age verification mechanisms, content moderation depth, and parental control sophistication. Higher-risk platforms (live-streaming, gaming with chat) will carry stronger obligations than lower-risk platforms (static content, e-commerce). Classification system pending publication.

06 — Penalty regime

Pending — but not toothless.

The specific administrative penalty figures are pending the Implementing Regulations expected during 2026. The law itself names the categories of enforcement available — and these are substantial. Service blocking, account suspension, and platform closure are explicitly on the table, alongside whatever financial penalty schedule the Cabinet sets. Plus the Cybercrime Law and PDPL operate in parallel where their respective triggers are met.

Enforcement category Source Practical scope
Administrative finesTo be set by Implementing Regulations CDS Law Forthcoming Administrative Penalties Regulation under the CDS Law. Specific figures pending. Expected to follow the proportionality logic applied across UAE federal regulation — fines calibrated to violation severity, with separate ceilings for individual vs corporate offenders. Multiple-violation aggregation likely.
Service blocking / suspensionOperational consequence CDS Law Explicitly named in the law as available enforcement. For foreign platforms in particular, the threat of service blocking is the most material enforcement consequence — given the absence of UAE establishment, financial penalty collection is harder, but blocking access at the network level is enforceable through ISPs. Similar to existing UAE blocking authority for prohibited content.
Up to AED 5 millionPlus imprisonment Cybercrime Law overlay Federal Decree-Law No. 34 of 2021 (Cybercrime Law). Applies in parallel where child-data misuse meets cybercrime triggers — unauthorised access, intentional disclosure, identity-related crimes targeting minors. Imprisonment available for material offences. Operates independently of CDS Law administrative penalties; one incident can trigger both.
PDPL administrativePending Federal PDPL Executive Regs Federal PDPL Federal Decree-Law No. 45 of 2021 — Personal Data Protection Law. Federal PDPL sanctions operate concurrently for personal-data violations involving children. PDPL Executive Regulations are themselves pending — meaning headline figures still to be set. Where both regimes apply (typical for child personal-data processing), the stricter penalty applies.

For foreign platforms, the headline risk is service blocking — not financial penalty. The combination of extra-territorial reach, mandatory regulator cooperation, and explicit blocking authority means non-compliance can be enforced at the network level even where financial enforcement is impractical. UAE authorities have a track record of using content-blocking authority against non-compliant foreign services.

07 — What the work looks like

Eleven workstreams the CDS Law actually triggers.

The work splits cleanly along the two-track structure. Platform operators carry workstreams W-01 to W-08; ISPs carry workstreams W-09 to W-11; vertically integrated groups carry both. Most workstreams must be largely complete by 1 January 2027 — meaning detailed scoping should already be underway in early 2026 to leave realistic build time.

W-01

Track determination & classification

First-pass determination: are we on the platform track, the ISP track, or both. For platform-track entities, alignment to the forthcoming Cabinet platform classification — risk-tier mapping for proportionality of obligations.

W-02

Age verification design

Age verification mechanism design proportionate to risk classification. For high-risk platforms (live-streaming, gaming with chat), robust verification with low circumvention risk. For lower-risk platforms, lighter mechanisms acceptable. Cross-jurisdiction integration where the platform also operates under EU GDPR / UK Children's Code obligations.

W-03

Verifiable parental consent

Verifiable parental consent mechanism for under-13 data processing. Identity-verification workflow for parent / guardian. Audit trail of consent capture. Refresh / re-verification protocol where consent context changes. Operational hard requirement for any under-13 processing.

W-04

Privacy-by-default architecture

Default privacy settings calibrated for child users — minimum data exposure as the starting state. UI flows redesigned where child accounts are auto-detected. Cross-product consistency where multiple services interact.

W-05

Content classification & filtering

Content classification system for age-appropriateness. Blocking, filtering and age-rating mechanisms. Reporting tools for harmful content visible to child users. Engagement with TDRA standards on content categorisation.

W-06

Advertising regime overhaul

Restrictions on targeted electronic advertising to children. Profiling and behavioural advertising disabled for child users. Contextual / non-personalised advertising as alternative. Ad-tech vendor stack reviewed against the under-13 prohibition on data commercialisation.

W-07

Commercial gaming & gambling cut-off

Hard cut-off for child access to online commercial gaming and gambling. Account-creation restriction; ad-promotion restriction; data-based exploitation restriction. For platforms with adjacent gaming features (e.g. social platforms with gaming integrations), boundary management against the prohibition.

W-08

Parental controls & reporting

Functional parental control mechanisms accessible to parents/guardians. Reporting tools accessible to child users. Cross-platform consistency where the parental-control system operates across multiple services. Documentation and demonstrability of effectiveness.

W-09

ISP network filtering

Network-level content filtering activation. Calibration to TDRA standards. Filter-list management; appeal / unblocking mechanism for false-positive blocks. Compliance with TDRA inspection requirements.

W-10

ISP supervised-access support

Network-level provisioning of safe-access measures. Parental control infrastructure compatibility. Customer-facing tooling enabling supervised access for child accounts. TDRA-aligned standards adoption.

W-11

Multi-regulator engagement

Engagement with TDRA, competent authorities (media, child affairs, cybersecurity), and the Child Digital Safety Council. Notification protocols, standards-update tracking, regulatory liaison cadence. For multi-track groups, coordinated regulator engagement avoiding duplicate or conflicting positions.

08 — How this is delivered

Three engagement shapes.

CDS Law work is delivered through one of three engagement shapes. Given the operational depth of the obligations and the 1 January 2027 deadline, most platform-track entities will need a substantive project engagement; ongoing operation post-build typically benefits from a DPOaaS or advisory retainer arrangement.

09 — Common questions

Things people ask on first call.

Common questions on the CDS Law during the 2026 grace period — from platforms scoping their compliance build, ISPs aligning to TDRA standards, and group operators figuring out which entities sit on which track.

We're a foreign platform with UAE users — do we have to comply?
Yes, if your platform is targeting UAE users or has a material UAE user base. The CDS Law has explicit extra-territorial reach. Practical enforcement of financial penalties on foreign entities without UAE presence is harder, but the UAE has explicit blocking authority — non-compliant foreign platforms can be blocked at the network level by UAE ISPs. The combination of mandatory regulator cooperation, immediate reporting obligations, and blocking authority creates significant compliance exposure even without UAE establishment. Most multinationals with UAE user bases should treat the law as fully applicable.
Do we need separate compliance for under-13 vs 13-17?
Yes — the regimes diverge meaningfully at age 13. For under-13 users: verifiable parental consent is required; data sale and commercialisation prohibited absolutely; targeted advertising prohibited; profiling-based personalisation prohibited. For 13-17 users: protective controls, age-appropriate design, and platform-side restrictions apply, but the absolute prohibitions on data commercialisation are not as strict. Operationally this means age 13 is a hard product-flow boundary requiring distinct compliance treatment, not just a graduated set of controls.
How does this overlay with the UAE Federal PDPL?
The CDS Law explicitly aligns with Federal Decree-Law No. 45 of 2021 (Federal PDPL). Where children's personal data is processed, both laws apply concurrently. The CDS Law's under-13 protections are stricter than anything in Federal PDPL — when both apply, the stricter standard prevails. Operationally, organisations with UAE operations face: the broader Federal PDPL framework for all personal-data processing, plus the CDS Law overlay for child-data specifics, plus DIFC or ADGM regimes if those apply, plus the Cybercrime Law where relevant. Multi-regime governance is the working reality.
What's the platform classification system?
Article 6 of the CDS Law contemplates a Cabinet decision establishing a classification system for digital platforms based on risk profile. The classification will determine the proportionality of obligations — particularly age verification mechanism robustness. Higher-risk platforms (live-streaming with chat, gaming with social features, content sharing with stranger interactions) will carry stronger obligations than lower-risk platforms (static content delivery, basic e-commerce). The Cabinet decision is pending; once published, in-scope platforms will need to determine their classification and align their compliance accordingly. Practitioners should design with conservative classification assumptions and adjust on Cabinet publication.
What does "verifiable parental consent" mean operationally?
The law requires the consent verification mechanism to be effective — not just nominal. Standard click-through cannot satisfy this. International precedent (US COPPA, EU GDPR Article 8 implementations) provides the working models: payment-card verification (with token charge that's refunded), government-ID verification (where lawful), parental email verification with knowledge-based authentication, video / live verification call, or dedicated parental verification services. The UAE Implementing Regulations may specify approved mechanisms; until then, conservative practice is to use stronger mechanisms aligned with international best practice rather than weaker click-through equivalents.
How is this different from EU / UK / India children's data regimes?
The frameworks share common ground (under-18 protection, parental consent for younger children, age-aware design) but differ on specifics. EU GDPR Article 8 sets the parental consent age at 16, with member-state derogation down to 13 — UAE uses 13 directly. UK ICO Children's Code is design-focused with 15 design standards. India DPDP Act 2023 sets the age at 18 with verifiable parental consent for all under-18 processing — stricter on age but broader in approach. UAE CDS Law is the most regulatory of the four — explicit two-track structure, multi-regulator architecture, hard prohibitions on commercial gaming and data commercialisation. For multinationals, the working approach is a single children's-data program built to the strictest applicable regime, with jurisdiction-specific overlays.
When will the Implementing Regulations be issued?
The Implementing Regulations — including the Administrative Penalties Regulation, Cabinet platform classification decision, and TDRA technical standards — are expected during 2026, the grace period before the 1 January 2027 compliance deadline. The expected sequence is platform classification first (allowing entities to determine their tier), penalties next (allowing risk-based prioritisation), and detailed technical standards last. Practitioners should not wait for full publication to begin scoping — the foundational obligations are clear from the law itself and warrant immediate work.
We're a vertically integrated telco — what does dual-track look like?
Common scenario for major Gulf groups. The ISP entity carries the network-level filtering and supervised-access track (Workstreams W-09 to W-11). The content / streaming / gaming entities carry the platform-track obligations (Workstreams W-01 to W-08). The two tracks must be designed independently — the ISP filtering doesn't satisfy platform obligations; the platform's age verification doesn't reduce ISP filtering obligations. At group level, you need: separate compliance owners for each track, coordinated regulator engagement (TDRA for ISP, competent authorities for platforms), and a unified group-level compliance summary for board / audit committee oversight.

A year is not headroom.

The 1 January 2027 deadline is closer than the build cycle for the obligations the CDS Law actually requires. Age verification, verifiable parental consent, content classification, advertising overhaul, parental controls — each is multi-month work in itself. A 30-minute scoping call costs nothing — we will tell you honestly which track applies, where the hardest exposures sit (typically under-13), and what the right shape of work looks like before the grace period closes.

Schedule a call