Last reviewed: 5 October 2026<\/p>\n
If your organisation provides online services to children, child safety should be part of product design, supplier selection and everyday operations. The UAE\u2019s Federal Decree-Law No. 26 of 2025 establishes a specific child digital safety framework. Its requirements should be assessed alongside applicable privacy, education and child-protection rules. [1]<\/p>\n
The first question is what your organisation actually does. A social-media platform, an educational app and a school using an external platform do not necessarily have identical duties. Map your activities and users before deciding which obligations apply. A service being accessible to children also deserves a practical safety assessment even where a particular platform rule does not cover it.<\/p>\n
The child digital safety law addresses internet service providers and digital platforms operating in or targeting the UAE. Official explanations identify safeguards involving age verification, privacy, harmful content and children\u2019s data. They also describe restrictions on collecting or sharing the personal data of children under 13, subject to specified conditions. [1]<\/p>\n
Separately, Cabinet Resolution No. 106 of 2026 regulates children\u2019s access to covered social-media platforms. Ministry of Family guidance sets a minimum age of 15 for personal accounts, with enhanced safeguards for users aged 15 to under 16. It identifies X, Facebook, Instagram, Snapchat and TikTok in the current phase and explains that platforms have a transition period of up to 12 months. [2]<\/p>\n
That transition matters. Avoid presenting every technical requirement as if it had to be fully implemented by all online businesses immediately. Equally, a transition under the social-media resolution should not be treated as permission to disregard other existing child-safety obligations.<\/p>\n
For an app or online service, examine registration, profiles, messaging, uploads, purchasing and reporting tools. Ask whether a child can be contacted by an unknown adult, reveal their location, make their profile public or upload identifying information without an appropriate safeguard.<\/p>\n
This is a practical design review, not a claim that every listed control is mandatory for every service. Priorities depend on the product and applicable rules. Document the risks you identify, the controls selected and who is responsible for testing them.<\/p>\n
For example, an educational platform may use a third-party discussion feature. The lesson content may be suitable, but the discussion feature could expose student names or allow unwanted contact. Review the whole user journey, including integrated services, rather than assessing only the main website.<\/p>\n
Official guidance on the child digital safety law describes explicit, verifiable parental consent in relation to protected data processing for children under 13. [3] Consent should not be treated as a universal solution: the relevant conditions and restrictions still need checking, and different activities may require different safeguards.<\/p>\n
Where consent is appropriate, make the request understandable. Explain what data is collected, why it is needed, who receives it and how the parent can manage the relevant permission. Keep a reliable record of the process without collecting excessive identity information merely for convenience.<\/p>\n
Age assurance creates its own privacy questions. The Ministry\u2019s social-media guidance emphasises proportionate verification and minimum necessary data. [2] A provider considering identity documents, facial analysis or an external verification service should assess access, security, retention and supplier responsibilities before implementation.<\/p>\n
A school does not automatically become a social-media platform because it uses one. However, it should review whether teaching activities, publicity or parent communications encourage children to use accounts or features that conflict with applicable rules.<\/p>\n
Prepare an inventory of learning apps and communication services. Ask vendors which child-safety controls are available and who can change them. Review student-photo permissions, access to class groups, staff accounts, recording settings and procedures for reporting harmful contact or content.<\/p>\n
Give staff a clear escalation route. Teachers should know whom to contact, how to preserve necessary evidence safely and when the safeguarding lead must involve the appropriate authorities. Avoid forwarding sensitive material widely within the organisation as a substitute for a controlled response.<\/p>\n
Keep the review active as the service changes. A new chat feature, advertising tool or analytics integration can alter the risk even when the organisation\u2019s main activity stays the same. Product and safeguarding teams should be involved before launch.<\/p>\n
For a review of platform terms, supplier contracts and child-safety governance, contact Prosperiti about digital safety advisory<\/a>.<\/p>\n You can also reach us on WhatsApp at +971 58 567 3776<\/a>.<\/p>\n This article provides general information. Duties depend on the service, users, jurisdiction and implementing measures; the social-media transition should be checked against current official guidance.<\/p>\n [1] Permanent Committee for Human Rights \u2014 UAE adopts Child Digital Safety Law<\/a><\/p>\n [2] Ministry of Family \u2014 Guidance on children\u2019s access to social-media platforms<\/a><\/p>\n [3] Abu Dhabi Early Childhood Authority \u2014 Emirati Children\u2019s Day Guide 2026<\/a><\/p>\nOfficial sources<\/h2>\n