This annex supplements the Data Processing Agreement (DPA) for customers who use relyd Cloud. 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. The processor for relyd Cloud worldwide is relyd Limited.
1. Subject matter and nature of the processing
relyd runs the Customer's Projects on relyd Cloud. In doing so, relyd processes the Customer's personal data in order to:
- store, run and deliver the Customer's websites, applications and databases;
- build, check and release new versions and keep earlier versions and the code of the last five versions of an app;
- keep access logs of the Projects and derive figures from them for the Customer's statistics and live traffic;
- monitor the availability and load of the Projects and restart applications that hang;
- store this data, back it up daily and restore it from a backup on request.
2. Categories of data subjects
Determined by the Customer, in particular users, visitors, customers, employees and other persons whose data the Customer processes in its Projects.
3. Categories of personal data
All data that the Customer places in Projects, databases, files and environment variables, as well as access logs of the Projects (IP address, time, request, response code, browser). The Customer determines whether special categories of personal data are included; in that case the Sensitive Data Terms apply.
4. Location
Project data is stored and processed in data centres in the European Union. The subprocessors used are listed in the list of subprocessors.
5. Instructions
In addition to the DPA, the Customer's instructions are the actions it triggers through the dashboard, Git, the API or a program it has connected. Connected programs, for example AI assistants, are engaged by the Customer and are not subprocessors of relyd (section 5.6 of the DPA).
6. Technical and organisational measures for relyd Cloud
Separation per Project
- separate container with its own kernel in a sandbox (gVisor), without privileges, file system read-only except for temporary files;
- separate user and separate user namespace on the server;
- separate network per Project, with no route to other Projects, to the server or to internal services;
- separate database instance with its own storage and a random password, reachable only within the Project;
- limits on memory, computing time and processes per Project, without swapping onto other Projects.
Access and access control
- dashboard only with a personal account, password and second factor; Git only with revocable tokens per device;
- every request checks team and Project; tokens of connected programs see only the Projects of their team with the permissions granted;
- staff access customer data only for a specific reason; every access in the admin area is logged.
Encryption and secrets
- transmission only over HTTPS (TLS);
- environment variables and secrets stored encrypted, never in logs and never returned to connected programs; passwords only as a hash.
Integrity and traceability
- log of every action through the dashboard, Git, the API and connected programs, visible to the Customer per Project;
- every version of an application is kept for rollback.
Availability and protection
- availability check of every application every 2 minutes, automatic restart of applications that hang;
- limits on requests per visitor and Project, protection against scanners and load peaks;
- outgoing mail port 25 blocked, detection of sustained load and of imitated login pages.
Backups
- daily backup of the databases and files of every Project, retention 7 days;
- encrypted with a separate key per Project, stored in the European Union and mirrored to a second region of the European Union;
- protection against deletion during the retention period: the servers can create backups but can neither delete nor overwrite them;
- regular tests of whether backups can be restored.
7. Return and deletion
The Customer can export its data itself during the term and up to 30 days after the end. relyd then deletes the data in the Projects. Backups are deleted when their retention period of 7 days expires; because of the protection against deletion, earlier deletion is technically not possible.