🛡️ Privacy • Safety • Originality • Accessibility
LumiQuest Trust Center
V4 is designed around a strict global child-protective baseline. That does not mean one static website can be guaranteed legally compliant in every country; commercial launch still requires operator details, jurisdiction review and production controls.
🔒Private by default
Local progress only in beta.
🚫No behavioral ads
No ad profiling or ad-tech SDKs.
🧒Child-first design
No public profiles or stranger contact.
♿Accessibility target
WCAG 2.2 AA / EAA-oriented design target.
V4 beta protective defaults
These are implemented product decisions, not only policy wording.
✅ No child registration
✅ No exact date of birth
✅ No public child profile
✅ No child-to-child messaging
✅ No geolocation API
✅ No photo/video upload
✅ No third-party analytics
✅ No behavioral advertising
✅ No push notifications
✅ No autoplay feed
✅ No loot boxes
✅ No real checkout
Global design baseline
High-level implementation targets. See the detailed research document in the package for sources and launch actions.
RegionKey child/privacy issueV4 approach
EU / EEAGDPR child consent rules; where DSA online-platform provisions apply, additional minor-safety and profiling-ad restrictions; accessibility/consumer rules.Minimize data; no profiling ads; privacy/safety defaults; plain language; production DPIA and consent layer.
United KingdomUK GDPR plus Children’s Code / age-appropriate design expectations.Best-interests design, high privacy defaults, no manipulative nudges, parent-friendly transparency.
United StatesCOPPA for child-directed services under 13; state privacy/consumer rules may add duties.Beta collects no cloud child personal data; production parent notice/consent and deletion workflow required before accounts.
IndiaThe DPDP Act defines a child as under 18 and contains child-processing/parent-consent obligations; statutory commencement is phased, so the launch review must confirm which provisions are in force.No cloud child account in beta; production India mode should be designed to the strict child/parent-control standard and re-check the phased commencement and final Rules before activation.
SingaporePDPA plus child-data digital-environment guidance and data-protection-by-design expectations.Minimal collection, child-friendly notices and strong default protections.
JapanAPPI consent capacity is context-specific; regulator guidance indicates parental/representative consent may be needed for younger children.Parent-controlled account design and age-appropriate explanations.
South KoreaPIPA requires legal-representative consent when consent is required for children under 14.Regional parent-consent gate before production child accounts.
ChinaUnder-14 personal information receives heightened protection; guardian consent and special handling rules apply.Separate China launch/legal/hosting review; do not enable cloud child profiles by default.
AustraliaPrivacy Act obligations plus a Children’s Online Privacy Code due by December 2026.Track the final Code; maintain privacy-by-design and child-best-interests controls.
Canada / Brazil / UAEStrong emphasis on children’s best interests, transparency, data minimization and/or guardian controls.Strict default profile plus regional legal review before cloud accounts, ads or paid services.
🧒 Privacy for Kids🔒 Privacy Policy👨👩👧 Parent Notice🍪 Cookie & Local Storage🛡️ Activity Safety© Originality & IP♿ Accessibility📜 Terms✅ Acceptable Use💳 Future Subscription Terms
Important: V4 is a technical and policy-ready beta, not a legal certification. China, South Korea, India, US state laws and other local rules can require additional implementation. The package includes a jurisdiction launch matrix and legal-review blockers.