European hosting, end to end
The database and the application sit on European infrastructure. Nothing about a patient is sent elsewhere to be processed, and there is no third-party analytics service watching a patient's reply arrive.
Privacy
A clinic's patients are not ours to trade.
This page is not a feature list. It is the whole of what acudda holds about a patient, where it is held, and what it refuses to hold — written plainly, because a clinic hands over its patient list before it hands over a euro.
What is kept
KeptFirst name
KeptSurname
KeptMobile number
KeptThe time of the appointment
KeptThe button they tapped
KeptAnything they wrote back
KeptReception's own notes
NeverDiagnosis, reason for the visit, history
Seven fields, and no eighth. The last row is the one that matters: nothing clinical is ever in the record, because the product has nowhere to put it.
Where it is held
Data protection
Encrypted connections and controlled access
We protect personal data and data obtained from Google Calendar using encrypted HTTPS connections between the browser and acudda, and between acudda and Google APIs. Access to a clinic's data requires signing in, and the server checks which clinic the user belongs to for each operation. The tokens that keep the Google connection active are stored encrypted with AES-256-GCM, using a key held in the server configuration. They are never sent to the browser. Technical logs omit sensitive fields such as passwords, tokens, phone numbers and patient messages.
What leaves the clinic
A first name and an hour
The message template carries the patient's first name, the clinic's name, the date and the time — nothing else. Not the surname, not the treatment, not a word from the file. The patient is asked whether they are coming at a time, never what for.
This page
No cookies, no trackers
This site sets no cookie, loads no analytics and requests nothing from anybody else's server — the typefaces are served from here.
The patient's rights
The clinic answers, we assist
Under the GDPR the clinic is the data controller and acudda is the processor: the patient's relationship is with the clinic, and requests for access, correction or erasure go there. We give the clinic the means to answer them, and we act on the clinic's instructions.
Google Calendar
Appointment synchronisation and confirmation
If the clinic connects its Google Calendar, acudda reads the list of its calendars and, for the ones it picks, the title, time and duration of each event: that is where the name, mobile number and treatment of the appointment come from. Appointments are synchronised in both directions: acudda can create events and update their title, time, duration and selected calendar when the clinic changes an appointment. It also adds “si” or “no” to the title when the patient answers. Cancelling an appointment in acudda keeps the event with “no” in its title; deleting an event in Google cancels the appointment in acudda. It reads nothing else from the account. That data is used only to manage and confirm that clinic's appointments: it is not sold, not shared, not used for advertising or to train models, and nobody at acudda reads it unless the clinic asks us to in order to solve an issue. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The clinic can disconnect the calendar at any time: acudda stops synchronisation, deletes the stored token and requests that Google revoke the permission. Appointments already imported remain in acudda. The clinic can also remove access through its Google Account permissions.
The contract
Data-processing agreement
Every clinic signs a data-processing agreement before a single patient is loaded: what we may do with the data, for how long, who else touches it, and what happens on the day you leave. Ask for it and we send it before the demo, not after.