Privacy Policy
What is kept
- Your account: your name, your email address, a hash of your password rather than the password, a passkey if you registered one, and your time zone.
- Your records: what the portal answers when the app syncs, kept with the portal's own text for appointments, prescriptions, lab results, immunizations, conditions, treatments, insurance coverages and messages, a small picture of each image attached to a message, one small picture of a scan the portal publishes pictures for (the scan itself comes from your health system's own image viewer, reached through the portal), and the raw payload each row was read from.
- What you bring: files you upload with all their bytes, notes you write, Apple Health exports and the readings derived from them, and reminders with their attachments.
- What you say: your conversations with the assistant, the passages it read to answer, any draft it wrote into a document, and a file you attach to a message — kept as the text the file contains, not as the file.
- What is connected: for MyChart, the portal session or passkey the app reuses to sync, never your password; for Granola, the grant that lets it read your meeting notes.
Where it lives
- App runs on Vercel. Database hosted by Supabase. Records we get from MyChart and documents you upload are saved in that database.
- Logging uses BetterStack and error reporting uses Sentry.
- Email is sent through Resend.
- A visit's address is turned into a point by OpenStreetMap's Nominatim and the map is drawn from Esri's tiles.
- A drug, condition or lab test's name is looked up in MedlinePlus, in the FDA's label filing as served by openFDA, and, for a brand name, in RxNorm.
- A condition with an ICD-10-CM code is looked up in the National Library of Medicine's Clinical Tables index instead, by the code alone.
- When you ask the assistant what a medicine, a test or a condition means, it may also look the name up in DailyMed, in the European Medicines Agency's register of medicines, in PubMed's index of published research, or in the World Health Organization's health statistics.
- When you paste a link, or a search turns up a page worth reading, the app's server fetches that address and reads the page's text so the assistant can answer from it. Nothing about you goes with the request — no cookie, no record, no account — so the site learns only that a page of theirs was read, and when. Addresses on private or local networks are refused, and the page's text is treated as what it is: somebody else's writing the assistant may quote, not an instruction it follows.
When you ask it about something outside your records — a clinic, a therapist, a pharmacy, what reviews say about a practice, where a service is — it searches the web through Tavily.
What is encrypted, and where that stops
- The portal session, the portal passkey and every MCP grant are encrypted with AES-256-GCM. Reading the database without that key does not hand somebody your portal login.
- The record's own content is not encrypted. Names, dates, doses and lab values are columns of text like any other, so anyone with the database's credentials can read every row: this is the largest risk the app carries, and it is stated here rather than left to be inferred.
- Our AI assistant will send information to 3rd party LLMs for various uses, including but not limited to answering questions, highlighting health concerns, updating user notes, and so forth. We will be using different LLMs throughout development of this product.
What it never does
- No ads, no ad network, no cross-site tracker, no analytics profile, and no selling or sharing of your data.
- No bank, insurer or employer connection. A portal is a login you give, and a document is a file you upload.
- No third party receives your record beyond the ones named above, and none of them receives it for a purpose of its own.
Offline copies on your device
When you open Epical from an installed app, the pages you have read from your appointments, messages, documents, records, care team, lab results and measures are kept on that device so they open without a network — along with the app's own files, never a picture from your records and never anything from the assistant. These copies stay on the device, are never uploaded, and are deleted when you sign out, when you press "Clear saved pages" — on the offline page or in Settings — or after thirty days without opening the app. Anyone holding the device unlocked can read what is kept there.
Cookies
Two cookies, both first-party. epical_web_session keeps you signed in: signed,
httpOnly, SameSite=Lax, and good for thirty days. epical_rail remembers
whether you folded the navigation rail: SameSite=Lax, Secure where the page
is served over HTTPS, and good for a year.
Nothing else is kept in your browser, except three small things the app writes
itself and never sends anywhere. A question typed on the dashboard travels to
the chat pane in that tab's sessionStorage, and reading it deletes it. A
marker there also stops a page whose files a deploy replaced from reloading
itself twice. And one localStorage key says whether the keyboard-shortcut
hints are showing — true or false, nothing more. The theme follows your
system's light or dark preference. The offline copy described in the section
above is the only other thing on the device, and only where the app is
installed.
Your controls
- Delete a record, a document or a note.
- Disconnect a connection, which deletes its stored token.
- Rotate a calendar feed's link, which retires the old one.
- Download your documents as a ZIP.
- Clear the copies of your records saved on this device, in Settings.
- Delete the account in Settings, and every row it owns goes with it.
Changes
This policy changes when the app does, and the date at the top of the page
changes with it. Write to [email protected] with any question about it.
Last updated .