1. Who is responsible for your information
There are two situations, and the difference matters:
- Information a school puts into EduOS, or that you give to a school through EduOS (student records, grades, attendance, coursework, messages, applications, payments to the school). The school decides what is collected and why, so the school is the controller (in US education law, the school is responsible under FERPA). EduOS acts as the school's processor or service provider and uses this information only to provide the service to that school, under our Data Processing Addendum. To use your rights over these records, contact the school; we will help them answer.
- Information about our own customers and visitors (the people who sign up a school, contact us, pay us for EduOS, or visit eduos.app). Here EduOS is the controller.
2. What we collect
You give us
- Account details: name, email address, password (stored only as a salted hash), and optionally a phone number, photo and passkeys.
- School account details: the school's name, address, website, and billing contact.
- Content you create or upload: courses, lessons, messages, files, answers, essays and comments.
- Messages to our support team.
Collected as you use EduOS
- Security and service logs: IP address, browser and device type, pages requested, sign-in times, and errors. We use these to keep accounts safe, prevent abuse and fix problems.
- Learning activity a school's course needs: lesson progress, quiz and exam answers, time watched on recorded lectures, and, only when a school turns on exam proctoring, the integrity signals that school chose (described to the student before the exam starts).
- Cookies that are strictly necessary for signing in and security. Anything else needs your consent: see the Cookie Policy.
From others
- From your school, when it adds you (for example a class list).
- From services you choose to connect, such as signing in with Google or Microsoft, or a school importing a Google Classroom roster. We receive only what is needed for that feature.
- From payment processors: whether a payment succeeded. We never receive or store full card numbers.
3. How we use it
- To provide EduOS: run accounts, deliver courses and records, send the emails and messages the service needs, and process payments.
- To keep it safe: detect and stop fraud, abuse and attacks, including bot checks on public forms.
- To support you and improve the product, using aggregated or de-identified usage information.
- To meet legal obligations, such as tax records for our own invoices.
Our legal bases under the GDPR are: performing our contract with you or your school; our legitimate interests in running and securing the service (balanced against your rights); your consent where we ask for it (for example non-essential cookies); and legal obligations.
We never sell or rent personal information, use student information for advertising or to build profiles for non-educational purposes, or use school records to train AI models.
4. AI features
EduOS has optional AI features (for example drafting a lesson, suggesting feedback on an essay, or an assistant for staff). Each school switches each one on or off. When they are used:
- We send only what the task needs. The staff assistant is built so that names, email addresses and other personal details from records are not sent to the AI model; it works with counts and identifiers and fills in names on our side.
- Our AI provider processes requests on our behalf, under terms that forbid using them to train its models, and deletes them after a short abuse-monitoring period.
- AI never makes final decisions about a student's grade or admission; a person confirms.
6. How we protect it
- Encryption in transit (TLS) and at rest. Secrets such as connected account keys are additionally encrypted in our database.
- Each school's records are separated at the database level (row-level security), so one school can't read another's.
- Two-step verification and passkeys, sign-in rate limits and lockouts, and an audit log of sensitive actions.
- Uploaded files are checked for type and malware before use.
- Access by our staff is limited to what support and operations need, logged, and protected by two-step verification.
No system is perfectly secure. If a breach affects personal information, we notify affected schools without undue delay (and within 72 hours of confirming it where the law requires), and help them inform the people involved. More on the Security page.
7. How long we keep it
- School records: while the school uses EduOS. When a school closes its account, it can download everything; we delete the records within 30 days, and they leave our backups within a further 30 days.
- Your account: until you or your school delete it. You can delete your own account from your account settings.
- Security logs: up to 12 months. Our own billing and tax records: as long as the law requires.
8. Your rights and choices
Depending on where you live (for example the GDPR in the EU and UK, or state laws such as the CCPA/CPRA in California), you may have the right to access, correct, delete or download your information, to object to or restrict some uses, and to withdraw consent. We do not sell or "share" personal information for cross-context behavioral advertising, so there is nothing to opt out of there.
- You can download your data and delete your account in Account settings.
- For school records, ask your school. Parents and eligible students may review and request corrections to education records through the school, as FERPA provides.
- For anything else, email hello@eduos.app. We answer within 30 days and won't treat you differently for using your rights. You may also complain to your data protection authority.
9. Children
Children use EduOS through their school. For children under 13 in the United States, we rely on the school's authorization under COPPA, and use their information only for the school's educational purposes. Schools can ask for a parent's or guardian's agreement before a younger learner signs up on their website. We don't knowingly collect information directly from children outside a school's use of EduOS; if you think we have, contact us and we'll delete it. See Student data commitments.
10. International transfers
EduOS is run from the United States. When we move personal information from the EU, UK or Switzerland, we rely on the European Commission's Standard Contractual Clauses (and the UK addendum), with the safeguards in our Data Processing Addendum.
11. Changes to this policy
If we make a material change, we'll tell schools by email and in the product at least 30 days before it applies. We'll never make a change that lets us use student information in a less protective way without the school's agreement.
Contact
EduOS. Privacy questions: hello@eduos.app. Security reports: hello@eduos.app.
If a translation of this page differs from the English version, the English version applies.