Security & privacy
What we do and don't do with student writing.
Plain-English principles. Defensible to writing-center directors, faculty governance, academic integrity offices, and IT.
Coach Mode is server-enforced
Every section AI request runs through a server-side filter that refuses to draft prose for a student. The toggle is not on the client. Prompt-injection attempts are rejected before the model sees them. The full pedagogy, the eight hard rules, and the seven layers of enforcement are published at /education/coach-mode.
Student writing is never used to train models
We send drafts to OpenAI and Anthropic for inference only. Both vendors honor zero-retention contracts for inference traffic on our account. On our side, student AI signals are stored in a separate database table from the one our internal product-quality tooling reads, so student rows are structurally excluded from any future model-improvement pipeline that may use the latter.
No ads. No analytics resale.
Student data does not flow to advertising or analytics providers. We use first-party telemetry only, scoped to product diagnostics.
FERPA-aware educational records
Our pilot cohort is college writing centers, where students are adult learners. Drafts produced inside an institutional section are educational records under FERPA, and we treat them as such: institution-scoped access, no third-party disclosure without authorization, and a clear retention path. We sign FERPA addenda on request.
Adult learners: COPPA does not apply
Our pilot is college writing centers (18+). COPPA covers under-13 use and is not in scope for this cohort. When we open K-12 in phase two, we will publish the under-13 stance and parental-consent flow separately before any K-12 enrollment goes live.
Students own their writing
A student can leave a section at any time and keep every word. The coach loses read access immediately.
Vendor questionnaires welcomed
Email hello@creader.io and we will respond within 5 business days with a completed questionnaire (HECVAT-lite friendly) and any additional documents your IT team requests.
Have a specific question?
- Writing-center directors & English department chairs: for FERPA addenda, vendor due diligence, or to walk through the policy with your office, email hello@creader.io or use the contact form.
- Students: if you're an enrolled student and have a question about what your coach can or cannot see, or about deleting your draft, email hello@creader.io. You can also leave the section at any time and keep every word.
- Institutional IT / vendor due diligence: we respond to questionnaires within 5 business days. Email hello@creader.io with your form, or use the contact form (select “School IT”). The OpenAPI spec lives at /api/openapi and security disclosures at /.well-known/security.txt.
- Academic integrity concerns: if a specific concern about a student's draft has arisen (suspected ghostwriting, Coach Mode bypass, etc.), email hello@creader.io with the section name. We do not auto-flag or block; the coach or faculty member remains the first responder under your institution's academic integrity policy.
- K-12 educators & guardians: K-12 is phase two of our rollout. If you're interested in K-12 access, email us at hello@creader.io and we'll loop you in when the under-13 / COPPA stance and parental-consent flow are published.