Data Processing Agreement (DPA)
Pursuant to Art. 28 GDPR
Note: DPA document not yet finalized. This page provides information about the legal obligation to conclude a DPA. The full DPA document will be provided before go-live. For questions, please contact transl.delta@gmail.com.
This is a non-binding convenience translation. The German version is the legally authoritative version.
Why is a DPA required?
When your practice enters patient data (e.g. names, phone numbers) into ClinicSlotHub, ClinicSlotHub processes that data on your behalf. In this case, your practice is the data controller (Art. 4(7) GDPR) and ClinicSlotHub is the data processor (Art. 4(8) GDPR).
Pursuant to Art. 28(3) GDPR, a written Data Processing Agreement (DPA) is legally required. Patient data must not be entered without a signed DPA in place.
When do I need a DPA?
- In trial mode: No DPA required for internal tests without real patient data. Please do not enter real patient data until a DPA is in place.
- In production: A DPA must be signed before entering any real patient data.
What does the DPA regulate?
- Subject matter and duration of processing
- Nature and purpose of the processing
- Type of personal data and categories of data subjects
- Obligations and rights of the controller (practice)
- Binding instructions to the processor (ClinicSlotHub)
- Technical and organisational measures (TOMs)
- Sub-processing arrangements (e.g. Supabase, Vercel)
- Data deletion or return upon contract termination
Request a DPA
The DPA document will be provided as a PDF or electronically signable document before go-live.
Contact: transl.delta@gmail.com
Sub-processors
- Supabase Inc. — Database hosting & authentication (USA; SCCs)
- Vercel Inc. — Web hosting (USA; SCCs in place)
- Twilio Inc. (optional) — SMS/WhatsApp delivery, only when explicitly configured by the practice