No DMs, open message boards, or unmoderated kid-to-kid communication in the current school plan.
Build the school
with parents in the room.
Dungeon Academy is still an enrichment beta. This page explains the safety posture before broad enrollment: parent-managed records, minimal data, no ad model, and private family tools while billing and entitlements mature.
The safety lines are intentionally boring
Kids can have fantasy, art, challenge, and progress without open social risk. These boundaries should stay obvious before any family pays.
Learner identity, progress, and records stay inside the parent-managed family path.
Membership and billing decisions belong to the parent or guardian.
Dungeon Academy lessons, records, and membership should stay inside the family learning product.
Showcase work must stay curated, synthetic, or guardian/reviewer-approved before anything public.
Academy is enrichment beta until records, policies, and accreditation work are actually ready.
Gmail, parent consent, learner passport, and reports stay in the parent-managed path.
Current records focus on learner name, guardian email, consent state, progress, reports, and sync IDs.
No child-facing behavioral ads, no public child profiles, and no social posting loop are part of the school MVP.
The public sampler collects no child account data; member school access is protected.
What is already true
Open to families without Gmail so kids can try one real lesson before any account work.
Temporary protected access for the full school, reports, and saved records until individual recovery is complete.
Learner profile, guardian consent, sync packet, weekly report, and dashboard readiness are visible to parents.
Parents can copy or download reports, record packs, sync packets, and mastery summaries from the beta tools.
Before broad enrollment, privacy policy, terms, deletion flow, billing, and account recovery need final review.
The safety backlog
This is the checklist that should be completed before treating Dungeon Academy like a normal public online school product.
Publish a legal-reviewed notice that explains collection, use, disclosure, retention, and deletion.
Replace local beta consent with production-grade parent consent and audit logs.
Use individual parent entitlements and account recovery for paid Academy rooms.
Give parents a clear way to request review, export, correction, and deletion of learner records.
Document AI art, voice, analytics, hosting, and payment vendors before broad family enrollment.
Official privacy sources to review
This page is not a final legal policy. It is the operating charter for the beta while the formal privacy and terms work is prepared.
Children's privacy requirements for online services directed to kids under 13.
Official sourceFTC COPPA FAQBusiness guidance on notice, consent, parent rights, and data practices.
Official sourceStudent PrivacyU.S. Department of Education resources for FERPA, PPRA, and student privacy practices.
Official sourceUse the demo, then review privacy before opening protected access.
The safety charter works best as a parent checklist: try the free room, read the data posture, then use the member gate only when the beta limits are clear.
Read privacy charterBest next step for parents checking child-data and record boundaries.
