Legal texts
Data processing agreement
In the hosted library, the data belong to whoever contracts it. Oksigenia processes them only on its behalf, so that the library works, and this agreement says how, as article 28 of Regulation (EU) 2016/679 (GDPR) requires.
It is part of the terms of service and is accepted with them. If your institution needs to sign it separately, or has its own model, write to us at privacidad@oksigenia.com.
1. The parties
- Controller
- The institution that contracts the hosted library (the customer).
- Processor
- Oksigenia SL, tax number B24911489, with the details in the legal notice. For your data, privacidad@oksigenia.com.
2. Subject matter and duration
Oksigenia processes, on behalf of the controller, the personal data needed to provide the library service hosted on app.ayvurenda.com. The processing lasts as long as the service. The duty of confidentiality continues afterwards.
3. Nature and purpose
Oksigenia stores, organises, consults, sends, copies, restores and deletes the data so that the library works: the catalogue, the readers and their cards, the desk, loans, holds and their notices, activities, help, reports and copies, and to provide the support the controller asks for.
Never for anything else: no advertising, no profiling, no selling or passing data to anyone, no training of artificial intelligence models.
4. What data
- Identity and contact
- Name and surnames, card code, photo if the library uses one, e-mail, language and account to sign in.
- Membership
- Type of reader, group or class, stage or approximate age, tutor and, if the library brings them, the name and e-mail of the adults in a minor reader’s family.
- Use of the library
- Loans, returns, holds, overdues, days without loans and recorded fines, purchase requests, challenges joined, reviews, drawings, recorded voices and their last search.
- Staff
- The account of each member of the team, their role and what they do in the library.
- Technical
- IP address and time in the server logs, and what the app needs to sign in and receive notices.
- Special categories
- Only if the library marks that a reader needs books in other formats (large print, audio, braille), which may say something about their health. The format is noted, never a diagnosis; if the library uses it, it needs one of the grounds of article 9 of the GDPR.
5. Whose
The library’s readers, minors included; their families; the staff of the library and of the institution (teachers, tutors, librarians); and anyone who records a voice with a link the library sends them.
6. What Oksigenia does
- Process the data only on the controller’s instructions (these terms, what it sets on its screens and what it asks for in writing), also for passing them outside the European Union, unless a law obliges Oksigenia to do otherwise; then it says so first, unless that law forbids it. If an instruction goes against data protection law, it says so.
- Make sure that whoever accesses the data at Oksigenia does so only when needed (support asked for or an incident), only to what is necessary and under a duty of confidentiality.
- Apply the security measures in section 12.
- Use other processors only as section 7 says.
- Help the controller deal with people’s rights: the library has the tools to see, correct, export and delete a reader’s data. If someone writes to Oksigenia to exercise them, it passes it on to the controller without delay and tells that person.
- Help the controller with security, breach notifications, the 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 the information that shows it complies, and allow the audits in section 11.
- Keep the record of the processing activities it carries out as processor.
7. Other processors
The controller authorises Oksigenia to use these providers, who commit by contract to the same as this agreement. Oksigenia answers to the controller for what they do with its data, as if it 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 the connections to app.ayvurenda.com, which go through its network.
- Scaleway
- Sends the library’s e-mails (notices and sign-ins), from France.
- Keeps the server’s backups, encrypted before they leave: Google cannot open them.
- Proton
- Receives the e-mail written to Oksigenia, support included, in Switzerland.
- Google and Apple
- Only with the app: they carry the notices to the phone, with a short text that does not say which book it is.
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 with a refund of the part paid that it has not used.
What the library contracts on its own, such as its own Google Drive or storage for its copies, or an artificial intelligence service, is between it and that provider; Oksigenia still processes on its behalf what it sends there and what it keeps to send it (the access code of its Drive, encrypted). If a provider came to process data on Oksigenia’s behalf, it would join this list.
8. Outside the European Union
The data are stored in the European Union. They only leave it, when needed, through Cloudflare and through Google’s and Apple’s phone notices, with the GDPR’s safeguards: 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 learns of a breach affecting the library’s data, it tells the controller without undue delay and within 48 hours at most, with what it knows: what happened, what data and how many people, what it may mean and what is being done. What is missing it tells as soon as it knows. Notifying the authority and the people is up to the controller, and Oksigenia helps.
10. At the end
While the service lasts, the controller can download the full copy of its library whenever it wants, in open formats (MARC 21, Dublin Core, RIS, CSV and a folder ready for Koha), with its files.
At the end, the controller chooses: to take its data and have it deleted, or only to have it deleted. It has 30 days to download whatever it wants. Then Oksigenia deletes its whole library, with all its data and the accounts that have nothing else in the service. The server’s backups, encrypted, are used for nothing else and disappear as they are renewed, within 12 months at most; if one ever had to be restored, that library’s data would be deleted again. If asked, it 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 it complies with this agreement. If it wants an audit, it can carry it out itself or through someone bound by confidentiality, with 30 days’ notice, once a year and at its own cost, without seeing anything of other libraries. If there has been a breach, an authority asks for it or a law requires it, whenever needed. Oksigenia also deals with its data protection officer, at the address above.
12. Security measures
- All connections encrypted (HTTPS).
- Each library kept apart: checked on every page, every request and every file, and automated tests watch it in every version.
- Passwords stored so that nobody can read them; two-factor sign-in for whoever wants it, with a code app or a passkey; signing in with Google or Microsoft without any account being created.
- The connectors’ keys, encrypted in the database.
- A copy of each library every night, which can leave encrypted with a key only the library holds; the server’s copies, encrypted before they leave.
- The record of who did what in each library.
- Only what is needed about each person: loans from more school years than the library keeps (two, by default) stop saying who borrowed them, and what is shown about a group is added up and without names.
- Security updates of the system and of the Moodle the service runs on, kept up to date, and security reviews of the code.
- Development and testing with sample data.
- The service monitored, to know at once if something fails.
13. What the controller does
Have a legal basis to process the data of its readers and staff, and inform them; ask for families’ permission where needed (the library asks for it for minors’ voices); give its instructions in writing; carry out the impact assessment if it applies; and take care of its team’s accounts.
This English version is a translation; if the two differ, the Spanish text prevails.
Last updated: November 2026.