Data processing agreement (DPA)
Courtesy translation — only the French text is authoritative. Read the French text
Article 1 — Parties and purpose
This agreement is entered into between:
- the client organisation, which uses the BySince platform for its own needs, hereinafter “the controller”;
- [to be completed], [to be completed], whose registered office is at [to be completed], registered under number [to be completed], publisher of the platform, hereinafter “Since & Co” or “the processor”.
It sets out the conditions under which Since & Co processes personal data on behalf of the controller, in accordance with Article 28 of Regulation (EU) 2016/679 (GDPR). It forms an integral part of the contract entered into between the parties and of the terms of use. In matters of data protection, it prevails over any other document.
It does not cover the processing for which Since & Co is itself the controller, described in the privacy policy.
Article 2 — Description of the processing
| Subject matter | Provision of the BySince platform and of the Cartographe mobile application: hosting, making available, maintenance, backup, support. |
|---|---|
| Duration | That of the contract, plus the reversibility period and the time taken for the backups to expire. |
| Nature of the operations | Collection, recording, organisation, storage, consultation, display, conversion, transcription, extraction, export, backup, restoration, erasure. On instruction: transmission to an AI provider. |
| Purposes | Those that the controller pursues with the platform: mapping of activities and skills, training and passing on of know-how, tracking of progress and learning outcomes, skills booklet, reviews, management of versatility, issuing of badges. |
| Data subjects | Users of the organisation and of its attached entities (employees, learners, tutors, trainers, administrators, contributors); persons recorded, photographed, filmed or mentioned in the content; external experts called upon for a review. |
| Data | Identity and account data; login data; learning, assessment and skills data; uploaded content; sound recordings, photographs, videos and transcriptions; consents; support requests. Details are given in the privacy policy. |
| Sensitive data | The platform is not designed to process data falling under Articles 9 and 10 of the GDPR. The controller undertakes not to upload any such data, unless the parties have agreed in writing beforehand on appropriate measures. |
Article 3 — Obligations of the controller
- It determines the purposes and legal bases of the processing, and keeps its record of processing activities.
- It informs the data subjects, including persons recorded in the field, and obtains their consent where it is required.
- It complies with its own obligations, in particular under employment law: information and consultation of employee representatives, prior information of employees about assessment systems.
- It documents its instructions in writing. The configuration of the platform by its administrators constitutes an instruction: creation of accounts, granting of rights, enabling of AI, registration of API keys, enabling of capture encryption, sharing.
- It carries out, where appropriate, the data protection impact assessment.
- It ensures the security of its own access: choice of administrators, removal of the accounts of persons who have left, confidentiality of credentials and keys.
Article 4 — Processing on instruction
Since & Co processes the data only on documented instructions from the controller, including with regard to transfers outside the European Union, unless required to do otherwise by law; in that case it informs the controller, unless the law prohibits it from doing so.
If Since & Co considers that an instruction infringes the GDPR or another data protection rule, it immediately informs the controller.
Since & Co does not use the data for its own purposes. It does not sell the data, does not disclose it to other clients and does not use it to train artificial intelligence models.
Article 5 — Confidentiality
Since & Co ensures that the persons authorised to process the data are bound by an obligation of confidentiality, receive the necessary training and access the data only to the extent necessary for their duties: operations, maintenance, security, support.
Authorised members of Since & Co's staff hold roles that allow them to access the space of any organisation. They access it only for the purposes of the service or at the controller's request.
Article 6 — Security
Since & Co implements the technical and organisational measures described in Annex 1, in order to ensure a level of security appropriate to the risk, in accordance with Article 32 of the GDPR. It may change them, without lowering their overall level.
Article 7 — Sub-processors
- General authorisation. The controller authorises Since & Co to engage the sub-processors listed in Annex 2.
- Changes. Since & Co informs the controller of any addition or replacement at least thirty days in advance, by publishing a new version of this agreement and by a notice sent to the contact designated by the controller. The controller may object in writing, on legitimate grounds relating to data protection, during that period. If no solution is found, it may terminate the service concerned.
- Same obligations. Since & Co imposes on its sub-processors, by contract, obligations equivalent to those of this agreement. It remains liable to the controller for their performance.
Article 8 — Artificial intelligence
The AI features and the data they transmit are described in Articles 11 to 24 of the terms of use. Three situations must be distinguished.
8.1. Call made with an API key of the organisation
The organisation registers a key obtained from an AI provider with which it has itself contracted. The provider then processes the data on the organisation's account and under the organisation's contract. It is not a sub-processor of Since & Co: it is a processor, or a recipient, chosen by the controller. The controller checks the provider's terms: location, transfers, retention periods, use for model training. Registration of the key constitutes an instruction given to Since & Co to transmit the data to that provider when an authorised user triggers the feature.
8.2. Call made with a user's personal key
The platform allows a user to register their own key, which takes precedence over the organisation's key. The data is then processed on that user's personal account with the provider. The administrator sees neither these keys nor the corresponding calls. It is for the controller to authorise, regulate or prohibit this practice through its internal rules. If it wishes to rule it out, it may disable AI for its organisation.
8.3. Processing carried out with Since & Co's resources
At the controller's request, Since & Co may launch, in the course of operations, AI processing on the controller's content: AI review of sheets, knowledge review, glossary, description, keywords, conversion of transcriptions. It then uses its own accounts with the providers, including by means of the “Claude Code” and “Codex” tools, which transmit the data to the provider. These providers are sub-processors of Since & Co and are listed in Annex 2.
Since & Co launches such processing only at the request or with the agreement of the controller, and never for an organisation that has disabled AI.
8.4. Common safeguards
- no call to a third-party provider is made for a user without an available key, without that user's active consent, or if AI is disabled for the organisation;
- local processing (skill suggestion, local transcription) transmits nothing to any third party;
- AI outputs are proposals subject to human validation; no automated individual decision is taken;
- API keys are encrypted, never displayed again, never exported; the usage log contains no request, no response and no key.
Article 9 — Transfers outside the European Union
The data is hosted at the following location: [to be completed]. Since & Co does not transfer data outside the European Union, except:
- to Switzerland, for the remote storage of backups, on the basis of the European Commission's adequacy decision;
- to AI providers, where those features are used on the controller's instruction. In the case of Article 8.3, Since & Co satisfies itself that an appropriate safeguard exists (adequacy decision or standard contractual clauses) and keeps it available to the controller. In the cases of Articles 8.1 and 8.2, the transfer falls under the key holder's contract.
Article 10 — Rights of data subjects
Since & Co assists the controller, by appropriate measures and in so far as possible, in responding to requests from data subjects to exercise their rights. The platform allows the administrator to view and correct the data of its users, and to deactivate or delete their accounts. A structured export (JSON) exists for the data of an attached entity; for any other extraction, Since & Co acts on request.
If a person sends their request directly to Since & Co, Since & Co forwards it without delay to the controller and does not respond to it itself, unless instructed otherwise.
Article 11 — Personal data breach
Since & Co notifies the controller of any personal data breach concerning it as soon as possible, and no later than forty-eight hours after becoming aware of it. The notification describes the nature of the breach, the categories and approximate number of persons and records concerned, its likely consequences, the measures taken or proposed, and the contact point. The information may be provided in phases.
The controller notifies, where appropriate, the supervisory authority and the data subjects. Since & Co assists it in doing so.
Article 12 — Assistance with compliance
Since & Co assists the controller, taking into account the nature of the processing and the information available to it, with carrying out impact assessments, with prior consultation of the supervisory authority and with compliance with its security obligations. The registers of AI features and of processors kept by Since & Co are provided on request.
Article 13 — Fate of the data at the end of the contract
- At the end of the contract, and at the controller's choice, Since & Co returns the controller's data to it in a commonly used format and then deletes it, or deletes it directly.
- API keys are deleted and are never returned or exported.
- Copies held in backups are deleted when the backups expire, at the latest twelve months after deletion. They are not used in the meantime.
- The fate of the public verification pages of badges issued is decided by the controller.
- Since & Co may retain the data that the law requires it to retain, and the data for which it is itself the controller.
- On request, Since & Co certifies the deletion in writing.
Article 14 — Documentation and audit
Since & Co makes available to the controller the information necessary to demonstrate compliance with Article 28 of the GDPR.
The controller may carry out an audit, or have one carried out, no more than once a year save in the event of a data breach or a request from an authority, subject to thirty days' notice, during working hours, without disrupting the service or accessing other clients' data. The auditor must not be a competitor of Since & Co and undertakes to maintain confidentiality. The costs of the audit are borne by the controller, unless a serious breach is found.
Article 15 — Record and contact
Since & Co keeps a record of the categories of processing activities carried out on behalf of its clients. Data protection contact: [to be completed].
Article 16 — Liability, term, governing law
Each party is liable for the damage caused by its breaches of the GDPR and of this agreement, under the conditions of Article 82 of the GDPR and within the limits provided for in the contract, which do not apply to the rights of data subjects.
The agreement applies for the entire duration of the processing of the data by Since & Co. It is governed by French law; disputes fall within the jurisdiction of the courts designated by the terms of use.
Annex 1 — Security measures
| Area | Measures |
|---|---|
| Authentication | No open registration. Hashed passwords; at least 8 characters with an upper-case letter, a lower-case letter, a digit and a special character; change required at first login and then every two months. Two-factor authentication by application (TOTP) or by code received by email, at the user's choice. Login history. |
| Access rights | Role-based rights. Access control on every operation. “Log in as” reserved for administrators. |
| Segregation | Every item of organisation data carries the identifier of its organisation. A filter applied to all queries restricts each user to their current organisation. |
| Encryption | Connections over HTTPS. AI API keys encrypted at rest (AES-256-GCM). Organisations' private keys encrypted at rest (AES-256-GCM). Optionally, captures from the Cartographe application encrypted on the device and in transit (AES-256-GCM, key protected by RSA-OAEP), then decrypted by the server on synchronisation. |
| Traceability | Audit log of sensitive administration actions. AI usage log, with no content. Automatic masking of secrets in technical logs. |
| Protection of forms and sessions | Anti-request-forgery (CSRF) tokens on sensitive actions. Session cookie restricted to the site and, on a secure connection, to HTTPS. Limit on the number of attempts for certain operations. |
| Backups | Daily (7 days), weekly (4 weeks), monthly (12 months). Remote copy transferred over an encrypted connection. Restoration procedure. |
| Badges | Email address published only in the form of a salted hash. Non-guessable public identifiers. Revocation. |
| Development | Automated tests, including tests of isolation between organisations and of non-disclosure of keys. Static code analysis. Review of changes. |
| End of contract | Procedure for deleting an organisation with prior export; exclusion of secrets from any export. |
Annex 2 — Sub-processors
| Sub-processor | Service | Data | Location and safeguards |
|---|---|---|---|
| [to be completed] — [to be completed] | Hosting of the platform. | All data. | [to be completed] |
| Infomaniak Network SA | Remote storage of backups. | Copy of the database and of the uploaded files. | Switzerland — adequacy decision. |
AI sub-processors
These providers act as sub-processors of Since & Co only in the case of Article 8.3, that is to say for processing launched by Since & Co with its own accounts, at the controller's request.
| Provider | Processing | Data transmitted | Location, transfers, retention, training |
|---|---|---|---|
| Anthropic (API and Claude Code tool) | AI review of sheets, knowledge review, glossary, description and business instruction, keywords, conversion of transcriptions into sheets. | Content of the activity sheets; text of the transcriptions; name, description, themes and activities of the organisation. | In accordance with Anthropic's commercial terms applicable to Since & Co's account, provided on request. |
| OpenAI (API and Codex tool) | Same drafting processing, at the operator's choice; audio transcription where local transcription is not available. | Content of the sheets; audio files of the sessions. | In accordance with OpenAI's terms applicable to Since & Co's account, provided on request. |
| Google (Gemini API) | Same drafting processing, at the operator's choice; keywords. | Content of the sheets; names of the activities. | In accordance with Google's terms applicable to Since & Co's account, provided on request. |
| Stability AI | Image generation. | Text description entered. | In accordance with Stability AI's terms applicable to Since & Co's account, provided on request. |
The following are not sub-processors, since they do not receive personal data entrusted by the controller: Hugging Face (downloading of models run locally), the image libraries, MyMemory, DiceBear, Lorem Picsum and the public “Recherche d'entreprises” API. They are described in the privacy policy.
Publisher's contact details: see the legal notice.