Sub-processors
Last updated: August 25, 2026
Diavisor is operated by Magma Company GmbH. This page lists every third party that may process personal data on our behalf, or that receives personal data because of a feature you choose to use.
We keep this list short on purpose. Diavisor handles health data, so every additional party is a risk we have to justify. We use no analytics, advertising, tracking, error-reporting, or marketing providers.
Always in use
These process data for every user, because they are what the Service runs on.
| Sub-processor | Purpose | Data | Location |
|---|---|---|---|
| DigitalOcean, LLC | Application servers, database, file storage | All account and health data | Amsterdam, Netherlands (European Union) |
| Cloudflare, Inc. | DNS and the reverse proxy in front of the API, which terminates TLS | All account and health data in transit, and request metadata (IP address, user agent) | Nearest edge location worldwide; the origin is in the European Union |
| Vercel, Inc. | Hosting for the web application and this legal site | Request metadata (IP address, user agent) | United States, with edge locations worldwide |
Used only when you turn a feature on
Nothing below receives any data unless you choose to use the feature it belongs to.
| Sub-processor | Triggered by | Data sent | Location |
|---|---|---|---|
| OpenAI, L.L.C. | Estimating carbohydrates from a meal photograph | The photograph you take, and nothing else — no account identifier, no glucose data, no name | United States |
| Telegram Messenger Inc. | Linking Telegram to receive alerts | Alert messages, which contain glucose values and trends, sent to the Telegram account you link | Outside Switzerland and the EEA |
Abbott (LibreLinkUp, api-eu.libreview.io) | Connecting a FreeStyle Libre account | Your LibreLinkUp credentials, in order to retrieve your glucose readings | European Union |
On the photo feature. The image is sent to OpenAI to get a carbohydrate estimate back. Once you have used it, the photo is stored with the calculation it belongs to. If you would rather no photo of your food ever left Switzerland, do not use the feature — everything else in Diavisor works without it.
On Telegram. Telegram is a consumer messaging service, not a healthcare provider, and it operates outside the EEA. Alerts sent through it contain your glucose values. Link it only if you accept that.
Not sub-processors
| Party | Why it is not one |
|---|---|
| Your Nightscout instance | Nightscout is software you run yourself. When you connect it, we send your credentials to a server you control and operate. It is your infrastructure, not a processor acting for us. |
| A clinician you share a code with | They receive your data because you decided to give it to them. They act for themselves or for you, not for us. |
| Apple | Distributes the iOS app. Diavisor sends no health data to Apple, and does not use iCloud, HealthKit, or Apple's analytics. |
Changes
We will update this page whenever we add or remove a sub-processor. Where a change materially affects how your health data is handled, we will make reasonable efforts to tell you in advance.
Questions about anyone on this page: support@diavisor.com.