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
What leaves the building
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 only thing it stores in your browser is which of the two languages you picked.
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.
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.