Data processing agreement
In hosted Eguahe, the data belongs to the school that signs up for it. Oksigenia processes it only on the school’s behalf, so that Eguahe works, and this agreement says how, as required by Article 28 of Regulation (EU) 2016/679 (GDPR).
It forms part of the terms of service and is accepted with them. If your school needs to sign it separately, or has its own template, write to us at privacidad@oksigenia.com.
1. The parties
- Controller: the school or institution that signs up for Eguahe (the client).
- Processor: Oksigenia SL, NIF B24911489, with the details in the legal notice. About your data: privacidad@oksigenia.com.
2. Subject matter and duration
Oksigenia processes, on behalf of the controller, the personal data needed to provide the hosted Eguahe service in the school’s installation. The processing lasts as long as the service. The duty of confidentiality continues afterwards.
3. Nature and purpose
Oksigenia stores, organises, consults, sends, copies, retrieves and deletes the data so that Eguahe works: how families and students come in, their page, emails and messages, visits, open days and their sign-ups, the team’s inbox and records, places, re-enrolment, the welcome (the first-day story and the birthday greeting, with each child’s name), the numbers, the forecast, reports and backups, and to provide the support the controller asks for.
Never for anything else: no advertising, no profiling, no scoring of families, no selling or passing data to anyone, no training of artificial intelligence models.
4. What data
- Families and students who sign up: the adults’ full name, email and phone number; for each child, or for the student themselves, their name, what they are called at home, their name in Latin letters if it is written in another script, their date of birth (if given) and the year group they apply for; their language, their municipality and whether they are moving to the area; how they heard about the school and, if they wish, which family told them about it; what they answer in the entry form and in surveys; and, if they want to tell, what they like doing, so they can be invited to events that match it.
- What they send: messages and, if the family uploads it, the photo of each child’s drawing with its strokes.
- Their journey with the school: messages and logged calls, the visits and open days they sign up for and whether they came, the permissions they give for the school to write to them, what the team promised, the place, enrolment, the first day or the reason they leave, re-enrolment, siblings who will come later and whether they offer to tell another family how it went.
- What they do on their page: when they open it and which parts they reach, and which links in the emails they click; never whether they open an email.
- What the school’s AI writes, if the school switches it on: drafts, which a person reads and sends, and the summary of where each family stands.
- What the school uploads: contacts from previous years and student lists (year group, class, year of birth, municipality, joining and leaving), for the numbers and the forecast. When they are uploaded, Eguahe removes names, email addresses and phone numbers, and matches families and students using pseudonymous keys. And, if the school uses the shared family record, the students already at the school, with their name and class.
- Staff: each team member’s account, their role, their photo, their job title and their name if the school shows them to families, when they are away, and what they do in Eguahe.
- Technical: IP address and time in the server logs.
Eguahe does not ask for special categories of data. If the school writes them in a free-text field, it is up to the school to rely on one of the grounds in Article 9 of the GDPR.
5. Whose data
Families interested in the school and their children, including minors; students who sign up on their own; students and families already at the school, if the school brings them in; those from previous years that the school uploads, without names; and the school’s staff.
6. What Oksigenia does
- Process the data only on the controller’s instructions (these terms, what it sets up on its screens and what it asks for in writing), including for transferring it outside the European Union, unless a law requires Oksigenia to do otherwise; in that case, Oksigenia tells the controller first, if that law does not forbid it. If an instruction goes against data protection law, Oksigenia tells the controller.
- Make sure that anyone at Oksigenia who accesses the data does so only when needed (a support request or an incident), only to what is necessary and under a duty of confidentiality.
- Apply the security measures in section 12.
- Use sub-processors only as section 7 says.
- Help the controller respond to people’s rights: Eguahe comes with the tools to view, correct, export and delete a family’s data, and the family itself downloads and deletes it from its page, with one button. If someone writes to Oksigenia to exercise these rights, Oksigenia passes the request on to the controller without delay and tells that person.
- Help the controller with security, breach notifications, the data protection impact assessment and prior consultation, giving it the information it needs.
- Return and delete the data at the end, as section 10 says.
- Make available to the controller the information that shows Oksigenia complies, and allow the audits in section 11.
- Keep the record of the processing activities it carries out as processor.
7. Sub-processors
The controller authorises Oksigenia to use these providers, which are bound by contract to the same obligations as this agreement. Oksigenia is liable to the controller for what they do with its data, as if Oksigenia had done it itself:
- OVH: the service’s servers and their snapshots, in a data centre in the European Union.
- Cloudflare: protects and speeds up connections to the installation, which pass through its network, and receives the mail for the school’s admissions mailbox to pass it on to the school’s installation.
- Scaleway: sends Eguahe’s emails to families and to the team, from France.
- Google: stores the server backups, encrypted before they leave: Google cannot open them.
- Proton: receives the email written to Oksigenia, including support email, in Switzerland.
Oksigenia’s voice bank, on its own servers, records each child’s name spoken aloud for their story and their birthday greeting. It receives only a first name, its language and the reading (with a female or a male teacher; in Arabic, for a girl or for a boy), with no surnames, dates or anything that links it to a person. The recording is stored in the school’s installation.
If Oksigenia wants to add or change a provider, it gives at least 30 days’ notice. The controller can object on data protection grounds and, if no agreement is reached, cancel and be refunded the part paid that it has not used.
What the school contracts on its own is between the school and that provider: an artificial intelligence service with its own key, or its Telegram bot and its WhatsApp number. The AI is off until the school switches it on. When it is on, Eguahe sends the AI only what each task needs: the families’ texts without email addresses, phone numbers or links, and aggregated numbers, never a list of families. Oksigenia still processes what is sent on the school’s behalf, and stores the keys in the school’s installation, visible only to those who administer it. If a provider were to start processing data on Oksigenia’s behalf, it would be added to this list.
8. Outside the European Union
The data is stored in the European Union. It only leaves it, when needed, through Cloudflare, with the safeguards of the GDPR: the EU-U.S. Data Privacy Framework or the European Commission’s standard contractual clauses. Switzerland has an adequacy decision from the Commission.
9. If there is a breach
If Oksigenia becomes aware of a breach affecting the school’s data, it tells the controller without undue delay and within 48 hours at most, with what it knows: what has happened, which data and how many people, what it may mean and what is being done. Anything still missing, it reports as soon as it knows. Notifying the authority and the individuals is the controller’s task, and Oksigenia helps.
10. At the end
While the service lasts, the controller can download its data whenever it wants, in open formats, and ask for a full copy of its installation.
At the end, the controller chooses: take its data and have it deleted, or just have it deleted. It has 30 days to download whatever it wants. After that, Oksigenia deletes its entire installation, with all its data and accounts. The server backups, encrypted, are not used for anything else and disappear as they are renewed, within 12 months at most; if one ever had to be restored, that school’s data would be deleted again. If the controller asks, Oksigenia confirms the deletion in writing. Only what a law requires to be kept is kept, and only for as long as it requires.
11. Audits
Oksigenia gives the controller the information it asks for to check that Oksigenia complies with this agreement. If the controller wants an audit, it can carry it out itself or through someone bound by a duty of confidentiality, with 30 days’ notice, once a year and at its own cost, without seeing anything from other schools. If there has been a breach, or an authority asks for it, or a law requires it, then whenever needed. Oksigenia also deals with its data protection officer, through the email address above.
12. Security measures
- All connections encrypted (HTTPS).
- Each school in its own installation, separate from any other.
- Passwords stored so that no one can read them, and two-factor authentication for anyone who wants it, with an authenticator app or a passkey.
- The keys for the services the school connects, stored in its installation and visible only to those who administer it.
- A copy of the installation every night; the server backups, encrypted before they leave.
- A log of who did what in the installation.
- Only what is needed about each person: what the school does not need to keep is deleted within the period it chooses, what a family deletes remains only as a number without a name, and what is shown about a group is aggregated and without names.
- Security updates for the system and for the platform the service runs on, kept up to date, and security reviews of the code.
- Development and testing with sample data.
- The service monitored, so that any failure is known straight away.
13. What the controller does
Have a legal basis for processing the data of families, students and its staff, and inform them; ask families for permission where needed (Eguahe asks for it before sending them anything they have not requested); give its instructions in writing; carry out the data protection impact assessment if it is required to; and look after its team’s accounts.
Last updated: November 2026.