Client data & privacy
Health data (GDPR Art. 9) is doubly protected.
What counts as client data
Records, fields, measurements, messages and files of clients. They sit exclusively behind the scopes clients:read and clients:write.
Release
In addition to the scope, claritos operations must release the organization for client data — a data processing agreement is the prerequisite. Without release the API answers 403 clients-data-not-enabled.
Logging
Every access to client data is logged (who, when, which endpoint). Payloads are never logged.
Endpoints
Records (/clients), fields (/clients/{id}/fields), value history (/clients/{id}/measurements), conversation (/clients/{id}/messages) and files (/clients/{id}/files, metadata only). File contents and findings deliberately do not go through the public API. Every call is logged per record — the organization can tell at any time which integration read or changed which record and when.
Webhooks
Client events (clients.record.created, clients.record.updated, clients.message.received) contain references only: record ID, record number, status, changed field IDs, message ID. Never values, texts or files — the receiver fetches details via the API if needed, where enablement, scope and logging apply.