Data processing agreement (GDPR article 28)
Version of 12 November 2026. This agreement supplements the API terms of use. It applies as soon as the Partner uses production keys; in the sandbox, only dummy data is allowed.
Controller: D.DESIGN & CONSEIL (Kelki), French simplified joint-stock company (SAS), registered office 4 rue de Bellefond, 75009 Paris, RCS Paris 794 023 564, SIRET 794 023 564 00022, intra-EU VAT number FR91 794 023 564. Personal data contact: contact@kelki.ai.
Processor: the Partner holding the developer account (name, registered office, registration and representative provided when real access is opened).
1. Roles of the parties and reasons
Kelki is the controller of the Requests: it alone decides their purpose (putting the Person in touch with one or more Professionals of the trade in their area, who call them back) and its essential means: closed list of data, Consent Text, e-mail confirmation, recipients, retention periods, security (GDPR article 4.7).
For collecting and sending Requests through the API, the Partner is Kelki's processor (GDPR articles 4.8 and 28). Reasons:
- Kelki's purpose, not the Partner's. The sole purpose of the operation is the matching organised by Kelki. The Partner pursues no purpose of its own with this data: it does not receive it back (masked contact details, statuses only), does not sell it, is not paid for it (the API is free and without revenue sharing) and refrains from reusing it.
- Essential means set by Kelki. The categories of data (closed schema, other fields refused), the Consent Text displayed word for word, the e-mail confirmation of every real Request, the Professionals receiving it and the retention periods are imposed by Kelki. The Partner only chooses non-essential means: the look of its screens, its programming language, its hosting (European Data Protection Board guidelines 07/2020 on the concepts of controller and processor, version 2.0 of 7 July 2021).
- Documented instructions. These rules are written down (terms, this agreement, API documentation) and technically enforced by the API, which matches the “documented instructions” of article 28.3.a.
- Consent is given to Kelki. The Person ticks Kelki's Consent Text, then confirms their Request themselves by clicking in the e-mail Kelki sends them. The Partner only relays: it collects no consent on its own behalf.
What the Partner does on its own behalf (its users' accounts, bookings, commercial relationship, invoicing) is its sole responsibility, outside this agreement, with its own legal basis and its own information of individuals.
Limit of this qualification. Should the Partner decide to process Request data for its own purposes (prospecting, profiling, resale, named statistics), it would become controller of that processing (GDPR article 28.10), or even joint controller with Kelki for the collection (article 26; Court of Justice of the European Union, 29 July 2019, Fashion ID, C-40/17). This agreement forbids it. So that individuals remain protected even in that case, Kelki remains their single point of contact for exercising their rights (article 7 below), and the notice of annex 1 names Kelki.
2. Description of the processing (article 28.3)
| Subject | Collecting, in the Partner's service, the Request of a Person who wants to be called back, showing them Kelki's summary and Consent Text, then sending the Request to Kelki through the API; then tracking its status. |
|---|---|
| Nature of operations | Entry, display, transmission through the API, brief technical storage, deletion. |
| Purpose | Putting the Person in touch with one or more Professionals of the trade in their area, organised by Kelki. |
| Data subjects | The Partner's users who ask to be called back (individuals or professionals). |
| Data | Name, phone, e-mail address, town and postcode, trade, service or need described in a few words, timing, optional free details; the Partner's technical reference without personal data. No sensitive data (GDPR article 9): no health, no opinions, no national identification number. |
| Duration | That of the API terms of use. |
| Legal basis (Kelki's side) | The Person's consent (article 6.1.a), given with the Consent Text then confirmed by e-mail. |
3. Instructions
- The Partner processes the data only to send the Request and track its status, according to the API terms, this agreement and the documentation. It only sends a Request if the Person wanted it and ticked the Consent Text, displayed word for word, box unticked by default.
- It asks no question about health or any other sensitive data and misuses no excluded trade.
- If an instruction seems to it contrary to the GDPR or French law, it informs Kelki immediately (article 28.3, last paragraph).
- It does not use the data on its own behalf and discloses it to no one other than Kelki, except under a legal obligation of which it informs Kelki beforehand where the law allows (article 28.3.a).
4. Confidentiality
Only the Partner's staff who need it access the data; they are bound to confidentiality by contract or by law (article 28.3.b).
5. Security (article 32)
The Partner implements at least the measures of annex 2, adapted to the risk. It keeps the list up to date and provides it to Kelki on request.
6. Sub-processors (articles 28.2 and 28.4)
- Kelki gives general authorisation for the necessary technical providers (hosting, managed services). The Partner keeps their list, informs Kelki of any addition or replacement at least 15 days in advance, and Kelki may object on legitimate grounds.
- The Partner imposes on each of them, by contract, the same obligations as those of this agreement, and remains liable to Kelki for their compliance.
- No transfer outside the European Union or the European Economic Area without Kelki's prior written consent and a safeguard under GDPR articles 44 to 49 (adequacy decision or standard contractual clauses).
7. Data subjects' rights (article 28.3.e)
Kelki answers requests for access, rectification, erasure, restriction, objection, portability and withdrawal of consent concerning Requests. The Partner forwards to Kelki, without delay and no later than 5 working days, any such request it receives, without answering it on the merits itself, and helps Kelki answer it.
8. Data breaches (articles 33 and 34)
- The Partner notifies Kelki of any personal data breach affecting Requests (leak, loss, unauthorised access, exposed key) no later than 24 hours after becoming aware of it, at contact@kelki.ai.
- The notification describes, as far as possible: the nature of the breach, the categories and approximate number of persons and Requests affected, the likely consequences, the measures taken or proposed, and a contact.
- Kelki decides on the notification to the CNIL (within 72 hours, article 33) and on informing individuals (article 34). The Partner does not communicate about the breach without consulting Kelki, except under a legal obligation.
9. Assistance
The Partner helps Kelki, taking into account the information available to it, to meet its obligations on security, notification, impact assessment and prior consultation (articles 32 to 36, article 28.3.f). It keeps the record of processing activities it carries out on Kelki's behalf (article 30.2).
10. Retention and end of processing (article 28.3.g)
- The Partner does not keep Request data beyond what is needed to send it and track its status. It may keep the Request identifier, its reference and its statuses, which contain no personal data.
- Its technical logs do not contain request bodies; if they contain personal data by mistake, they are erased within 30 days.
- At the end of the contract, it deletes all data processed on Kelki's behalf (including copies, except where the law requires retention) and confirms it in writing within 30 days.
11. Documentation and audit (article 28.3.h)
The Partner makes available to Kelki the information needed to demonstrate compliance with this agreement (screenshots of the Request flow, security measures, list of sub-processors). Kelki may have an audit carried out, by itself or by an auditor bound to secrecy, with 30 days' notice, at most once a year except in the event of a breach or established failure. Each party bears its own costs.
12. Liability
Each party is liable for its breaches of the GDPR under the conditions of article 82. A Partner acting outside or contrary to Kelki's lawful instructions is solely liable (article 82.2).
Annex 1 — Notice to display to the Person
To be displayed next to the send button, with the link to Kelki's privacy policy, in addition to the Consent Text (which stays unchanged, box unticked). In French, as displayed to French-speaking Persons:
(Meaning: “Your request is sent to Kelki (D.DESIGN & CONSEIL), which writes to you to confirm it. After you click ‘Confirm my request’, Kelki passes it on to one or more professionals of the trade in your area, who may call you back. Without confirmation within 48 hours, it is erased. Your rights: contact@kelki.ai. Details: Kelki's privacy policy.”)
Consent Text in force (version v2026-10-18), to be taken word for word from the API:
Annex 2 — Minimum security measures of the Partner
- API calls from its servers only, over HTTPS; production keys stored in a secrets vault or a protected environment variable, never in source code, a mobile app or a browser.
- Access restricted to authorised staff, named accounts, two-factor authentication on administration tools.
- No personal data in addresses (URLs) or in logs; no copy of Requests in analytics or support tools that are not needed.
- Webhook signature checked and messages older than 5 minutes refused.
- Security updates applied, protected backups, key rotation and incident handling procedures known to the team.
Reference texts
- Regulation (EU) 2016/679 (GDPR), articles 4, 6, 9, 26, 28, 30, 32 to 36, 44 to 49 and 82; French Law no. 78-17 of 6 January 1978 as amended.
- European Data Protection Board, guidelines 07/2020 on the concepts of controller and processor (version 2.0, 7 July 2021).
- CJEU, 29 July 2019, Fashion ID, C-40/17; CJEU, 5 June 2018, Wirtschaftsakademie Schleswig-Holstein, C-210/16.
- CNIL, processor's guide and “Sous-traitance : exemple de clauses”; CNIL, technical recommendation on data sharing through APIs (2023).