Sub-processors
The providers Xolotl uses to run the practice software, what each one receives, and where. A practice is told before a new one starts.
How this list works
In the software, the practice is the controller of its clients' and patients' data and Xolotl is its processor. The providers below are the ones Xolotl engages to run the service (GDPR article 28). We tell each practice before adding or replacing one, and the practice can object.
Xolotl is not yet running for practices, so several providers below are planned rather than in use: the Status column says which. Our data processing agreement is available on request at contact@xolotl.vet.
The list
| Provider | What for | Where | Transfer safeguard | Status |
|---|---|---|---|---|
| Amazon Web Services | Hosting: servers, database, file storage, backups | European Union (Paris, France) | None needed: the data stays in the EU | Planned |
| Amazon Web Services (Amazon SES) | Reminders, invoices, sign-in codes and portal e-mails | European Union (Paris, France) | None needed: the data stays in the EU | Planned |
| GatewayAPI (OnlineCity.IO ApS, Denmark) | SMS reminders and the clients' replies | European Union | None needed: the data stays in the EU | Off until SMS is turned on |
| Twilio | SMS instead of GatewayAPI, if chosen; WhatsApp messages | United States | EU-US Data Privacy Framework and standard contractual clauses | Only if chosen |
| Apple (APNs) | Notifications on staff Apple devices | To be confirmed | To be established | Off until configured |
| Google (Firebase Cloud Messaging) | Notifications on staff Android devices | United States | EU-US Data Privacy Framework and standard contractual clauses | Off until configured |
| Sentry | Error tracking | To be chosen: an EU data region, or our own server | Data Privacy Framework and standard contractual clauses, unless kept in the EU | Active once configured |
| Stripe | Card payments at the terminal | To be confirmed | To be confirmed | Off until configured |
| e-invoice.be | Peppol access point for e-invoices | To be confirmed | To be confirmed | Used when a practice sends Peppol invoices |
| Mistral AI (Paris) — the AI scribe | Transcribing web dictation and drafting the record from what the vet dictated, for the vet to check field by field | European Union (zero data retention and no training, to be confirmed in the contract; or a model we host ourselves on EU servers) | None needed: the data stays in the EU | Planned, off by default |
Data Privacy Framework entries checked on dataprivacyframework.gov on 2 October 2026.
What each one receives
- Hosting: everything the practice stores.
- E-mail, SMS and WhatsApp: the recipient's address or number and the message, which can name the practice, the animal and the appointment.
- Notifications: a device token and the text of the alert.
- Error tracking: technical error reports. Program variables are not sent, and eID and national-number fields are removed.
- Card terminal: the amount and an invoice reference. Card details go from the reader to Stripe and never pass through Xolotl.
- Peppol: the invoice, including the business customer's name and address.
- AI scribe (a pilot, off by default): the audio of a web dictation (deleted once the record is validated, or at the latest after the practice's quality hold of 30 days at most), the transcript, and the animal's species, breed, sex, age, weight, allergies and current prescriptions. No client name, address, phone or national number, no animal name. On Mac and iPad, speech becomes text on the device and only the text is sent.
Who is not on this list
Recipients the practice chooses itself: its laboratory (IDEXX or Antech, for example), its bank feed (CodaBox), Payconiq, its wholesalers and insurers, and the calendar and sign-in accounts of its own users. The practice sets them up with its own credentials, and Xolotl sends them data on its instruction.
Authorities are not sub-processors either. What a vet declares to the FAMHP (VAMREG), to ARSIA (BIGAME) or to the FASFC (Sanitel) is declared under the vet's own legal obligations.
Nor are the systems a practice connects itself, with the API keys and webhooks it creates in Xolotl (Settings > Integrations): the system reading with a key and the address receiving the webhooks are the practice's own processors or recipients, under its own agreement with them.
One AI provider, off by default
The AI scribe is the only feature that sends practice data to an AI provider, and it is off until the practice switches it on. It only drafts: the veterinarian checks every proposal before anything is saved, parts of the record it drafted are labelled as such, and the client is told before a consultation is recorded and may refuse. The provider is in the EU and keeps nothing after answering; we confirm both in its contract before it starts, and practices are told.