For school IT
IT kit
Updated October 24, 2026
KiteQuad is built to need as little from your network as possible. Allow three hostnames and you're done — two for students, one for teachers.
The short version
- Allow
kitequad.schoolandkitequadusercontent.com(with their subdomains) for students. - Allow
kitequad.comfor teachers. - Allow the camera on
kitequad.schoolif your students sign in by scanning a QR badge. - No third-party trackers, analytics or fonts load on any student page — nothing else to allow.
What to allow in your web filter
| Allow | Who needs it | What it's for |
|---|---|---|
kitequad.school and its subdomains (*.kitequad.school) | Students | Where students sign in and open your apps. |
kitequadusercontent.com and its subdomains (*.kitequadusercontent.com) | Students | The locked-down domain each app's own files are served from. |
kitequad.com | Teachers | The teacher dashboard, where teachers build and publish. Students don't need it. |
Both student hostnames are served over HTTPS on port 443. Allowing the subdomains matters: each app runs on its own subdomain of kitequadusercontent.com, and schools can get a subdomain of kitequad.school, so a rule that allows only the bare domain will miss them.
In a content filter (GoGuardian, Securly, Lightspeed, Cisco and the like)
Add the three entries above to your allow list as domains (with subdomains). If your filter asks for a category, KiteQuad is an educational tool. You don't need to allow any other domain for KiteQuad itself — there are no third-party trackers, analytics or font services on student pages to let through. If your filter does TLS/SSL inspection, exempt the two student hostnames so the sandbox and sign-in work smoothly.
In Google Admin (managed Chromebooks)
If students use managed Chromebooks, make sure the three hostnames aren't blocked by a URL-blocking rule, in Devices → Chrome → Settings → Users & browsers → URL blocking. If you keep a strict allow-list, add them there. No extension or app install is needed — KiteQuad runs in the browser.
The camera, for badge sign-in
If your students sign in by scanning a QR badge, their browser needs permission to use the camera on kitequad.school. KiteQuad only turns the camera on when a student chooses to scan, and the picture never leaves the device. On managed Chromebooks, allow the camera for kitequad.school in Devices → Chrome → Settings → Content → Camera (or your filter's site-permission settings), so students aren't stopped by a prompt. Classes that sign in with a class code and a PIN or picture password don't need the camera at all.
Privacy, in one line
No third-party scripts, analytics or fonts run on any page a student sees, and app code can't reach the network. There's more for your privacy review on the trust center, including where data lives and our breach-notice commitments.
Done looks like: a student on a school device opens a teacher's app, signs in, and uses it — and the leaderboard and saving work — without any page or request being blocked.
Questions
If something's still blocked, or you need these entries in another format, write to support@kitequad.com and tell us your filter and what you're seeing.