MyVisitVault

Privacy Notice

Version 2026-11-12 · Effective November 12, 2026 · Previous version (November 4, 2026) · September 27, 2026 version · September 26, 2026 version · June 22, 2026 version

The short version

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

3. What we collect and why

Information, where it goes and why
InformationWhere it goesWhy
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
Care records: people you care for, visits, notes, recordings, medications, diagnoses and procedures Stored on your phone. Leaves it only as described in sections 4 and 4a. 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 you send us Our email To answer you

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:

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:

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:

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:

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:

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

7. Your choices and rights

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.

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.