This annex supplements the Data Processing Agreement (DPA) for Customers that use relyd Learning Studios, relyd's platform for online courses, courses on site and online live courses (in the Customer's administration it may appear as "relyd LMS"). It supplements Annex 1 (description of the processing) and Annex 2 (technical and organisational measures) of the DPA. For everything not set out here, the DPA applies.
1. Subject matter and nature of the processing
relyd operates relyd Learning Studios for the Customer. In doing so, relyd processes personal data of the Customer to:
provide accounts for learners, trainers, office staff and administrators, including sign-in in two steps;
deliver lessons, videos, practice questions and tests, record learning progress and learning time and issue certificates;
manage courses on site and online live courses, registrations, attendance confirmations, orders and invoices;
give companies their own access with invitations, seats, assigned trainings with deadlines and progress reports;
on instruction of a trainer, send a brief and selected documents to the AI provider to draft lessons or trainings;
where the Customer connects its Google Workspace account, create, change and delete the calendar events of online live courses with a Meet room and add confirmed participants and the course leader as guests;
store and back up this data.
2. Categories of data subjects
learners and their contact persons for billing;
trainers, course leaders, office staff and administrators of the Customer;
employees of companies to which the Customer gives access, and their company administrators;
persons whose data the Customer enters into lessons, materials or briefs.
3. Types of personal data
Accounts: name, e-mail address, password hash, encrypted secret for sign-in in two steps, role, company and company role;
billing and registrations: address, billing details, phone number (optional), course registrations and their status, orders, invoices, payment status;
learning: completed lessons, learning time, answers to practice questions and tests, results, certificates with verification code, ratings;
company access: invitations, seats, assignments with deadlines, progress;
content: lessons, files and materials uploaded by the Customer, AI drafts;
Google connection: e-mail address of the connected account, encrypted access tokens, event identifiers, Meet links and the guest e-mail addresses sent to Google;
usage data: AI usage per company;
technical logs: time, address called and status of requests.
Special categories of personal data may be processed only within the limits of the Sensitive Data Terms.
4. Artificial intelligence
4.1 When a trainer asks for a lesson proposal or a training draft, relyd transmits to the AI provider listed as a subprocessor only the brief written by the trainer and the documents the trainer has selected. Data of learners is not transmitted.
4.2 Under its contract with relyd, the AI provider may not use this content to train its models.
4.3 Drafts are proposals. They become visible to learners only after a person of the Customer has published them. The Customer can limit AI usage per company with a monthly quota.
5. Google Calendar and Google Meet
5.1 The Customer connects its own Google Workspace account. Google Workspace is a service of the Customer and is not a relyd subprocessor; Google processes the data under its own contract with the Customer.
5.2 relyd Learning Studios uses only the permissions openid, email and calendar.events. It creates, changes and deletes only the events of the courses it manages and reads no other calendar entries.
5.3 relyd's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. relyd does not use this information for advertising, does not pass it on and does not use it to train AI models.
6. Location of the data
Operation and backups: on servers of OVH SAS in the European Union (France).
AI provider: as listed in the subprocessor list; transfers outside the EU, the EEA, the UK and Switzerland follow Annex 3 of the DPA.
Services of the Customer: the location of Google Workspace and of the mail service of the Customer follows the Customer's contracts with these providers.
7. Technical and organisational measures
In addition to Annex 2 of the DPA:
Separation: each Customer has its own database. Within a Customer, companies see only their own employees, trainings and files; a company's own trainings are not visible to anyone outside that company.
Access: roles limit what a person sees and may change; administration requires sign-in in two steps.
Files: lesson files are delivered only through signed links that expire; only files in a folder marked public are reachable without them.
Secrets: passwords are stored as one-way hashes; secrets for sign-in in two steps and Google access tokens are stored encrypted.
Transport: connections are encrypted (TLS).
8. Retention and deletion
Data | Retention |
|---|---|
Accounts, learning data, courses, registrations, content | during the subscription; learners can delete their account themselves, other data is deleted by the Customer or on request to privacy@relyd.co |
Invoices and orders | as long as the Customer has to keep them by law |
After the end of the subscription | deleted from the active systems thirty (30) days later (DPA) |
Backups | encrypted, at the latest twelve (12) months after the end of the subscription (DPA) |
Technical logs | as long as needed for operation and security, at the latest thirty (30) days |
Google calendar events | deleted from the connected calendar when a course is cancelled or deleted; the Customer can remove the connection at any time |
9. Subprocessors
For relyd Learning Studios, relyd uses the following subprocessors from the subprocessor list:
OVH SAS: servers and backups;
Anthropic Ireland, Limited / Anthropic, PBC: AI model for lesson proposals, training drafts and the learning companion, which answers participants' questions about their training.
Eleven Labs Incl.: Speech output of the learning companion when participants have an answer read aloud; only the answer text is transmitted.
Services that the Customer connects or uses itself, such as Google Workspace or its own mail service, are not relyd subprocessors.