Data Processing & GDPR
Last updated: August 2026
Contents
1. Roles
Because Alnora runs entirely on your infrastructure:
- You (the clinic) — are the data controller for all patient and appointment data Alnora stores on your site, and decide how it is used.
- Alnora (the vendor) — provides the software but does not host, receive, transmit or access that data, and is therefore not a processor of it. We only process the limited account data described in section 7.
2. What Alnora stores on your server
On your WordPress database, the plugin may store:
- Patient details (name, contact, date of birth) and appointment history.
- Optional encrypted medical records — diagnosis, prescription, notes and attached files.
- Consent logs, recording the consent text shown plus a timestamp and IP address at the time of booking.
- Any custom booking-form fields you choose to collect.
- Payment records — amounts, and the gateway transaction and refund reference IDs used to reconcile payments and process refunds. Card and bank details are held by the gateway, never by Alnora.
3. Security & encryption
Medical records are encrypted at rest (AES-256) and stored only on your server. Because you control the hosting, you are responsible for the security, backups and access control of that server. See Medical records in the docs.
4. Integrations you enable (your sub-processors)
Alnora can connect to third-party services — but only when you turn them on and add your own credentials. In each case the data travels directly from your site to that provider; it does not pass through Alnora. These are your sub-processors, and you should have your own agreement with each:
| Service | Used for | Data sent (when enabled) |
|---|---|---|
| Stripe, PayPal | Online payments & refunds | Payment or refund amount and the payer/transaction details they require |
| Twilio | SMS & WhatsApp reminders | Patient phone number and the message |
| Telegram | Telegram reminders | The message, sent to the patient’s connected Telegram account (no phone number — the patient opts in through the bot) |
| Google Calendar, Microsoft Outlook | Calendar sync | Appointment time, doctor and service on the event |
| Zoom, Google Meet | Telehealth links | Appointment meeting details |
| Zapier | Automation webhooks | Event, time, doctor, service and patient name/email/phone. The free-text “reason for visit” is deliberately excluded. |
If you enable none of these, no patient data leaves your site at all.
5. Built-in GDPR tools
To help you meet your obligations as controller, Alnora includes a GDPR toolkit — consent logging, configurable retention, a data export, right-to-erasure handling, and an audit log. Consent capture (timestamp + IP) is available even in the free version.
6. Handling data-subject requests
As the controller, you handle requests from your patients (access, rectification, erasure, portability). Alnora’s export and erasure tools let you fulfil them directly from your admin, and the audit log records access. Because we hold none of this data, such requests are not directed to us.
7. The data we do process (website & account)
Separately from your patient data, we process limited account data when you buy or contact us — your name, email and licence/subscription status — via our checkout provider Freemius. That is covered in our Privacy Policy.
8. Contact
For data-protection questions about the product, email admin@alnora-booking.com.