Edus

Privacy policy

Last updated 1 August 2026

science
This is a prototype. Every record in it is fictional demo content, and nothing you type here is stored on a server.

1.Who controls your data

Your institution is the data controller. Edus processes student and staff records on its instructions and does not decide on its own what happens to them.

That means access requests, corrections and deletions go through your campus admin first. We act on their verified instruction.

2.What we collect

Account data (name, institutional email, role, staff or student ID), the academic and administrative records your institution enters, and technical logs — sign-in times, IP address, browser and the pages you open.

We do not collect payment card details; billing is handled by your institution’s finance office.

3.Why we process it

To provide the service your institution has contracted for, to keep accounts secure, to meet the reporting duties institutions have to their regulators, and to fix faults.

We do not sell personal data, and we do not use student records to target advertising.

4.AI features

The assistant, timetable suggestions and voice minutes process the records you point them at. Outputs are drafts for a human to approve — nothing is actioned automatically.

Your institution’s data is not used to train shared models.

5.Who else sees it

Other users at your institution, according to their role. Cloud hosting, email delivery and error-monitoring providers act as our processors under contract.

We disclose data to authorities only where the law requires it, and tell your institution unless we are barred from doing so.

6.How long we keep it

Records live as long as your institution’s contract, then for the statutory retention period that applies to student records in your jurisdiction. Technical logs are kept for 90 days.

7.Your rights

Access, correction, deletion, restriction, portability and objection, exercised through your campus admin. Where your institution cannot act, write to privacy@edus.example.

8.Security

Encryption in transit and at rest, role-based access control, audited administrative actions, and password policy enforced server-side. Report anything suspicious via Get help.