Skip to Content

Personal data processing agreement (GDPR, article 28)

Between the Practitioner (controller) and Roots Unity SASU, RCS Valenciennes 106 128 903, 45 rue Léon Bathiat, 59600 Maubeuge, contact contact@roots-unity.com (processor).

1. Purpose and duration

The processor hosts and operates the “Systemic board” service on behalf of the Practitioner. The agreement lasts as long as the Practitioner has an account, and until the data is returned or deleted (article 9).

2. Nature, purpose and data processed

  • Purpose : to enable the Practitioner to run remote systemic constellation sessions and keep a record of them (board, notes, client file).
  • Operations : hosting, storage, real-time transmission between participants, export, deletion.
  • Categories of data subjects : the Practitioner’s clients.
  • Data : client pseudonym, figurine names and layouts, custom images uploaded by the Practitioner (which may depict people or objects), session notes and client file entered by the Practitioner, the client’s answers to the reflection sheet (free text entered by the client from their space, after consent, read only by the Practitioner), dates of consent and acknowledgement of reading, requests to exercise rights. This content may reveal health data or data relating to family life (art. 9 GDPR) depending on what the Practitioner and their client enter. No video or audio is recorded or stored; the audio/video stream passes directly between participants (or through a relay that is end-to-end encrypted by the protocol, without recording).

3. Instructions

The processor processes the data only on documented instruction from the Practitioner, evidenced by use of the service and by this agreement. It informs the Practitioner if it considers that an instruction infringes the GDPR.

4. Confidentiality

The persons authorised to process the data undertake to keep it confidential. Administration of the service does not give access to the content of Practitioners’ constellations; exceptional technical access (maintenance, incident) takes place only on request or with the Practitioner’s prior agreement, is limited to what is strictly necessary and is logged.

5. Security (article 32)

Measures in place at the date of the agreement:

  • encryption of exchanges (HTTPS/TLS, secure WebSocket);
  • Practitioner’s notes and client’s answers to the reflection sheet encrypted at rest (AES-256-GCM); two-factor authentication secrets encrypted;
  • passwords hashed (scrypt); two-factor authentication (TOTP) available; protection against replay and limiting of attempts;
  • strict separation between accounts (each request is filtered by the session’s account), tested automatically;
  • session and client space links of limited duration, revocable, session tokens stored in hashed form; client space link kept in hashed form and in encrypted form (server key) so that it can be shown again to the Practitioner, encrypted copy deleted on revocation;
  • no third-party scripts, no trackers; security headers (CSP, HSTS, etc.);
  • event log with no content or IP address, kept for 12 months;
  • isolated container, privileges removed, administration access limited to a private network (VPN);
  • backups: daily copy of the service database, encrypted (AES-256) with a separate key, kept for 14 days on the server; in addition, the server itself is backed up by the host OVHcloud (server backup option, outside the server);
  • custom images: redrawn by the browser (metadata removed), re-checked by the server, stored in the database, accessible only to the owning Practitioner and the participants of their sessions, deleted with the account.

6. Sub-processors

The Practitioner authorises the following sub-processors, located in the European Union:

Sub-processorRoleData concerned
OVH SAS (France)server hostingall the service’s data
Brevo (France)sending account e-mails (confirmation, reset, reminders)Practitioner’s e-mail address only
Self-hosted Odoo on OVH (France)invoicing and subscriptionPractitioner’s identity and e-mail, invoices (no client data)
Stripesubscription paymentPractitioner’s payment data (never client data)

The processor informs the Practitioner of any change, to which they may object within 30 days.

7. Rights of data subjects

The service allows the client to send their requests (access, rectification, erasure) from their space; they are passed to the Practitioner, who responds to them. The processor provides technical help: export of a client’s data, deletion of a client and their sessions.

8. Personal data breach

The processor notifies the Practitioner of any personal data breach without undue delay and at the latest 48 hours after becoming aware of it, with the information useful for notifying the CNIL (72 hours) and, where applicable, the data subjects.

9. Fate of the data

At the end of the agreement, the Practitioner may export their data for 30 days; it is then deleted. Constellations are also deleted automatically 12 months after their last modification. The service’s backup copies are purged at the end of their retention period, that is, at the latest 14 days after the data is deleted; the host’s server backup follows the retention period specific to that option.

10. Audit and documentation

The processor makes available the information necessary to demonstrate compliance with its obligations and allows reasonable audits, at the requester’s expense and with 30 days’ notice.

11. Location

The data is hosted in France. The processor makes no transfer outside the European Union, with the possible exception of payment (Stripe) under the conditions of its documentation.

12. Liability and governing law

The liability provisions of the general terms of sale apply. French law, courts of Valenciennes.