Security and data
The person stays in control, the partner only receives statuses and masked contact details, and the data the API keeps is encrypted field by field.
Roles
- Kelki (D.DESIGN & CONSEIL) is the controller of the requests: recording, confirmation, transmission to a professional, tracking.
- The partner acts on Kelki's behalf, as a processor within the meaning of GDPR article 28, to collect and send requests; it remains solely responsible for its own processing (accounts, bookings…). See the data processing agreement.
- The professional who takes the request becomes an independent controller for the call-back and the service.
Minimisation
- Closed schema: only the necessary fields are accepted; no precise postal address;
referenceandend_user_refwithout personal data. - The need sent to
POST /trade-matchesis neither stored nor logged; the agent's free text is not stored. - No health data: health trades are not open to the API, and the free message must contain nothing medical.
What you receive, and never
In return: statuses, dates, the trade, the service, the timing, the place, your reference, and masked contact details (C•••, +33 6 •• •• •• 42, c•••@example.com). Never: contact details in clear, the professional's identity or contact details, where a request came from, an internal identifier.
Retention periods
| Data | Period |
|---|---|
| Draft (including contact details) | 2 hours, then erased |
| Unconfirmed request | 48 hours, then contact details erased |
| Transmitted request | 12 months from sending (privacy policy) |
| Conversation with the agent | 2 hours after the last message |
| Call log (without content) | 90 days |
| Idempotency keys and their response | 24 hours |
| Completed webhook deliveries | 30 days |
Encryption
- In transit: HTTPS (TLS); webhooks over HTTPS only, certificate verified.
- Secrets: keys and secrets never stored in clear (HMAC-SHA256 fingerprint with salt and a pepper kept outside the database); shown only once.
- Fields: each piece of personal data kept by the API (name, phone, e-mail, town, message, place of requests, copies of responses) is encrypted with AES-256-GCM, with a random nonce per value and associated data bound to the table, column and row: a value copied elsewhere cannot be decrypted. Duplicates are looked up through an HMAC-SHA256 fingerprint computed with a separate subkey, without decrypting anything. Subkeys are derived with HKDF-SHA256 from a 256-bit master key kept in a separate file (restricted access), never in the database nor in its backups.
Isolation and logs
- Every record carries the account and the mode; every request is filtered by account; another account's resource answers
404. Test and production are separate. - The call log keeps the date, request identifier, route template, code, duration and a fingerprint of the IP address: never a body, a parameter or contact details.
- The API service is isolated from the website and the connector: an outage of one does not affect the others.
Incidents
- Kelki notifies a personal data breach to the CNIL within 72 hours when it presents a risk (GDPR article 33), and informs the partners concerned.
- The partner reports to Kelki any key leak, compromise or doubt about requests sent within 24 hours of becoming aware of it, at contact@kelki.ai.
- A vulnerability found in good faith is reported to the same address, without exploiting or publishing it before it is fixed. Security testing of the API requires Kelki's written consent.