Visit Digest Privacy Policy

Last updated: 27 October 2026
Effective: 27 October 2026

This Privacy Policy describes how Visit Digest ("Visit Digest", "we", "us", or "our") collects, uses, stores, and protects information when you use the Visit Digest mobile application (the "App"). By using the App, you agree to the practices described below.

Visit Digest is operated by Priyesh Rughani, who is responsible for your information as described in this policy. If you have any questions about this policy, please contact us at support@visitdigest.com.

1. About Visit Digest

Visit Digest is a personal health record application. It helps you record, transcribe, and summarise your own medical visits, and optionally share that information with people you choose, such as a family member or caregiver.

Visit Digest is a personal tool for patients. It is not a clinical system, electronic health record (EHR), or healthcare provider service. We do not transmit your data to your doctor, clinic, hospital, insurance company, or any other healthcare entity. Your records belong to you.

2. Our Privacy Principles

• We will never sell your data. We do not, and will never, sell, rent, or trade your personal information or health information to any third party.
• We will never share your data with advertisers, insurers, employers, or healthcare providers.
• You control your data. You decide what is recorded, what is stored, and who (if anyone) you share it with.
• We collect only what is needed for the App to function.
• You can keep a visit entirely on your device. By default, audio transcription and AI summarisation are performed by a third-party AI provider in the cloud. On supported iPhones, Pro members can turn on on-device processing so that a visit's audio and medical content never leave the device (see 7.1a).

3. Age Requirement

You must be at least 13 years of age to create an account or use Visit Digest.

We do not knowingly collect personal information from children under 13. If we learn that we have collected information from a child under 13, we will delete it promptly. If you believe a child under 13 has provided us with information, please contact us at the email address above.

A parent or legal guardian aged 13 or older may use Visit Digest to record and manage health information about a minor in their care, by creating a patient profile for that minor under the parent/guardian's own account. The account holder remains responsible for the data stored under their account.

4. Information We Collect

4.1 Information You Provide

Account information

• Email address
• Password (stored only in hashed form; we never see or store your plaintext password)
• Full name and preferred name (optional)
• If you sign in with Apple or Google: an identity token, plus the email address and name that the provider returns

Patient profile information

• Patient name and relationship to you (self, parent, child, spouse, sibling, other)
• Date of birth, blood type
• Allergies, chronic conditions
• Emergency contact information, primary doctor name, notes
• Profile photo (optional)
• Language preferences

Health information

• Medications: name, dosage, frequency, purpose, instructions, prescribing doctor, dates, side effects
• Symptoms: name, severity, duration, triggers, vital signs, notes, resolution status
• Appointments: date, doctor name, specialty, facility, reason, preparation notes

Feedback

• If you send feedback from the App: your message, its category, an optional star rating, your device platform (iOS or Android), and your account and active profile IDs so we can follow up

4.2 Information Created When You Record a Visit

• Audio recordings of medical visits, captured via your device's microphone
• Transcripts of those recordings (raw and speaker-segmented)
• AI-generated content based on the transcript: visit summary, key takeaways, tone analysis, extracted symptoms, conditions, medications, treatments, action items, keywords, and a glossary of medical terms
• Chat messages you exchange with the AI assistant about a visit
• Visit Prep conversations: your answers to the Visit Prep questions and the symptom summary and questions it produces
• Visit metadata you provide: doctor or facility name, location, visit reason, visit type, recording consent status

4.3 Information We Collect Automatically

• Device push notification token, used to deliver notifications you have opted in to
• Error logs, including error messages, stack traces, and in some cases your user ID or the ID of the visit involved, used to diagnose and fix problems
• AI usage records, specifically the number of tokens consumed by AI features for your account, used for service operation and capacity planning. These records contain only counts and timestamps and do not contain the content of your transcripts, summaries, or chats.
• Purchase and plan information: your plan (Free, Pay as you go, or Pro), purchase and renewal dates, your pay-as-you-go credit balance, and how many visits, Visit Preps and questions you have used, so we can apply your plan's limits. Payments are handled by Apple or Google; we never see your card or bank details.

We do not collect:

• Behavioural analytics or feature usage tracking
• Advertising identifiers
• Device fingerprints
• Location data (beyond what you voluntarily type into a visit)
• Data from third-party analytics SDKs (we use none)

5. How We Use Your Information

We use your information only for the following purposes:

• To operate the App: store and display your records, generate transcripts and summaries, and sync data across your devices
• To authenticate you and keep your account secure
• To deliver notifications you have asked for (sharing alerts, appointment reminders, summary-ready alerts)
• To enable sharing with people you explicitly invite
• To diagnose and fix technical problems through error logs
• To track aggregate AI token usage for capacity planning
• To provide the plan you have purchased and apply its usage limits
• To read and respond to feedback you send us

We do not use your data for advertising, profiling, training third-party AI models on your content, or any commercial purpose other than operating the App.

6. How We Store Your Information

6.1 On Your Device

• A local database stores all your visits, transcripts, summaries, profiles, medications, symptoms, appointments, and chat history.
• The database is encrypted at rest using AES-256 encryption (SQLCipher). The encryption key is stored in your device's secure keychain (iOS) or keystore (Android) and is only accessible after the device is unlocked.
• Authentication tokens are stored in your device's secure keychain (iOS) or keystore (Android).
• Your recordings are kept on your device. To transcribe a visit, the audio is uploaded over an encrypted connection to private storage, passed to our AI provider, and deleted from our servers as soon as transcription finishes. If you delete a visit, the audio file is deleted from the device.
• Recordings are included in your device's backups (for example iCloud) according to your device settings, so you keep a copy if you change or lose your phone.
• The App does not save responses from our servers in the operating system's web cache, so your health information is not left behind in unencrypted cache files.

6.2 In the Cloud

• Structured data (profiles, visits, transcripts, summaries, medications, symptoms, appointments, sharing permissions) is stored in our cloud database.
• All cloud data is protected by row-level security, meaning the database itself prevents any user from accessing another user's data unless it has been explicitly shared.
• Your health information is additionally encrypted field by field in the cloud database using AES-256, with the key held in a separate secrets vault. This covers patient names, dates of birth, allergies, conditions and notes; visit transcripts, summaries, titles, doctors, clinics and the people present; and medications, symptoms and appointments. It is decrypted only when you, or someone you have shared it with, opens it, and when our servers process it to provide the service (for example, to generate a summary).
• Details needed to run sharing, such as email addresses and the display name you choose, are not field-encrypted, but they remain protected by row-level security and by our cloud provider's encryption of its storage.
• All data transmitted between your device and our servers is encrypted in transit using HTTPS / TLS 1.2 or higher.

7. Third-Party Services

We use a small number of third-party services to operate the App. We do not sell or share your data with any third party for advertising, marketing, or commercial purposes.

7.1 AI Processing Provider

When you record or upload a visit, the audio file and resulting transcript are sent to our AI provider (Google's Gemini API) for speech-to-text and analysis. Patient context that you have entered (such as existing conditions or medications) may also be included to improve the quality of the summary. When you use Visit Prep or ask a question about a visit, your messages and the relevant visit details are sent to the same provider to generate the reply. For Visit Prep this can include the profile's age, allergies, conditions and current medicines, the appointment, and short summaries of up to five related past visits. When you translate a visit summary, the summary text is sent to the same provider, and the translation is saved with the visit.

We use our AI provider's paid API service. Under its terms, the provider does not use content submitted through that service to improve its products.

The AI provider's data handling is governed by their own policies, available here:

• Provider terms (data usage)
• Provider privacy policy

7.1a On-Device Processing (Private Mode)

On supported iPhones, Pro members can turn on On-device processing in Settings. Recordings made with it on are transcribed, labelled by speaker and summarised on your iPhone, using Apple's on-device speech recognition and Apple Intelligence on-device model. The audio, transcript and summary are not sent to us or to our AI provider, and these visits are not synced to our cloud database, backed up by us, or included in sharing or data export. Symptoms and medication changes created from them also stay on the device. Because we hold no copy, these visits cannot be recovered if you delete the App or lose your device.

Ask AI and Visit Prep ask for your permission before sending an on-device visit to our AI provider; if you allow it, that visit's details are handled as described in 7.1. The speech files and the speaker-label model are downloaded to your device when you turn the feature on. The download does not include any of your information.

7.1b MedlinePlus

When you use Visit Prep's Ask about a topic, our servers look up the topic you enter on MedlinePlus.gov, a service of the U.S. National Library of Medicine, to provide reference text. Only the topic text is sent, from our servers, never your name, account or health record. Answers that do not use your medical history may be cached on our servers for up to 24 hours, without any user identifier.

7.2 Cloud Backend Provider

We use a cloud backend provider (Supabase) for authentication, database storage, and serverless functions. This provider acts as a data processor on our behalf and stores your data subject to the security measures described in Section 6.

7.3 Sign-in Providers

If you choose to sign in with Apple or Google, those providers will return an identity token to authenticate you. We do not send your health information to these providers. Their use of the sign-in data is governed by their own privacy policies.

7.4 Email Delivery

When you invite someone to share a profile with you and they do not yet have a Visit Digest account, we send an invitation email to the address you provide, through our email delivery provider (ZeptoMail by Zoho). The email contains your name and a link to accept the invitation. Invitations expire after 48 hours.

7.5 Push Notifications

Notifications sent from our servers are delivered through Expo's push notification service, which passes them to Apple Push Notification service or Firebase Cloud Messaging (Google). These services receive your device's push token and the notification text, which never includes health details (see Section 13).

7.6 Purchases

Subscriptions and pay-as-you-go credits are sold through the Apple App Store or Google Play and managed with RevenueCat. RevenueCat receives an anonymous account identifier, your purchase and renewal history, and basic device information (such as platform, app version, and country) so it can confirm what you have bought. It does not receive your health information. RevenueCat's handling of this data is governed by its privacy policy; Apple's and Google's by theirs.

8. Sharing Your Information With Others

You can choose to share a patient profile or an individual visit with another person, such as a family member or caregiver.

• All sharing is initiated by you. We never share your information without an explicit action from you.
• You choose what the recipient can see (summary, transcript, medications, symptoms, appointments, etc.) using granular per-field permissions.
• You can revoke a recipient's access at any time.
• Audio files are never shared with other users, even if you share the visit.
• If the person you invite is not yet a Visit Digest user, we send them an email invitation containing your name and a link to sign up. They must accept the invitation to gain access.

9. Permissions the App Requests

You may decline or revoke any permission in your device settings. Some features will not function without the relevant permission (for example, you cannot record a visit without microphone access).

10. Recording Consent and Your Responsibility

Before each recording, Visit Digest displays a consent screen that you are expected to show to your healthcare provider. The provider must explicitly agree before the recording starts.

Recording laws vary by location. Some jurisdictions require all parties to consent to a recording; others require only one party. You are responsible for complying with the laws that apply to you and to the location where the recording takes place. Visit Digest provides the tool; the legal responsibility for using it appropriately rests with you.

11. Data Retention

12. Your Rights and Choices

You can exercise the following rights at any time directly within the App:

• Access: View all your data in the App.
• Export: Settings to "Export All Data" exports your visits, transcripts, summaries, and extracted medical data as a JSON file. The export is generated on your device and shared via your operating system's share sheet. No data is sent to our servers during export. Audio files are not included.
• Correct: Edit any profile, visit, medication, symptom, or appointment record at any time.
• Delete a visit: Removes the visit, transcript, summary, chat history, and audio file. Also revokes access for anyone you shared it with.
• Delete a profile: Removes the profile and all associated visits, medications, symptoms, appointments, and shares.
• Delete All Data: Settings → Delete All Data permanently deletes all your visits and their recordings, on your device and in your account. Visits other people have shared with you are kept.
• Delete your account: Settings → Delete Account permanently and irreversibly deletes your account and all associated data, including profiles, visits, transcripts, summaries, medications, symptoms, appointments, shares and invitations, push tokens, plan and usage records, and any audio still waiting to be transcribed. Error logs, AI token usage records, and feedback are kept but are no longer linked to you. Deleting your account does not cancel an App Store or Google Play subscription; cancel it in your store account settings.
• Sign out: Clears your session on the device. Local data on the device remains until you reinstall or clear app data.
• Manage sharing: Revoke any active share at any time from the Sharing screen.

Depending on where you live, you may have additional rights under laws such as the EU/UK General Data Protection Regulation (GDPR) or the California Consumer Privacy Act (CCPA), including the right to lodge a complaint with your local data protection authority. To exercise any right that is not already self-service in the App, please contact us at the email address at the top of this policy.

13. Security

We protect your information with the following measures:

• AES-256 encryption of the local database on your device, with its key in the secure keychain (iOS) or keystore (Android)
• AES-256 field-level encryption of your health information in our cloud database
• Audio deleted from our servers as soon as it has been transcribed
• No server responses saved to the device's unencrypted web cache
• Notifications sent from our servers and invitation emails never include health details: they say only that something was shared or that an appointment is coming up, without the patient's name, the doctor, the clinic, or what a visit was about
• Reminders scheduled on your device (for medications, action items and appointment preparation) are created and delivered by your device, not our servers, and show the details you entered so they are useful at a glance
• If you choose Add to Calendar for an action item, your device's own calendar screen opens with the item filled in. You pick the calendar and can edit or cancel before anything is saved. Once saved, the event is stored and synced by that calendar's provider (for example iCloud or Google), so it is visible to anyone you share that calendar with. Visit Digest does not read your calendar
• Row-level security on every cloud database table, enforced at the database layer
• HTTPS / TLS 1.2+ for all network traffic
• Authentication tokens stored in the operating system's secure keychain (iOS) or keystore (Android)
• Server-side AI provider keys, never exposed to the App
• Error logs automatically deleted after 90 days
• Nonce-verified Apple Sign-In and native Google Sign-In

No system can be guaranteed 100% secure. If we ever become aware of a breach affecting your data, we will notify you in accordance with applicable law.

14. International Users

Visit Digest is operated from, and your data may be stored or processed in, jurisdictions that may differ from your own. By using the App you consent to this transfer and processing. We apply the security measures described in Section 13 regardless of where your data is processed.

15. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date at the top and, where appropriate, notify you in the App. Continued use of Visit Digest after a change takes effect means you accept the updated policy.

16. Contact Us