Checked against official sources on 21 October 2026. This is a course setup guide, not a claim that accounts have been created or that each feature has been tested with these learners.
Google documents parent-enabled Gemini Apps access for an under-13 child's own Family Link-supervised account. Rollout is gradual, some features have separate age restrictions, and availability must be checked in the actual account. Google also advises parents to explore and supervise use. This is not a shared adult login. Google supervised Gemini guidance.
The UAE appears on Google's general Gemini web availability list, but that does not prove supervised access has reached any particular account. Google availability list.
Google's general help documents coding-related chat and copying code responses. The proposed route is ordinary Gemini chat → copy complete HTML → inspect and edit → local browser. That route is an inference to test, not a verified under-13 coding-feature guarantee. No Canvas, AI Studio, Gemini API, API key, or special agent feature is required. Google chat and code-response help.
If the route is unavailable, keep doing real-source coding with the starter. Mark AI generation pending. Do not bypass an age or feature restriction.
Replit's terms require age 13 or older and parent or guardian permission for under-18 users. An own-account Replit route is therefore a candidate for the older learner after parental setup and an actual feature check. The terms do not establish free credits, unrestricted agents, or permission for purchases and publishing. Replit terms.
The parent should check that the intended plan can produce and expose a small app's source, run its preview, and retain an export. If that route is unavailable, a verified eligible conversational AI plus local source editing can still teach genuine AI-assisted coding.
Lovable's privacy policy says personal accounts require age 18. It describes a separate supervised under-18 route under a written organizational agreement. Ordinary parental supervision is not that agreement. Even if other wording appears less restrictive, do not create either learner a personal account on that basis without resolving the service's requirements. Lovable privacy policy, Children section.
Passing this preflight checks the route, not every future AI response. Continue oversight and pause for unexpected permissions, money, private data, downloads/installations, or publishing.
The existing course is an introductory guided lab. The local Code Desk review build is implemented for editing, version saving/restoring, and exporting only. It has no Run button, and the learner’s own device and external account still need checking. An arbitrary-code iframe runner is not implemented or security-verified. Do not describe it as an offline or network-blocked sandbox.
Use a parent-set-up local editor/browser or an eligible Replit preview. Local HTML is not automatically safe simply because it is local; generated scripts can make network requests or navigate. The supplied reference app contains no such features, but new generated code requires its own review. Cloud previews have their own access and visibility rules. No public sharing is required for course completion.
OpenAI's applicable individual-service terms require at least age 13 or the relevant country minimum, parental permission under 18, and no shared account access. This makes an own-account Codex route a candidate for an eligible learner aged 14 after setup, not an independent route for a learner aged 12. Actual product access, device support, rollout, permissions, plan, and cost still need checking; no Codex workflow has been tested for these learners. OpenAI terms, service terms, and current pricing/access information.
Do not promise free web, CLI, IDE, or desktop access from a general plan label. Keep Replit or the verified chat-plus-local route as the concrete lessons until a specific Codex route passes preflight.
Before any hosted creation, the parent checks the exact route's plan, charges or credits, project visibility, and preview access. The Replit-in-ChatGPT documentation has route-specific privacy and billing details, so a connector-created project must not be assumed equivalent to the direct Website workflow. No actual learner-account build or private Replit demo has been verified here. Replit integration documentation.