How your health data is protected

Everything you record here is encrypted. You choose who holds the key when you join, and this page says plainly what each choice means.

Two ways to hold the key

Standard protection

We look after your key

  • Lose your device or forget everything? Sign in by email and your data is there.
  • Reminders, Telegram, wearables and sharing all work in the background.
  • Our systems can unlock your data to run those features. Our staff can't browse it: opening one member's record takes a written reason and a second person's approval, lasts 60 minutes, and you are told every time.

Private vault

You hold the key

  • Your data is encrypted on your own device with a passphrase only you know, before it reaches us. We store it but cannot read it.
  • Nobody at RPB can open it, and neither can anyone who breaks into our systems.
If you lose both your passphrase and your recovery key, your health data is gone for good. We cannot reset your passphrase and we will not be able to help.

What a private vault covers

In a private vault your data is encrypted in your browser before it reaches us, and decrypted only there. A few things need our server for a moment, and each is listed here.

In the vault today

  • Protocols and every version of them
  • Your daily log: doses, measurements, side effects and notes, including entries made offline
  • Vials and batch numbers
  • Your health profile and your list of medicines
  • Lab reports and certificates of analysis: the blacked-out pages and the values read from them
  • Supplements and vitamins, with the label photos they were read from
  • A full export of all of it, and spreadsheet, calendar and Markdown files of a protocol, all made on your device

Leaves your vault only if you switch it on

  • Dose reminders: we keep the times so we can remind you while your vault is locked. The name and amount of the dose are kept only if your reminders are set to say them.
  • A reminder button you tap while locked: recorded in a form only your vault can open, and added to your log when you next unlock.
  • Share links: we store an encrypted copy of what the link shows. The key is part of the link and never reaches us, so only people you give the link to can read it.
  • Connected wearables: we keep which metrics you chose and, for a connected account, the access it gave us, so data can arrive while your vault is locked. Each day's readings pass through our server once and are sealed to your vault as they arrive; after that we cannot read them.

Sent once, when you ask for it

  • A question to the Research Assistant: your question and a summary of your record, written on your device, pass through our server to the AI provider. We keep how much was used, and a record only your vault can open. The conversation is saved in your vault.
  • Your own AI provider key: sent once to be checked, then with each question, for that request only. It is stored only in your vault.
  • A lab report or certificate you upload: the file is sent to our server to be turned into page images and text, which come straight back to your device. We keep no copy. Blacking out your details and encrypting the pages happen on your device.
  • An AI explanation of a lab report: the marker names, values and ranges, never the pages, pass through our server to the AI provider with your own key. The result is saved in your vault.
  • A photo of a supplement label: sent to our server to be read by the assistant you chose. It comes back with any personal details blacked out and is stored only if you save the product, encrypted on your device first. Looking up a product by name sends the name.
  • A PDF of a protocol, or of your supplements and medicines: what is to be printed is sent to our server, laid out and returned. For a verified protocol PDF we keep the verify ID and the file's fingerprint, never the contents.
  • A question in an "Ask about this page" box: the question and what is on that page are sent to the AI provider through our server, as with the Research Assistant.

Not available in a vault

  • Health conversations in Telegram that use your record, and logging a dose or scanning a label by Telegram message. Telegram reminders, and the Telegram assistant without your record, still work.
  • Help from our staff that would mean looking at your data, and resetting your vault by email.

Each of these would need your key while you are away, or in someone else's hands, which is what a private vault rules out.

What we can still see

  • Your account: email, display name, country, forum posts and subscription. We hold these for every member, whichever protection they chose.
  • That entries exist and when: how many protocols you have and their status, which days you logged, and the size of each encrypted entry. Never what is in them.
  • Anything you choose to publish or post.

What a private vault cannot protect you from

  • Losing both your passphrase and your recovery key. We cannot reset either, and your health data would be gone for good.
  • Someone who knows your passphrase and can sign in as you.
  • A device that is itself compromised.
  • The code that does the encrypting is delivered by our site each time you visit, as with any web app. You are trusting that we serve honest code. We keep that surface small: a strict content security policy and no third-party scripts.

How we look after a key we hold

  • Every member has their own key, and those keys are themselves locked by a master key that is not kept in the database.
  • Health data is stored in the EU, separately from your email and identity.
  • Staff cannot browse it. Opening one member's record takes a written reason and a second person's approval, lasts 60 minutes, and the member is told every time.
  • Backups are encrypted, and deleting your account destroys your key, which makes every copy unreadable.

Deleting

In either mode, deleting your account deletes your health data and destroys the key material. Backups made before that age out within 14 days.

Create an account