Try the demo before you create a bucket
The demo vault is an in-tab sandbox. No Google account, no S3 keys, no leftover objects. Close the tab and it is gone. That is the right first step if you want to see a panel consult, not learn IAM.
Use real storage when you decide the file should survive a refresh and sync to another device.
Google Drive — the fast path
For most people, Drive is enough. DoctorVault asks for a narrow drive.appdata folder — a hidden app folder, not your Photos or Docs. OAuth happens in the browser. Tokens live in the encrypted vault, not on our servers.
You still need a passphrase and a recovery code. Losing both means the Drive folder is unreadable ciphertext. We cannot reset it.
S3, R2, B2, MinIO — the power-user path
Use S3-compatible storage when you want a bucket you fully control, multi-device sync with conditional writes, or no Google account in the loop. Cloudflare R2 and Backblaze B2 are common cheap options. MinIO works if you already run it.
You will need:
- A bucket plus an access key scoped as tightly as you can stand
- CORS allowing
https://doctorvault.aifor GET, PUT, DELETE, HEAD, withETagexposed (required for sync)
The onboarding form includes presets. If health-check fails, it is almost always CORS or a key that cannot write.
What storage providers can and cannot see
Objects in Drive or S3 are AES-256-GCM envelopes created in your browser. The provider sees that you stored blobs. They should not see labs, chats, or keys. They can still delete the objects, throttle the API, or change their terms — you picked that vendor.
Full data-flow language is in the privacy policy. If you want a durable vault, keep your own backup of the recovery code and consider that your storage account is now part of your health continuity plan.
Try it in the demo vault
No account. Nothing is saved when you close the tab. Add a couple of sample records, ask the panel one question, then read how to verify that our servers never see the contents.