This agreement (the "Agreement") supplements the Conflo Studio terms of use and sale (the "Terms"). It meets Article 28 of Regulation (EU) 2016/679 (the "GDPR").
1. Parties
- The controller: the Customer, as identified when its organization was created or in its order form [TO BE COMPLETED for a signed agreement: company name, address, representative].
- The processor: Jean Carboni, sole proprietor (entrepreneur individuel), SIREN 917 410 979, [TO BE COMPLETED: business address], [TO BE COMPLETED: contact e-mail address for personal data] (the "Publisher").
2. Purpose
The Publisher processes personal data on behalf of the Customer for the sole purpose of providing it with the Conflo Studio service (the "Service"). Annex 1 describes this processing.
What the Publisher processes on its own account (invoicing, sign-up of a new organization, platform security, refused sign-ins of addresses nobody invited) falls under its privacy policy, where it is the controller.
3. The Customer's instructions
The Publisher processes the data only on the Customer's documented instructions. These instructions are: the Terms, this Agreement, and the settings the Customer makes in the Service (members and roles, projects, integrations, agents, support access, presentation links, export, deletion). If an instruction seems to infringe the GDPR, the Publisher informs the Customer.
4. Confidentiality
The Publisher is a sole proprietorship: only Jean Carboni has access to the operation of the Service. Anyone he authorized in the future would be bound to confidentiality [TO BE COMPLETED: written undertaking].
Nobody at the Publisher reads an organization's content unless that organization has opened a support access (lasting 1, 4, 24 or 72 hours, read-only or not, banner visible to all members, each screen read recorded in the Customer's audit log). Outside this access, the Publisher sees only numbers about an organization.
5. Security
The Publisher implements the measures of Annex 2. It may change them without lowering their level.
6. Sub-processors
The Customer authorizes the Publisher to use the sub-processors on the attached list ("List of subprocessors"). The Publisher informs the Customer of any addition or replacement [TO BE CONFIRMED: period, for instance 30 days] in advance, by [TO BE COMPLETED: channel]. The Customer may object on legitimate data-protection grounds; failing agreement, it may terminate without charge. The Publisher imposes equivalent data-protection obligations on each sub-processor and remains liable for it towards the Customer.
The services the Customer connects itself (Discord, Slack or Teams channels, Jira, GitHub, AI agent) are chosen and set by it; what the Service sends them leaves on its decision. [TO BE CONFIRMED: legal qualification of these services — see the questions for the lawyer.]
7. Transfers outside the European Union
The Service's data is hosted in the European Union (Annex 3 and the list of subprocessors). Some sub-processors are established outside the Union (Google for sign-in; Discord, Slack or Microsoft if the Customer connects them); these transfers are governed by [TO BE CONFIRMED: EU-US Data Privacy Framework adequacy decision, standard contractual clauses — to be checked for each].
8. Data subjects' rights
The Service gives the Customer the means to answer data subjects:
- access and portability: JSON export of a project or of the organization by an administrator;
- erasure: the person leaves the organization or deletes their own account; deletion of a project or of the organization. An administrator can close a member's access (their sessions are closed), but the member's record then stays in the organization [TO BE COMPLETED: erasure of a member at the Customer's request, done by the Publisher as long as the tool does not allow it];
- rectification: an administrator changes roles and access; the name and picture come from the person's Google account [TO BE COMPLETED: the name cannot be changed in the Service today; on request to the Publisher].
If a person contacts the Publisher directly, it forwards the request to the Customer [TO BE CONFIRMED: period] and helps it answer.
9. Personal data breaches
The Publisher notifies the Customer of any personal data breach without undue delay and at the latest [TO BE CONFIRMED: period, for instance 48 hours] after becoming aware of it, with what it knows: nature, data and persons concerned, likely consequences, measures taken. It helps the Customer notify the supervisory authority and, where applicable, the data subjects. [TO BE COMPLETED: written incident-handling procedure.]
10. Assistance
The Publisher helps the Customer, as far as it knows, to carry out a data protection impact assessment or to consult the supervisory authority, by providing the description of the processing and of the security measures.
11. End of the Agreement
At the end of the Service, at the Customer's choice:
- return: the Customer exports its data (JSON export of the organization) before deletion;
- deletion: the owner requests the deletion of the organization; it can be cancelled for 30 days, then all its rows are erased from the database. The backups that still contain them expire on their own, at most 14 days later on the server and 30 days later for the off-server copies.
[TO BE COMPLETED: deletion on the Publisher's initiative when the Customer does nothing at the end of a subscription.]
12. Audit and documentation
The Publisher makes available to the Customer the information needed to demonstrate compliance with this Agreement. The Customer may have an audit carried out [TO BE COMPLETED: notice, frequency, costs, auditor bound to secrecy]. The organization's audit log (sign-ins, invitations, roles, tokens, settings, support access, agents' reads and writes) can be read and exported as CSV by its administrators.
13. Record
The Publisher keeps the record of the categories of processing carried out on behalf of its customers (GDPR Article 30(2)) [TO BE COMPLETED: record to be written].
Annex 1 — Description of the processing
Nature and purpose: hosting, display, collaborative editing and backup of the Customer's content; management of its organization's members and their access; internal notifications; the organization's audit log.
Duration: that of the Terms, then the deletion period of section 11.
Data subjects: the organization's members and guests; persons whose data the Customer places in its content; visitors of a presentation link.
Categories of data:
| Data | Retention |
|---|---|
| Account: e-mail address, name and picture address (provided by Google), language, roles, organizations | Until the person leaves the organization or deletes their account, or the organization is deleted; a closed access keeps its record |
| Sessions: token hash, IP address, browser, dates | Expire after 30 days; expired sessions are erased at each new sign-in to the Service |
| Personal tokens: hash, purpose, scope, end date | Until revoked or the account is closed |
| Audit log: who, what, when, IP address, browser | As long as the organization exists [TO BE CONFIRMED: duration]; cannot be altered from the Service |
| Activity log, notifications, mentions | As long as the project exists [TO BE CONFIRMED: duration] |
| Comments and content (screens, sheets, scenarios, back end, kits), with the personal data the Customer places in them | As long as the project exists, including the history of published versions |
| Live presence (who is on a screen, selection, pointer) | Not stored: for the duration of the connection |
| Request-limit and refused sign-in counters (IP address, account) | In memory only, a few minutes |
No special category of data (GDPR Article 9) is required by the Service; the Customer refrains from placing any in its content [TO BE CONFIRMED].
Annex 2 — Security measures
- Encryption in transit: HTTPS only (Let's Encrypt certificates), redirect from HTTP, HSTS.
- Per-organization content encryption: designs, back end, scenarios, revisions, comments and shared states are encrypted (AES-256-GCM) with a key specific to the organization, itself encrypted by a master key that is never in the database (Scaleway key management service planned, or a key kept on the server). A database or a backup alone yields no readable content. Not encrypted this way: account data, logs, kits, call records.
- Integration secrets (webhook addresses, Jira tokens) encrypted separately (AES-256-GCM).
- Isolation: Postgres row-level security, each request sees only its organization; rights checked by the server on every route.
- Authentication: sign-in with Google; sessions by a random token of which only the hash is kept,
HttpOnly,SameSite=Lax,Securecookie; 30 days at most; sessions listed and closable remotely; personal tokens kept as hashes, which can be limited to a project, to reading, to a date. - Abuse protection: 600 requests per minute per address and per account; 15-minute block after 10 refused sign-ins; request body capped at 20 MB; strict content security policy.
- Server: firewall opening only SSH, HTTP and HTTPS, fail2ban, automatic security updates; database reachable from the server only.
- Backups: every night, kept 14 days; encrypted copy (AES-256-GCM) off the server, kept 30 days [planned: active once the external storage is opened]; weekly test restore; alerts to the operator if the test or the copy fails.
- Traceability: per-organization audit log, which cannot be altered from the Service.
- Publisher's access: operations console limited to numbers; access to content only through the support access opened by the Customer.
Annex 3 — Sub-processors
See the "List of subprocessors" document.