Sub-processors
Everyone who processes data on our behalf, what they receive, and where they are. The privacy notice promises this list; this is it. Anything not named here does not get your data from us.
1Our own hardware — the site itself
Spain (EU). The application, both databases, the uploaded documents and the encrypted nightly backups all live on hardware we run ourselves. This is not a sub-processor: it is us. No cloud database, no managed storage service and no third-party analytics service holds any of it.
2Hetzner Online GmbH — the public entry point
Falkenstein, Germany (EU). Every request to the site arrives at a proxy here and is forwarded to our own server through a private tunnel. Encryption is terminated on our hardware, not theirs, so Hetzner carries your connection and sees your IP address, but cannot read the pages you request, anything you type, or any health data.
3Mailgun (Sinch Email) — email
EU region. Sends sign-in links, address verification, account notices and — if you turn them on — dose reminders by email. It receives your email address and the content of the message. A reminder by default says only the time (“Time for your 08:00 entry”) and names no compound; naming the compound and dose is a setting you have to turn on yourself, under Account → Notifications. If you take no reminders by email, Mailgun handles only sign-in and account mail.
4Anthropic — the Research Assistant (Plus)
United States company; requests are processed globally, so they may be handled outside the EU. Covered by Anthropic’s data processing agreement with standard contractual clauses. Anthropic keeps requests and answers for up to 30 days for safety monitoring, then deletes them, and does not use them to train models. Used only if you turn on the assistant’s Plus tier and give its separate consent. It then receives your question, the conversation so far, the passages of our library it is answering from, and — unless you switch it off in Account → Health profile — a summary of your health profile, the notes you kept, your medications, your active protocol, the last two weeks of your log, your latest confirmed lab results and the supplements you listed with their daily totals. If you scan your supplement bottles, it also receives those photos, shrunk, with location data stripped and any name, address, phone or ID number found on them blacked out on our server first. We keep that blacked-out copy, encrypted with a key unique to you, so you can look at it and have it read again; it is deleted when you remove the last product read from it, and with your account. The original photo is never kept. It never receives your name, email, date of birth or location. Lab documents have names, dates of birth, addresses and ID numbers removed before anything is sent, and you see the redacted version first. If you bring your own API key instead, processing happens under your own account with your provider, not ours.
5Telegram — optional reminders and, if you choose, health conversations
Outside the EU: Telegram’s group companies are in Dubai and the British Virgin Islands. Used only after you deliberately link your Telegram account by messaging the bot yourself, under a consent recorded separately from everything else. Reminders: it receives only the reminders you asked for; by default they say the time and no more, and naming the compound and dose is a setting you turn on yourself. Health conversations: only if you also turn these on in Account → Notifications, under a second, separate consent. Then what you write to the bot — how you feel, side effects, questions — and the Research Assistant’s answers about your health pass through Telegram. Without that second consent, anything you write to the bot is neither read nor stored. We store your chat ID against your member ID; a running conversation is kept encrypted on our server for a few hours and deleted when you turn the feature off or unlink. These are the entries on this list that involve a transfer outside the EU through Telegram — if that is not acceptable to you, use push or email reminders and the assistant on the site, and nothing is ever sent to Telegram. You can unlink in Account, or send /stop to the bot.
6Browser push services — if you enable push
Google, Mozilla, Apple or Microsoft, depending on your browser, in their own regions. A push reminder goes through the push service your browser is registered with. The message is encrypted to your device before it leaves our server (RFC 8291), so the push service can see that a message was sent to a device, but not what it says.
7Stripe and Link — payments for Plus (not sub-processors)
Only if you subscribe to Plus. Stripe is a United States company, and payment data may be processed outside the EU. Plus is sold through Link, Stripe’s reseller, as the seller of record, so for your payment Stripe and Link act as independent controllers under their own privacy policies rather than on our behalf. We send Stripe your email address and an internal account reference, nothing about your health. They hold your card, billing address and invoices; we hold only your plan, its status and its renewal date.
8Not sub-processors, deliberately
Location data in our analytics is looked up in a copy of the DB-IP database held on our own server, so no address is ever sent anywhere for geolocation. Fonts and scripts are served from our own domain, so no CDN or font service sees your visits. There is no third-party analytics service, advertising network, tag manager, tracking cookie, error-reporting service or customer-support widget anywhere on the site.
9If you connect a device or service
Oura, Whoop, Withings, Garmin, Dexcom, Abbott LibreView and Google Fit are supported in the code but are not enabled in production, so no such connection can currently be made. When one is, it works only if you authorise it yourself, and those companies are separate controllers of the data in your account with them, not our sub-processors — we only read what you grant us.
10Changes to this list
We publish a change here before a new sub-processor starts handling your data, not after. The version and date at the top of this page tell you when it last changed.
Current as of the date above and checked against the running system. Two things await legal review: the exact contracting entity for each company, and the transfer safeguard relied on for Telegram (Art. 46 GDPR).