Trust
Trust center
Draft — not yet in effect
Draft — under review. This page describes how KiteQuad is built today and is being reviewed by counsel. It isn't a binding policy yet, and the wording may change before launch.
KiteQuad exists to let teachers publish AI-built apps to students safely. This page is where a school's privacy or IT reviewer can find how that works and the documents to review.
The short version
- Anonymous by default. No real student names or email unless a school turns on authorized mode.
- In the United States. The database and files are created in Cloudflare's US jurisdiction; nothing personal is globally replicated.
- Two vendors only: Cloudflare runs the service; Stripe takes a teacher's payment and never sees student data.
- Deletion when you ask, with a certificate of what was removed, and a breach-notice commitment in writing.
Documents
Privacy policy
What we store, for how long, and where.
COPPA school notice
How a school consents, and why anonymous mode needs no real student data.
Security overview
The app sandbox, data location, access control and what we log.
Subprocessors
The two vendors that run the service, what each handles, and where.
Accessibility
Our WCAG 2.1 AA target and how we check every page.
Terms of service
The agreement for teachers and schools.
Vendor risk answers (K-12CVAT)
Our answers to the CoSN/SETDA toolkit, with sources — printable and as a spreadsheet.
Where your data lives
KiteQuad runs on Cloudflare. The database and file storage are created in Cloudflare's United States jurisdiction, and this can't be changed after creation. Requests are served from the Cloudflare location nearest the user, and nothing personal is kept in any globally replicated store. Traffic uses HTTPS, and stored data is encrypted at rest. The subprocessor list names every vendor and where each one is.
How apps are kept safe
A teacher's published app runs on a separate web domain, inside a locked-down frame, with network access blocked. The one channel built for saving a student's work keeps it inside KiteQuad; other ways an app might try to send data out are detected and reported to the teacher. Every app is checked before students see it. The security overview has the detail.
Deletion and certificates
A teacher can delete a student's data, a class's, an app's, or their whole account at any time. Deleting your account, or clearing the data an app saved, takes that data out of the live service within 7 days of the request, with copies in encrypted backups removed within about 30 days after that (about 37 days in all). Deleting a student, class or app record itself — and the student work saved under it — takes it out of the live service within 30 days, again with backup copies removed within about 30 days after that (about 60 days in all). The privacy page has the full retention schedule. For a school ending its use, KiteQuad performs certified deletion and provides a deletion certificate listing what was removed by internal id and count — which is possible because audit records never hold names, nicknames or values.
Breach notice
If a security incident affects student data, KiteQuad will notify the affected schools or districts without undue delay. Our target is to notify within 72 hours of confirming an incident, and in every case within the windows the law sets — including New York Education Law 2-d / Part 121's seven-day requirement and Illinois SOPPA's thirty-day requirement. We maintain a written incident-response runbook, and a school's data agreement sets out the notice in full.
Compliance at a glance
| Requirement | How KiteQuad meets it |
|---|---|
| COPPA (school consent) | School, not teacher, authorizes real data; anonymous mode collects none. Notice. |
| FERPA (school official) | Direct school control under a data agreement; no redisclosure. |
| Written retention policy | On the privacy page; data auto-deletes on schedule. |
| Storage location disclosed; breach notice | United States, above; 7-day / 30-day notice, above. |
| Certified deletion at contract end | Deletion certificate of ids and counts. |
| No third-party disclosure; no AI training | Two subprocessors; neither trains on student data. |
| WCAG 2.1 AA | Target, with axe on every page. Statement. |
| No companion chatbot; AI opt-out | No persona chatbots; student AI is off in R1, with a parent opt-out when enabled. |
Talk to us
For a data privacy agreement, a completed vendor questionnaire, or any question about how KiteQuad handles student data, write to support@kitequad.com. You can also download our vendor-risk answers right now.