Privacy Policy
Last updated October 12, 2026
Vemri is built on one hard rule: we never collect, store, or process patient-identifying data. This policy explains the limited information we do handle to run your subscription and the app, and how the content you write is kept to procedure-level material that never identifies a patient.
The one thing to know first
Vemri is not a HIPAA Business Associate and is architected to stay that way. Our servers do not receive, store, or transmit Protected Health Information (PHI). Vemri keeps your case log, and it holds only procedure-level content (technique, steps, attending pearls, plans, templates) — never patient names, MRNs, dates of birth, or clinical history tied to a person. See our Security & PHI page for the technical detail.
Information we collect
Account & billing
- Your email address and display name.
- Your training context — post-graduate year (PGY), specialty, and the names of your attendings and hospital locations. These are procedure-level metadata you enter to organize your own case log; they are not patient data.
- A Stripe customer identifier and subscription status. Your card details are handled entirely by Stripe — Vemri never sees or stores them.
Your case log
The procedure-level content you write in Vemri: cases (procedure, attending, site, date of the case, CPT codes), pre-op plans, op-notes assembled from already-redacted dictation, pearls, techniques, playbooks and their layout. It is stored in our database, encrypted at rest, and readable only by your account unless you choose to share something (see below). Free text you write passes an automated redaction step before it is saved.
Case images
Images you add (X-rays, OR photos, diagrams) are de-identified in your browser before upload: file metadata is stripped, overlay text such as names, MRNs and dates is removed, and you confirm the image is clean. Our server checks again and rejects anything that still carries metadata or overlay text. Only the cleaned image is stored. Images are never sent to our AI provider, never used in analytics, and never included in a share link or the program feed. An attending you invite to their case log sees the images on the cases you share with them.
Usage analytics
We record privacy-preserving, count-only events (for example, that a brief was opened or a review was completed) to understand product usage. These events never contain your case content, your Notion content, patient data, or the text of anything you capture.
What we do NOT collect
- No patient identifiers of any kind — in any field, form, upload, or prompt.
- Nothing read from your Notion workspace. Reads flow through a pass-through proxy that never logs, caches, or persists them (see Security).
- No card or bank details (handled by Stripe).
Sharing is your choice
Nothing you write is visible to anyone else unless you share it. You can send a pre-op plan to an attending by email link, share a pearl or technique with your program, or make a share link to a technique, playbook or case. Share links and the program feed carry procedure-level content only, never images, and you can revoke a link or stop sharing at any time. If you invite an attending to their case log, they see the cases you share with them (including their images and follow-up notes), and you can remove their access at any time. Program admins manage the roster of attendings and sites; they cannot open your cases, notes or playbooks. To troubleshoot, the Vemri operator can view an account read-only; every view is logged, and nothing is changed.
Notion (optional)
Notion is optional. If you connect your own workspace, Vemri mirrors your case log into it. When the app reads from your Notion workspace, the request passes through a Vemri proxy that forwards the bytes from Notion back to your browser and never logs, caches, or stores the response. A small, allow-listed set of write operations create or refresh structural and procedure-level content in your own workspace (your case-log setup, a procedure template, your settings-derived configuration, and the mirrored copy of your case log). We do not read your Notion content on the server for any other purpose.
AI features
A closed set of optional, procedure-level workflows can send de-identified text to our AI provider (Anthropic) to help draft templates and structure your own notes. Every such call runs through an automated redaction step first, is gated behind a feature flag, and writes only a metadata-only audit record (token counts and timing) — never the prompt or response content, and never patient data.
Sub-processors
We rely on these vendors to operate Vemri:
- Supabase — authentication and our application database.
- Vercel — application hosting.
- Stripe — subscription billing and payment processing.
- Resend — transactional and opt-in email.
- Anthropic — the AI provider for the de-identified workflows above.
- Notion — only if you connect your own workspace, as a mirror of your case log.
Data retention
We keep your account, subscription records and case log for as long as your account is active. Deleting an image erases it; it is not kept in a hidden archive. When you close your account we cancel your subscription and delete your case log, images and other Vemri records (billing records we are required to keep are retained as the law requires). If you connected Notion, your workspace and the mirrored copy in it remain yours.
Your choices & rights
- Access & export. Your case log is yours. You can request a copy of it at any time, and if you connect Notion you also keep a mirrored copy in your own workspace.
- Deletion. You can request deletion of your Vemri account and associated records at any time (see contact below).
- Email. Every non-essential email has one-click unsubscribe, and you can manage all notification preferences in Settings.
Cookies
We use essential cookies for authentication and to remember your timezone, plus privacy-preserving analytics. We do not sell your data or use third-party advertising trackers.
Changes
We may update this policy as the product evolves. Material changes will be reflected by the “last updated” date above.
Contact
Questions about privacy or a data request? Email rserbin15@gmail.com.