District-wide detection that works with your compliance posture.

About: K-12

K-12 deployment of AI-detection tools is a different animal from higher-education deployment. The detectors are the same; the compliance environment is not. A district buying detection for a 9,000-student footprint has to think about FERPA alignment, COPPA for under-13 users, vendor data agreements, and state-level student-data-privacy laws, before anyone writes a check.

This page is a summary of how aiessaydetector.ai fits into a K-12 deployment. For the line-item compliance matrix, see /for-institutions/compliance. For the technical SSO and integration details, see /for-institutions/sso-deployment.

What K-12 districts get

• Per-student pricing, districts pay once for an enrolled-student count, not per teacher and not per check. Unlimited checks per student within fair-use limits.
• SSO through ClassLink or Clever (OIDC), or direct SAML. No secondary student logins.
• Retention controls, default 30 days, dial-able to zero (scan-and-discard).
• Under-13 mode, when SSO metadata indicates a user is under 13, we apply COPPA-aligned restrictions: no persistent storage, no cross-session history, no marketing.
• Teacher controls, per-school admin panel, per-teacher detection thresholds, roster-aware bulk mode.
• Parent-facing transparency, a district-brandable parent-notice page explaining what the tool does and does not do. Drafted so it doesn't require a lawyer to approve.

What we don't do in K-12

We do not provide student-level surveillance (keystroke logging, screen capture, browsing-history review). We do not sell detection tools as academic-integrity judges; the product is a signal that enters a human process. We do not integrate with filtering or monitoring tools (Gaggle, GoGuardian). If those are the problems you're solving, a detector is the wrong tool.

Typical deployment timeline

1. Intake call with district IT and a curriculum lead (60 minutes). Clarify scope, compliance posture, and target schools.
2. Data Processing Agreement and student-data-privacy addendum. We sign state-specific addenda (California SOPIPA, New York Ed Law 2-d, Illinois SOPPA, etc.) without fuss.
3. SSO pilot with one school (2 weeks). Teachers get training; the first week's detection results are reviewed together before broad rollout.
4. District-wide rollout (4–6 weeks).

Pricing

District pricing is quoted per enrolled-student count, with volume discount brackets. We do not list public K-12 pricing because it depends heavily on the compliance addenda required, the SSO provider, and the retention policy. Submit a quote request via /contact.