MedVault Privacy Policy
Version 1.0 (Draft) · Effective date: 2026-06-15
Draft notice: This document describes MedVault's intended privacy posture and must be reviewed by legal counsel before public release. It is not yet legal advice.
1. Who we are
MedVault ("MedVault", "we", "us") publishes the MedVault iOS app. Contact: privacy@medvault.app.
2. Summary
MedVault is a local-first personal health organizer. Your records and original documents live on your device (and, only if you turn it on, in your own private iCloud). We do not run a cloud medical chart and we do not store your medical records or documents on our servers.
3. Information stored on your device
- Structured records (medications, labs, allergies, conditions, vaccinations, appointments, family history, health profile) in an on-device SwiftData store.
- Original artifacts (photos, PDFs, audio) you import, in the app's on-device storage.
- Your AI API key (if you supply one) in the iOS Keychain — never in plain storage and never sent to us.
- Optional backup: when you enable iCloud backup, the above is mirrored to your private iCloud account, governed by Apple's terms. It is not visible to us.
4. Information sent for processing (AI)
MedVault sends content to the Venice.ai inference API over HTTPS in three cases, each triggered by something you do in the app — never as a background sync of your whole vault:
- When you add a record: the single artifact or text you submitted is sent to be parsed into structured fields. Alongside it we send the names already in your vault (e.g. existing medication names) so the model can avoid creating duplicates.
- When you chat with the assistant: your messages, and any records the assistant looks up from your vault to answer, are sent so it can respond.
- Assistant memory: so the assistant remembers your context, MedVault summarizes your recent records and chats into short notes. These passes run automatically after you add records or finish a chat, and they also call Venice.
We never send your whole vault, and there is no background upload outside of the cases above.
- Today the app connects to Venice directly using your own API key (bring-your-own-key).
- In a future managed release, requests will transit a MedVault zero-retention proxy that performs no content logging (see our subprocessor list and the Managed Backend notice). The structured result returns to your device, where you review it before it is saved.
Venice performs private inference — per Venice, prompts are not stored, not linked to your identity, not used for training, and are purged after each request. The content sent can include real medical details and images, so it is not anonymous while in transit; it is transient and never retained.
5. What we do not collect
- No sale of personal or health information.
- No advertising or ad tracking, and no third-party analytics SDKs running on your vault contents.
- No developer-side database of your medical records, documents, or extraction results.
6. Our servers
In the current bring-your-own-key app, there is no MedVault server in the data path. In the future managed release:
- The inference proxy is pass-through with no disk retention of request or response bodies.
- A minimal operational database stores non-health data only — subscription entitlement status, anonymous usage counters, abuse-prevention identifiers (e.g. App Attest), and support metadata. It never stores vault contents (see the Managed Backend data boundary).
- Subprocessors: Venice.ai (inference), Apple (App Store, optional iCloud), and our hosting provider for the proxy/operational store.
7. Subscriptions
If you purchase a subscription, Apple processes the payment. We receive entitlement status (active/tier), not your card number.
8. Support
If you email support, do not include personal health information in your message. We retain only the ticket metadata and any email address you provide, to respond to you.
9. Children and international users
MedVault is not directed at children under 13. The initial release targets users in the United States; availability elsewhere will be noted as it expands.
10. Your choices and rights
- Your data is yours: you can edit or erase all data on-device at any time (Settings → Erase all data), and disable iCloud backup.
- Where applicable (e.g. GDPR/CCPA), deletion of any minimal operational record we hold can be requested at privacy@medvault.app; your on-device/iCloud data is erased by you directly.
11. Changes
We will update the version and effective date above when this policy changes and surface material changes in-app.