How to evaluate GDPR-friendly scheduling software
If you are comparing online booking systems for your organization, review what data each one collects, where each part is processed, which services receive it, and how you can control retention. A vendor’s features or EU hosting can support your assessment, but they don’t make your use GDPR compliant on their own.
No scheduling tool makes you GDPR-compliant on its own: you still choose the lawful basis, the form fields and the retention period. Before you pick one, check the vendor’s DPA, sub-processors, hosting region, transfers, retention and erasure. Kalendarius hosts booking data on Hetzner servers in Germany and is run by Ugur Akcelik in Turin, Italy; start free on the Personale plan to test it against the checklist below.
Start with the booking data and the purpose
List the fields the booking form collects, including optional questions, service names, meeting titles, email reminders and calendar events. Ask whether each field is needed to arrange the appointment and whether free-text answers could invite people to share sensitive information.
Say a physiotherapy practice asks for name, email, phone, date of birth and “Describe your symptoms”. Name and email are needed for the confirmation and reminders, and the phone number lets the practice call if a therapist is ill. Date of birth goes into the patient file, which is opened at the first visit anyway, so it can wait until then. The symptoms field is the one to drop: it pulls health details into emails and calendars that don’t need them, and the therapist asks at the appointment. The practice also renames “Back pain treatment” to “First appointment, 45 minutes”.
Decide which organization determines the booking purpose and what role the software provider plays for that data. The provider contract should describe the processing and allocate responsibilities; review the current DPA rather than relying on a ‘GDPR compliant’ badge.
Map hosting, subprocessors and calendar integrations
Ask where the provider hosts the core application and database, and where subprocessors handle email, support, analytics, backups or other operations. Then check what changes when you connect Google Calendar or Microsoft 365: calendar events and availability involve those providers under their own terms.
Review the provider’s subprocessor list and the data each enabled integration receives. EU hosting tells you where the core data sits; the integrations tell you where else it goes.
Check the DPA, security measures and deletion process
For processing carried out on your behalf, review the DPA’s scope, instructions, confidentiality, security measures, subprocessors, breach process, assistance with requests, and return or deletion terms. Confirm that the safeguards match your booking workflow and the information involved.
If appointments might reveal health or other special-category information, decide whether that information is needed at booking at all and how it will be protected across email and calendar notifications. Establishing the legal conditions for that processing is the controller’s job.
Set a retention period you can actually apply
Choose how long appointment records are needed for the stated purpose, document the decision, and check whether the product can apply that period to completed bookings. Also find out how you can locate, export or delete one person’s records when they ask, and what the contract says when service ends.
In Kalendarius, completed appointments are deleted automatically after the period you set: up to 90 days on Personale and Professionista, 180 on Team and 365 on Business and Enterprise. If a guest asks to be erased, email info@kalendarius.com and we anonymise their bookings by email address: name, email address, notes and consent time are removed. The rest of the record (time, status, answers to custom questions, cancellation reason) is deleted at the end of your retention period. Events already written to a connected calendar stay there. We can also send you an export of a guest’s bookings. The application and database run on Hetzner servers in Germany, public booking pages load no advertising or analytics trackers, and Google or Microsoft calendar connections are optional. A Data Processing Agreement (DPA) for the Business and Enterprise plans is in legal review; contact info@kalendarius.com. Review the Calendly-specific DPA and data-location guide when comparing those data flows.
Vendor checklist
Ask every vendor on your shortlist for these ten things, in writing:
1. DPA: a data processing agreement that covers the points in Article 28(3) GDPR, including instructions, confidentiality, security, sub-processors, help with requests, deletion or return at the end, and audits.
2. Sub-processor list: every company that receives booking data, its role and its location, and how you are told about changes.
3. Hosting region: where the application, the database and the backups run, named by provider and country.
4. International transfers: for each recipient outside the EEA, the adequacy decision or Article 46 safeguard it relies on, such as Standard Contractual Clauses.
5. Retention: whether you can set how long completed bookings are kept, and whether deletion then happens automatically.
6. Erasure: how you find and erase one person’s bookings when they ask, what that removes, and what stays behind, such as events already written into connected calendars.
7. Audit log: whether changes to users, settings and bookings are logged, who can read the log, and on which plan.
8. Trackers on booking pages: which third-party scripts load on the public booking page and why. Guests see that page before they have agreed to anything.
9. Calendar permission scopes: what the Google, Microsoft or Zoho connection may read and write, whether details of your other events are stored, and how to disconnect.
10. Breach notification: how and how fast the vendor tells you about a personal data breach. Article 33(2) GDPR requires a processor to notify the controller without undue delay.
Write the answers into your records of processing activities under Article 30, so the next review starts from what you already checked.
Sources
The legal points on this page come from the GDPR on EUR-Lex: Article 28 (processors), Article 30 (records of processing activities) and Articles 44 to 46 (transfers to third countries). For transfers, see the EDPB Recommendations 01/2020 on supplementary measures and the Court of Justice’s Schrems II judgment, case C-311/18, which in July 2020 invalidated the EU-US Privacy Shield and kept Standard Contractual Clauses, subject to stricter checks. Kalendarius’s own sub-processors are listed in our privacy policy. Sources checked October 2026.
Frequently asked questions
What makes scheduling software GDPR-compliant?
Software isn’t compliant or non-compliant on its own; the way you use it is. A tool can make compliance easier with an Article 28 processor contract, a clear sub-processor list, known hosting and transfer safeguards, retention you can configure, a way to erase one person’s data, and booking pages without advertising trackers. The lawful basis, the form fields and your privacy notice stay your decisions.
Which scheduling tools store data in the EU?
Some vendors host in the EU, some offer EU data residency on certain plans, and others store data in the US. Check the sub-processor list and the DPA rather than the marketing page, because email, error monitoring or support tools can sit elsewhere. Kalendarius runs its application and database on Hetzner servers in Nuremberg and Falkenstein, Germany.
Do I need a DPA with my booking tool?
Usually, yes. When a vendor processes booking data on your behalf, it is your processor, and Article 28 GDPR requires a contract or other legal act with the content listed in Article 28(3). Many vendors publish a standard DPA for this. For Kalendarius, a Data Processing Agreement (DPA) for the Business and Enterprise plans is in legal review; contact info@kalendarius.com.
Does EU hosting remove all international transfers?
No. Hosting decides where the main database sits, not where every copy goes. At Kalendarius, Sentry stores error reports in its EU region, but it is a US company, so access from outside the EU can’t be ruled out. If you connect Google or Microsoft calendars, those providers process the events under their own terms, which can involve transfers outside the EU. Check each sub-processor and integration, not only the host.
How long can I keep booking data?
The GDPR sets no fixed number of days. Article 5(1)(e) says personal data should be kept no longer than the purpose needs, so choose a period that matches why you keep booking records and write it down. In Kalendarius you can pick 30 or 90 days on every plan, 180 days on Team and 365 days on Business and Enterprise, counted from the end of the appointment.
Related guides
A Calendly alternative hosted in Germany. Team costs €9.90 per organizer a month, and interviewers who only connect a calendar don't pay.
Is Calendly GDPR compliant? Calendly stores user and invitee data in US data centres. What its DPA says about transfers, and what EU teams should check.
Collective and round-robin booking links for up to 25 organizers at €9.90 each a month. Colleagues who only connect a calendar don't pay.
Where ten scheduling tools say they store booking data: EU or US hosting, EU region options, transfer terms and DPAs, with links to each vendor's documents.
Check your own booking workflow
Create a free account, set a retention period and look at what your booking form actually asks.
Create free account