Kids' Safety & COPPA

How JCIL.AI handles K-12 school deployments under the Children's Online Privacy Protection Act. Plain language, no legalese.

Default posture

JCIL.AI is not directed at children under 13. Our consumer signup flow (jcil.ai/signup) requires users to be 13+. We do not advertise to children, build behavioral profiles on children, or use child content to train AI.

K-12 school deployments

Christian K-12 schools, youth ministries, and similar institutions can deploy the JCIL Cloud widget in contexts where under-13 students may use it. When that happens:

  • Your school or institution is the COPPA "operator"under the FTC's school-authorization guidance (2014). Parental consent is obtained by your school, not by JCIL.AI directly.
  • JCIL.AI acts as a service provider under school authorization. We Process student data only for the educational purpose you configure in the widget's custom prompt.
  • No ad targeting, no profile building, no cross-site tracking, no third-party advertising pixels. Ever.
  • No training on student content. Our API providers do not train on JCIL API traffic.
  • Data retention is limited to the minimum necessary for the educational purpose. Schools can request deletion at any time via the compliance contact form with topic COPPA / K-12 deployment — we honor deletion requests within 30 days.

What schools must do

  1. Notify parents that JCIL.AI is deployed in the student environment (a line in your existing tech/privacy notice is usually sufficient).
  2. Obtain parental consent through your institution's existing consent mechanism (enrollment paperwork, parental-consent portal, etc.) — COPPA permits school-authorization consent for classroom tools, but your institution is responsible for confirming the consent chain.
  3. Configure the widget's custom prompt to match the educational purpose. Do not collect data beyond what the lesson requires.
  4. Enable the safety webhook so crisis signals route to your on-call staff (school counselor, designated administrator) — not to a generic inbox.
  5. Periodically request deletion of student data at term boundaries (semester end, school year end) via the compliance contact form.

What JCIL.AI will not do

  • Market to children or their parents based on conversation content
  • Transfer student data outside the United States
  • Retain data beyond the educational purpose without a legitimate reason (e.g., legal hold)
  • Share student data with any third party outside the subprocessors listed on the subprocessors page
  • Produce or serve any content sexualizing minors (moderation pipeline blocks this at the platform level and escalates to immediate account termination + NCMEC report)

Data subject rights for parents

Under COPPA, parents have the right to review, request deletion of, and refuse further collection of their child's Personal Information. Since JCIL.AI operates under school authorization, parents exercise these rights through the school; the school then relays the request to us.

If a school cannot or will not relay a parental request, parents may contact JCIL.AI directly via the compliance form with topic COPPA / K-12 deployment. We'll verify the parental relationship and honor the request within 30 days.

Age-gating on the consumer product

The consumer chat at jcil.ai (not the JCIL Cloud widget deployed by schools) requires users to confirm they are 13+ at signup. If we learn that a child under 13 has created a consumer account without school authorization, we delete the account and its associated data on learning about it.

Last updated: April 17, 2026. This page reflects current FTC guidance on the COPPA school-authorization framework. Pending FTC rulemaking may alter this posture; we will notify K-12 customers of material changes.