Privacy Notice
The short version
- Your care records and recordings are stored on your phone.
- When you share a person with another caregiver, or turn on backup, those records are encrypted on your phone first. We can't read the encrypted copies. We can read any words that you, or a co-caregiver you share with, choose to include in a report or email to us.
- Transcripts and summaries are the exception. To make one, the audio or notes are sent, readable, through our cloud provider (Cloudflare) to our AI providers (Deepgram and Anthropic) and deleted after a short time.
- If you report something to us, our team can read the report, including any note you write and any words you choose to include from the entry or summary you report. A co-caregiver who reports an entry you shared, or its summary, can choose to include its words.
- If you email us, our email providers and team can read any health details or attachments you choose to send. These messages are not protected by the app's record encryption.
- We don't sell personal information, show ads or track you across apps and websites.
- We can't recover a backup if you forget its password and have no other signed-in phone.
1. Who we are
MyVisitVault is operated by MyVisitVault LLC, a Virginia limited liability company ("we", "us"). This notice explains how we handle information in the MyVisitVault app, at myvisitvault.com and in our beta program.
MyVisitVault is a tool for family and other caregivers to keep their own records of medical visits. We are not a doctor, hospital, health plan or healthcare provider, and we don't provide the app on behalf of one.
2. Who this notice covers
- Account holders: caregivers who create a MyVisitVault account.
- Co-caregivers: people a caregiver invites to share a person's records.
- People in the records: the person being cared for, and anyone whose voice is recorded during a visit. Caregivers enter this information; we explain below how it is handled.
- Beta applicants and website visitors.
3. What we collect and why
| Information | Where it goes | Why |
|---|---|---|
| Email address, password (stored hashed by our sign-in provider), account ID, plan status | Our servers (Supabase) | To create and secure your account and provide your plan |
| App account ID | RevenueCat (our subscription service) | To identify and check your plan when you sign in online, even before a purchase |
| Care records: people you care for, visits, notes, recordings, medications, diagnoses and procedures | Stored on your phone. The app sends it only as described in sections 4 and 4a. You may separately choose to email us health details or attachments, as described in the email row below. | To keep your records |
| Records you share with co-caregivers, and backups | Our servers, encrypted. Shared records and backups are encrypted on your phone first; AI processing and words included in reports are handled as described in sections 4 and 4a | To share with people you invite, and to restore your records on a new phone |
| Audio and typed notes sent for transcripts or summaries | Sent readable through Cloudflare to our AI providers; see section 4 | To produce transcripts and summaries you asked for |
| Sharing details: who you invited, their email, display names, and which people are shared | Our servers | To deliver invitations and shared records |
| Reports you make: your account, the account the report is about, what you reported, the reason, when, an optional note, and words from the reported entry or summary only if you choose to include them | Our servers (Supabase), readable by our team; see section 4a | To review what you report |
| Blocks: who blocked whom, when, and a coded (hashed) form of the blocker's email address | Our servers (Supabase); see section 4a | To stop invitations and sharing between blocked accounts |
| Device and app identifiers, push notification token, app version | Our servers; Google Firebase (for push delivery) | To sync shared records between your phones and send notifications. Notifications contain no care information. |
| Purchase history and subscription status | Apple or Google, and RevenueCat (our subscription service) | To provide the plan you buy. We never receive your card details. |
| Error reports: app version, device platform and technical crash details | Our servers, stored without your account ID | To find and fix problems |
| Beta applications and referrals: contact and store email addresses, platform, answers, consent and enrollment history, verification and opt-out records | Our servers; Cloudflare and Resend for enrollment and email; Apple or Google when you join their test program. See Beta enrollment and referrals. | To verify applications, manage test access, deliver builds, prevent abuse and track program costs |
| Messages and attachments you choose to email us may contain health information | Cloudflare Email Routing forwards them to our Google Gmail inboxes, where our team can read them | To answer your messages and handle privacy, support and beta requests |
We send your app account ID to RevenueCat when you sign in online to check your plan, even if you have not bought one. We do not send care records to RevenueCat. Email you choose to send us is separate from records protected by the app's sharing and backup encryption.
The app has no advertising, analytics or tracking tools. Our website uses Cloudflare Web Analytics, which our host adds to website pages to count visits and measure how quickly pages load. Cloudflare says it doesn't collect visitors' personal data or track people across websites. We don't use it for advertising. We don't sign you in with Google or Apple accounts, and we don't collect your location, contacts or photos.
Beta enrollment and referrals
When you apply for the beta, we keep your name, contact email, phone platform, caregiving role and other answers, the version of the Beta Terms you agreed to and the Privacy Notice you acknowledged, and your application and admission history. Your Google Play account email or TestFlight invitation email can differ from your contact email. We use those addresses to arrange test access. If you sign in to the app, we use your app account email to link that account to your application. Applying does not guarantee a place in the beta.
If an applicant names a co-caregiver, we hold the address they provide. We send an invitation only after the applicant is admitted to the beta on at least one platform. The applicant may request one resend. Being named does not mean the co-caregiver has agreed to join, and it does not share any care records. The invitee can decline that invitation or ask not to receive further beta invitations.
Our servers keep the minimum records needed to verify addresses, decide admission, count participants, prevent duplicate or unwanted invitations, deliver test builds, and show program operating costs. These include hashed verification and session tokens, temporary salted hashes of an IP address or request identity for rate limiting, coded (hashed) email addresses used to honor opt-outs, and limited references showing whether a managed store-test membership was added or removed. The cost records are aggregate and do not contain care records or account identifiers.
Resend delivers beta messages. Cloudflare handles the website, bot protection and enrollment requests. For an admitted iPhone tester, we give the TestFlight invitation email to Apple; Apple sends the test invitation and handles TestFlight feedback and analytics. For an admitted Android tester, we add the Google Play account email to a managed Google group used for closed testing and license testing. Apple and Google handle their own test-platform records under their privacy policies.
You can ask to change an address, leave the beta, or access, correct or delete an application by emailing beta@myvisitvault.com. You can do this even if you never create an app account. Declining ends that referral. If you ask not to receive further beta invitations, we keep a coded opt-out record for the limited period below.
4. How care information is handled
On your phone
Care records and recordings are stored inside the MyVisitVault app on your phone. MyVisitVault doesn't add its own encryption to them there; your phone's lock and security protect them. They are excluded from iCloud and Android device backups. Anyone who can unlock your phone and open the app can see them, so the app also asks for your face, fingerprint or passcode.
Sharing with co-caregivers
When you share a person, their records are encrypted on your phone with keys held only by your phones and the invited caregivers' phones, then sent through our servers. We store the encrypted data plus the routing details needed to deliver it (such as which accounts and devices it is for). AI processing and reports are handled separately, as described below.
When sharing ends, co-caregivers keep the records already on their phones as independent copies they can edit. This includes when the primary caregiver stops sharing, their sharing entitlement ends, or they delete the person. Changes to these copies no longer go to the former sharing group. If you share again later, the recipient gets a separate person in the app; the earlier copy is not merged or overwritten.
Backups
Backups are encrypted on your phone using a password you choose, then stored on our servers. We don't hold a key that can open them. If you forget the password and don't have another signed-in phone that can reset it, the backup can't be recovered, by you or by us.
Transcripts and summaries (AI processing)
To make a transcript or summary, information leaves your phone in readable form:
- Audio is uploaded to our cloud provider (Cloudflare), sent to Deepgram to turn speech into text, and deleted after processing. Any leftover copy is removed automatically within about a day.
- The transcript, or your typed notes, is sent through our Cloudflare servers to Anthropic (Claude) to write the summary.
- Readable results held for collection are deleted within five minutes. For delivery that can continue after your phone disconnects, we also encrypt results, and audio when included, for the receiving devices, including your own phone. These encrypted copies stay on Cloudflare until the receiving devices have confirmed delivery or their delivery is cancelled. Automatic cleanup removes them after any required 24-hour period following confirmed delivery.
- Anthropic deletes this data within 30 days and doesn't use it to train its models by default. It may keep flagged content longer to enforce its usage policies.
- We opt out of Deepgram's model-improvement program on every request, so Deepgram keeps the audio only as long as needed to make the transcript and doesn't use it to train its models.
- We don't collect, use or sell personal data, including health data, to train large language models.
Summaries are generated automatically and can contain mistakes. They are for your records and aren't medical advice. Always check important details with the care team.
4a. Reporting and blocking
Reports
When you report an invitation, another caregiver, a shared entry or an AI summary, we store:
- your account, and the account the report is about. Our server confirms which account that is from what you reported; you don't type it in. A report about an AI summary isn't about another account.
- what you reported, the reason you picked from a fixed list (such as harassment, spam or an inaccurate summary), and when you reported it
- codes that identify the invitation, shared person or entry involved, but not its contents
- your phone type (iPhone or Android) and app version
- a short note in your own words, if you write one (up to 500 characters)
- words from the entry or summary you're reporting, only if you choose to include them (up to 8,000 characters). If the app doesn't offer that choice, it doesn't include them.
We also record whether our team has closed the report and how, and technical details that stop the same report from being saved twice.
Reports are stored on our servers (Supabase), where other users, including the person you reported, can't see them. Our team can read them. That includes your note and any words you include: they aren't protected by the encryption used for shared records and backups, so that we can review the report. A co-caregiver who reports an entry you shared, or its summary, can choose to include its words in the same way; you aren't asked first.
Each report is deleted automatically 365 days after you make it, or 90 days after our team closes it if that comes first.
Blocks
When you block someone who sent you an invitation, or another caregiver of a person you share or used to share, we store:
- your account and theirs, and when you blocked them
- whether you blocked them from an invitation or from a shared person
- a coded (hashed) form of your email address at that time, used to refuse their invitations to you
You can't block someone while you still share a person with them, so blocking them then also means leaving that person or removing them from it. While the block is in place:
- They can't send you invitations. Blocking also ends pending invitations between you: theirs to you are declined, and yours to them are cancelled.
- They can't accept an invitation to a person you're a caregiver for, and you can't accept one to a person they're a caregiver for. The one exception is an invitation you send them yourself after blocking them: they can accept it unless another block applies between them and a caregiver for that person.
We don't tell the person you block. But if they try to invite you, or to accept an invitation to a person you're a caregiver for, they're told the invitation can't be sent or isn't available, and they may be able to work out that you blocked them. They can't see your list of blocks.
A block lasts until you remove it or either account is deleted. Removing a block deletes it.
To limit misuse, we keep a count of how many reports, blocks and unblocks each account makes per day.
5. Service providers
We use these companies to run MyVisitVault. They process information on our behalf for the purposes above:
- Supabase: accounts, database and encrypted backup storage
- Cloudflare: our servers, temporary audio and result storage for transcripts and summaries, website, website analytics and bot protection
- Deepgram: speech-to-text
- Anthropic: summaries
- RevenueCat, Apple and Google: subscriptions and payments
- Google Firebase: push notification delivery
- Resend: account, beta and invitation emails
- Google Gmail: inboxes for messages you choose to email our privacy, support or beta addresses, forwarded through Cloudflare Email Routing
We don't sell or rent personal information, and we don't share it for advertising. We may disclose information if the law requires it, to protect someone's safety, or as part of a sale or transfer of the business, in which case this notice continues to apply to your information.
6. How long we keep information
- Records on your phone: until you delete them or remove the app.
- Shared records in transit: encrypted deliveries become eligible for automatic cleanup 24 hours after confirmed delivery. Copies needed for delivery or encryption-key recovery stay until that work ends and its retention period has passed.
- Backups: while backup is part of your plan. If your plan ends, backups become restore-only for a limited time and are then deleted.
- Audio sent for transcription: deleted after processing, and within about a day at most. Readable results held for collection: within five minutes. Encrypted results and audio for delivery: kept until delivery is confirmed or cancelled, then removed by automatic cleanup after any required 24-hour period following confirmed delivery.
- Error reports: 90 days.
- Reports: deleted automatically 365 days after they're made, or 90 days after our team closes them if that comes first. Deleting your account deletes the reports you made sooner. A report about an account that is later deleted stays until its normal deletion date, with the link to that account removed.
- Blocks: until the person who made the block removes it, or either account is deleted.
- Daily counts of reports, and of blocks and unblocks: each is replaced by a later day's count the next time the account makes a report, or a block or unblock, respectively, and deleted with the account.
- Account information: while your account is open. When you delete your account, we remove it within 30 days, except a record that the account was deleted, which we keep for 12 months, and the limited technical records needed to tell other devices that sharing has ended (section 8).
- Unverified beta applications: deleted after 7 days. Ordinary application, address and status links expire after 2 hours; referral-join links expire after 72 hours.
- Beta rate-limit records: temporary salted IP-address and request-identity hashes expire after 5 minutes.
- Unconfirmed referral addresses: deleted 14 days after collection if no invitation is sent, or 14 days after the last invitation. They are deleted immediately if the invitee declines or opts out, or the sponsor withdraws the referral. A coded address may remain with the sponsor's application to count referrals.
- Verified beta applications: kept until 90 days after the beta ends, unless the applicant becomes a MyVisitVault user. Then the application follows the account and is deleted with it.
- Beta email and processing history: delivery and job records are deleted 90 days after reaching a final state. They do not contain email addresses or message bodies. A record of a managed Apple or Google test membership stays while access is active or removal is unresolved, then is deleted 90 days after we verify its absence.
- Beta opt-out records: an opt-out link normally lasts 31 days; a valid pending or sent invitation may renew its suppression deadline. A detached hashed link record is removed after that deadline and a 7-day cleanup period. Coded addresses used to prevent unwanted invitations stay until 12 months after all beta programs end. They contain no care records.
- Aggregate beta cost records: kept for 13 months without care or account identifiers. Resend says it keeps email and log data for 30 days on its Free, Pro and Scale plans; Enterprise retention may differ. We have not verified which plan our account uses. Apple and Google may keep their own test-platform records under their policies.
- Messages you email us: kept while we handle your request. For completed account-deletion cases, we plan to remove the correspondence 12 months after the confirmed request; unresolved cases stay until resolved. Other support and beta mail has no fixed deletion period yet. Our email providers may retain their own copies under their policies, and deleting your app account does not automatically remove those copies.
7. Your choices and rights
- You can use MyVisitVault without transcripts or summaries. Typed notes and recordings still work on your phone.
- You can stop sharing a person, leave a shared person, or turn backup off at any time.
- You can ask us to access, correct or delete your information. We'll respond within 45 days. If we decline a request, you can ask us to reconsider by replying to our answer.
- We send account and service emails. We don't send marketing emails. If that changes, we'll ask you first, and every marketing email will include a way to unsubscribe.
Depending on where you live, state law may give you additional rights, described in the next section.
7a. Consumer Health Data Privacy Policy
This section is our consumer health data privacy policy under the Washington My Health My Data Act, Nevada's consumer health data law (NRS 603A) and Connecticut's Data Privacy Act. It applies to everyone.
- Health data we handle: the care records, notes, recordings, transcripts, summaries, medications, diagnoses and procedures you enter about yourself or the people you care for, any health information that you or a co-caregiver include in a report, and any health details or attachments you choose to email us.
- Why: to provide the features you use: keeping records, sharing with caregivers you invite, backups, the transcripts and summaries you request, and reviewing reports you make; and to answer messages or handle privacy and support requests you email us.
- Sources: you, co-caregivers you share with, the recordings you make, other users who make a report, and messages or attachments you email us.
- Sharing: with the co-caregivers you invite, encrypted, and with our service providers listed in section 5. For in-app transcripts and summaries, Cloudflare, Deepgram and Anthropic receive readable health data. Anything written or included in a report, by you or by a co-caregiver you share with (a note, and any words from an entry or summary), passes through Cloudflare and is stored by Supabase, our database provider, where our team can read it (see section 4a). Health information you choose to email us is readable to Cloudflare Email Routing, Google Gmail and our team; it is not protected by the app's record encryption.
- Consent: when you add a person, the app asks you to confirm you're allowed to keep their health information. Before you share a person, it shows who will get a copy of their records. Before sending health data for transcripts or summaries, it asks for your permission. You can turn AI transcripts and summaries off in Settings. This stops new processing requests; information already sent is handled as described in section 4.
- We never sell health data or use it for advertising.
- Your rights: confirm whether we hold your health data, see it and the third parties it went to, withdraw consent, and ask us to delete information we hold, including backups. A report another user made stays until its normal deletion date, and email providers may retain their own copies as described in section 6. Email privacy@myvisitvault.com. We respond within 45 days, extendable once by another 45 days when necessary, and we'll tell you if we extend.
- Appeals: if we deny a request, reply to our decision to appeal. We'll decide within 45 days and explain the result. If you disagree, you can contact your state attorney general.
8. Deleting your account
To delete your account, follow the steps on our account deletion page, or email privacy@myvisitvault.com from the address on your account. Deleting your account removes your account, shared-record deliveries and backups from our servers. It also deletes the reports you made and every block you made or that someone made against you. A report someone else made about you is kept until it is deleted on its normal schedule (section 6). Records stored on your phone stay there until you delete the app. Co-caregivers keep the copies already on their phones as independent records they can edit. We keep limited technical records needed to tell their devices that sharing has ended until those updates have been received. Deleting your account doesn't cancel a store subscription: cancel it in your Apple or Google account settings.
9. Security
We encrypt ordinary shared records and backups on your phone. For AI processing, readable information passes through our servers as described in section 4; copies kept for delivery are encrypted for the receiving devices. We use encrypted connections and limit who can access our systems. No system is perfectly secure. If a breach affects your information, we'll notify you as the law requires.
10. Children
MyVisitVault accounts are for adults 18 and older. Caregivers may keep records about a child in their care. We don't knowingly create accounts for children.
11. Recording other people
Laws about recording conversations differ by state, and some require everyone's permission. Before recording, the app asks you to confirm that everyone being recorded has agreed. You are responsible for getting that permission.
12. Changes to this notice
We'll post any new version here with its effective date and keep previous versions available. If a change materially affects how we use information we already have, we'll tell you in the app or by email first.
13. Contact us
MyVisitVault LLC. Email privacy@myvisitvault.com.