KidChatAll documents

DRAFT — not legally published. Counsel review pending. Do not rely on this text as a published policy.

Publication Gate

Every public claim, its control, and whether it is safe to publish yet.

PHASE B — FINAL PUBLICATION GATE TABLE

Every material public claim across Phase B documents 1–10, mapped to its control ID and its publication status. A row that is not SAFE TO PUBLISH: YES may not appear in any published document, marketing page, or product surface.

Doc key: 1 Children's Privacy Notice · 2 Parent Privacy Policy · 3 Parent Consent · 4 Terms · 5 Child Safety · 6 Responsible AI · 7 Parent Rights · 8 Security/Trust · 9 Cookies · 10 AUP

Public claimDocumentControl IDImplemented?Verified?Safe to publish?Launch blocker?
A parent must set up every child profile; children cannot sign themselves up1,3,4,10C-01Partial (parent account required; server-side binding pending)NoNo — not until server check existsYes
KidChat is for children aged 6–121,3,4,10C-02Partial (UI only)NoNo — needs server-side age gateYes
We ask for a parent's verifiable consent before a child can use KidChat3,4C-03NoNoNoYes
Conversations are kept for 30 days and then deleted1,2,3,7C-04No (no deletion job)NoNoYes
A parent can delete a child's profile and its data2,3,7C-05No (cascade workflow pending)NoNoYes
We remove personal details before sending a question to the AI6C-06NoNoNo — `[DO NOT PUBLISH UNTIL C-06/C-07 VERIFIED]`Yes
We don't keep the private detail we removed6C-07NoNoNo — `[DO NOT PUBLISH UNTIL C-06/C-07 VERIFIED]`Yes
Children's conversations are not used to train general-purpose AI models2,3,6C-08No (contracts unsigned)NoNo — `[DO NOT PUBLISH UNTIL C-08 SUBSTANTIATED]`Yes
We don't sell children's data or use it for advertising2,4,6,8,9C-09Yes (no ad tech present)Pending dependency auditYes, after auditNo
No third-party analytics runs in Kid Mode8,9C-10Yes (none installed)No automated assertionYes, after automated assertionNo
"Your grown-up / your parent or guardian can see your KidChat conversations"1,2,4,5,7C-11Partial (copy drafted, not persistent in product)NoNo — until the persistent child notice shipsYes
Parent access to conversations is protected and recorded2,7,8C-12Partial (PIN exists; no audit log)NoNo — drop "and recorded" until the log existsNo (high priority)
If a child seems to be in danger, KidChat shows real help lines5C-13No (no directory, no fail-closed)NoNoYes
A person at KidChat reviews the most serious safety events5C-14Partial (owner named, no queue)NoNo — and never with an SLA or 24/7 wordingYes
KidChat cannot call emergency services or contact anyone outside KidChat1,3,4,5,10C-15N/A (limitation)N/AYes — must be statedMust be stated
Voice features are turned off3,8C-16Partial (feature exists; server flag pending)NoNo — until endpoints are unreachable behind the flagYes
We encrypt data in transit and at rest2,8C-17YesWording not yet matched to provider docsYes, once wording matches provider docsNo
We keep a record of what each AI request cost, without keeping what was said6,8C-18No (ledger not built)NoNoNo (high priority)
Available in Mexico; not offered to children in the UK or EU2,3,4C-19No (no geo control)NoNo — until the region block existsYes
KidChat uses AI and can be wrong1,4,6,10C-20N/A (limitation)N/AYes — must be statedMust be stated
Consent uses an approved payment-method verification flow or another legally accepted mechanism3C-21 (new)NoNoNo[COUNSEL REVIEW REQUIRED — VPC IMPLEMENTATION]Yes
Verification information is minimized and promptly deleted3C-22 (new)NoNoNoYes
Deletion from active systems as soon as reasonably practicable; backups purged on a rolling cycle2,7,8C-23 (new)NoNoNo[TECHNICAL VALIDATION REQUIRED — BACKUP RETENTION]; never publish "deleted within 30 days from all systems"Yes
privacy@kidchat.io (and safety/legal/security) reach a real, responsible human1,2,3,7,8C-24 (new)No (aliases not live)NoNoYes — privacy@ must be monitored before the first real child's data is collected
Screen-time rules, allowed windows, breaks, and PIN-granted extra time7C-25 (new)YesYes (tested in product)YesNo
One family's data is isolated from another's (row-level security)8C-26 (new)YesYesYesNo
Session recaps, topics, and safety indicators visible to the parent7C-27 (new)YesYesYesNo
No certification or audited-compliance claim8N/AN/ANever claim

SUMMARY

Safe to publish today: C-09 (after audit), C-10 (after assertion), C-15, C-17 (wording), C-20, C-25, C-26, C-27.

Launch blockers still open: C-01, C-02, C-03, C-04, C-05, C-06, C-07, C-08, C-11, C-13, C-14, C-16, C-19, C-21, C-22, C-23, C-24.

Open for counsel only: Resolved: KidChat is a technology service operated by NOXON, LLC, a Texas limited liability company. [COUNSEL REVIEW REQUIRED — PRIVACY CONTROLLER / RESPONSIBLE ENTITY ADDRESS], [COUNSEL REVIEW REQUIRED — GOVERNING LAW / DISPUTE RESOLUTION], [COUNSEL REVIEW REQUIRED — VPC IMPLEMENTATION], [COUNSEL REVIEW REQUIRED — MANDATORY REPORTING POSTURE].

No Phase B document may be published while its own gates and the rows above remain unresolved. Phase C does not begin until this table is reviewed.

Who operates KidChat

KidChat is a technology service operated by NOXON, LLC, a Texas limited liability company.

KidChat es un servicio tecnológico operado por NOXON, LLC, sociedad de responsabilidad limitada constituida en Texas, Estados Unidos.

NOXON, LLC — Texas, United States. privacy@kidchat.io · safety@kidchat.io · security@kidchat.io · legal@kidchat.io

© 2026 KidChat. Operated by NOXON, LLC.