Legal & Compliance
Every document a school, district or parent might need — and a plain account of how student privacy is actually protected, not just promised.
The one-paragraph version
Students have no accounts and give us nothing. A student joins a game with a 6-character code and is assigned an anonymous alias like “Cactus7”. We never ask for — and our database physically rejects — a student name, email, photo, address or phone number. Class rosters, if a teacher uses them, are stored in that teacher’s own browser and never transmitted to us. The only personal information Outlaw Roundup holds is the teacher’s account: their email, name and school.
Documents
Privacy Policy
EveryoneWhat is collected, what is not, who can see it, how long it is kept, and how to have it deleted.
Read →Terms of Use
EveryoneThe agreement covering use of the service, acceptable use, and limitations of liability.
Read →End-User License Agreement
TeachersThe licence granted to you for the software itself, and what you may and may not do with it.
Read →Data Processing Agreement
DistrictsA ready-to-sign DPA naming the parties, processing purposes, sub-processors, retention and breach terms.
Read →Information for Schools
DistrictsData residency, infrastructure, security measures, and the regional answers procurement asks for.
Read →Help & Setup Guide
TeachersSetup steps, network requirements and troubleshooting — including what to unblock on a school network.
Read →How we meet school-district requirements
The table below maps each regulation to the specific design decision that satisfies it. Most of them are satisfied the same way: we do not collect the data in the first place, which is a far stronger guarantee than a policy promising to look after it.
| Regulation | Region | How Outlaw Roundup satisfies it |
|---|---|---|
| COPPA | United States | COPPA governs collecting personal information from children under 13. We collect none: students provide no name, email, or identifier of any kind, and the database rejects writes containing those fields. With no personal information collected, there is no verifiable-parental-consent obligation to discharge. |
| FERPA | United States | Game results are alias-keyed performance data held on the school’s behalf. The teacher who ran the session is the only person who can see it, can export it, and can delete it at any time. We never use it for any purpose other than showing it to that teacher — see the DPA, “Prohibited Uses”. |
| PPRA | United States | No surveys, no political, religious, behavioural or family questions. The only content is vocabulary a teacher wrote or approved. |
| State student-privacy laws (SOPIPA-style) | United States | No advertising, no ad profiles, no sale of data, no third-party analytics or tracking scripts anywhere on the site. Nothing is disclosed to anyone for marketing. |
| PIPEDA | Canada | Teacher accounts are created with informed consent at sign-up; the purpose is stated, limited and not repurposed. Teachers can export or delete their data themselves at any time from Account settings. |
| FOIP | Alberta | Student data is minimised to pseudonymous aliases, and the school remains the custodian of any roster that links an alias to a student — that link exists only in the teacher’s own browser and never on our servers, so it never leaves the school’s control. |
| Accessibility (WCAG 2.1 AA / AODA) | All | Keyboard-navigable interfaces, semantic headings, visible focus states and high-contrast text on opaque surfaces. See the accessibility statement below for what is verified and what is still being improved. |
This table describes our design and practices; it is not legal advice, and it is not a substitute for your district’s own review. Districts are welcome to verify every claim here — see “For district reviewers” below.
Sub-processors
The complete list of third parties that process any data on our behalf. There are no others, and none of them receive student data.
| Provider | Purpose | Data | Region |
|---|---|---|---|
| Google Firebase | Database, sign-in | Teacher account records; alias-keyed game data. No student personal information. | See /school-info |
| Vercel | Application hosting | Serves the site. Standard request logs; no student data stored. | Global edge |
| Stripe | Payments (optional) | Teacher email and card details for the optional Supporter plan. Cards are entered on Stripe's own pages — we never see them. No student data. | United States |
| OpenAI | Word bank generator (optional) | Only the topic or passage a teacher types in. No student data and no teacher identity are sent. | United States |
We notify schools with a signed DPA before adding a sub-processor that would handle school data.
Security controls
- Encryption. All traffic is HTTPS, with HSTS instructing browsers never to try plain HTTP. Data is encrypted at rest by Google Cloud.
- Database-level access control. Access is enforced by Firestore security rules on Google’s infrastructure, not by our application code — so a bug in the app cannot expose another teacher’s data. The rules are covered by an automated test suite that runs before every change.
- PII rejection at the database. The rules actively reject any student record containing an email, real name, phone, address or photo. Sending us student personal information is not merely against policy — it fails.
- Administrative access is logged. Every action taken by a Outlaw Roundup administrator is written to an append-only audit log recording who did what, to which record, and when.
- Least privilege. Administrative roles are separated, and the actions that can destroy or expose data are restricted to the highest role and individually confirmed.
- Hardened browser policy. The site sends a content security policy, frame-blocking, MIME-sniffing protection and a restrictive permissions policy that denies camera, microphone and location outright.
- Abuse limits. Sign-in and public endpoints are rate limited, so credentials cannot be guessed at speed and game codes cannot be enumerated.
Data retention and deletion
- Teachers set the retention window in Account → Privacy. Game sessions are deleted automatically once it passes.
- Any session can be deleted immediately by the teacher who ran it.
- Deleting a teacher account removes everything — every game, every question set, every class, and the sign-in itself. It is immediate and irreversible.
- Schools can request deletion of any session or account on the school’s behalf; see the contact details on Information for Schools.
Accessibility statement
Outlaw Roundup targets WCAG 2.1 Level AA. The game is designed for classrooms that include students using assistive technology and school-issued devices of varying quality.
- All interactive controls are reachable and operable by keyboard.
- Text sits on opaque surfaces chosen for contrast rather than translucent overlays.
- Headings are semantic and ordered, so screen readers can navigate by structure.
- No content flashes more than three times per second.
- Colour is never the only way information is conveyed.
Accessibility is an ongoing commitment rather than a finished state. If any part of the game is difficult for one of your students to use, please tell us — reports from real classrooms are the fastest route to a fix.
For district reviewers
If you are evaluating Outlaw Roundup for a school or division, these are the things worth asking for, and our answers:
- A signed data processing agreement
- Use our sample DPA or send us yours. We will sign a reasonable district agreement.
- A list of every data element collected
- Published in full in the Privacy Policy, field by field, including the ones we deliberately refuse.
- Proof that student PII cannot be stored
- Our database rules reject it, and we can walk your IT team through the rule and the test that proves it.
- Breach notification terms
- Set out in the DPA. We maintain a written incident response procedure.
- What to allow on the school network
- Listed on the Help page so your filter can be configured before the first lesson.
A note on scope. These pages describe how the service is built and operated. They are not legal advice, and no page here creates a contract on its own — the Terms of Use and any signed DPA govern. Districts should apply their own review process, and we will support it with whatever detail you need.