Sub-processors
Draft — pending legal review
This document describes how Labiora currently works. It has not yet been approved by Labiora's legal advisers and may change before it takes effect. Items marked “to be confirmed” are still being finalised. Draft prepared 14 October 2026.
Service providers that process personal data for Labiora
Labiora uses the following providers to host and run the platform. Each one processes personal data only to provide its service to Labiora. How we use personal data is described in our Privacy Policy.
| Provider | Purpose | Personal data | Location |
|---|---|---|---|
| Database hosting, user authentication and sign-in, real-time updates, secure storage of service credentials, and scheduled reminders. | All platform data: accounts, organisations, cases and clinical details, messages, invoices, calendar, subscription status, consent records and audit logs. File contents are not stored here. | AWS Europe (Ireland), eu-west-1 | |
| Private storage of case files and message attachments (scans, 3D models, images, radiographs, documents). | File contents uploaded to cases, which can include patient health information. | [to be confirmed: production bucket region] | |
| Sending email: account confirmation, password reset and team invitations, and Labiora's notification emails. | Recipient names and email addresses, and the details of each notification: for example case and invoice numbers, organisation and sender names, file names, calendar event titles with the linked patient's name, invoice totals and dates, and plan or billing amounts. Case rejection and cancellation emails include the reason the person gave. Emails contain links back to Labiora. An invoice sent to an external customer also contains links to view the invoice and download its PDF, which work without signing in. Account emails contain one-time confirmation, password-reset or invitation links. Emails never contain file contents or the text of case messages. | AWS Europe (Ireland), eu-west-1 | |
| Labiora's own subscription billing: Checkout, the Billing Portal, trials and recurring payments. Stripe is not used for invoices between organisations. | The Owner's email address, the organisation's Labiora identifier and plan, and the payment details the Owner enters directly on Stripe's pages. | [to be confirmed: processing location] | |
Web application hosting [to be confirmed: hosting provider and contracting entity] | Runs the Labiora web application that every page and request passes through. | All data shown in or sent through the platform, while it is being processed. | [to be confirmed: hosting region] |
Services Labiora does not use
Labiora does not use analytics, advertising, session-recording, error-monitoring or artificial-intelligence services, and does not load fonts or scripts from third-party servers.
Changes
This list will be updated when providers change. [to be confirmed: how, and how far in advance, organisations are told about new sub-processors] Questions: support@labiora.eu.