Privacy policy

Last updated 2026-11-15.

Who we are

MedaRep is run by MedaRep LLC, a Florida limited liability company, 3939 NW 34th Place, Gainesville, FL 32606 (“we”). This policy covers two groups of people: visitors and subscribers who use the site, and the physicians and other clinicians the site describes.

What we collect from you

Cookies. A random visitor ID (ti_sid) that counts the profiles you open against your plan’s limits; a sign-in cookie once you sign in; and your choice of Basic or Advanced view (ti_mode). All are first-party and needed for the site to work. We set no advertising or third-party analytics cookies.
Your account. Your email address and, if you give one, your name. Sign-in is by emailed link or code, or by a passkey: for a passkey we keep its public key, never anything that could sign in as you. Your plan, its states and procedure categories, and your team if you are on one.
Billing. Stripe takes payment. We never see or store card numbers; we keep the Stripe customer ID and what your subscription covers.
What you add. Saved territories, lists and their notes, the customers you mark (and when you unmark one), the lines you sell, your account record (visits, where each account stands, follow-ups), territory reports you ask for, and whether you said a case figure looks right. A note that looks like it holds patient information is refused, on the site and through an assistant (compliance guide).
How you use the site. Which surgeon, practice and facility pages you opened and when, and your exports, to apply your plan’s limits. A daily count of the kinds of page you open (the kind, and the state and procedure family it showed, not which surgeon or place), to see what the site is used for.
AI assistant connections. When you connect an assistant we keep the connection and its access tokens, and a log of its calls (which tool, when, and whether it worked; surgeon names and your notes are left out) for 90 days.
Security records. Our servers keep request logs (network address, time, page) for security and to fix errors, for 30 days; error reports leave out cookies and search terms. When an account is created we keep a one-way keyed hash of the network address and of the email address for 24 hours, to limit sign-ups from one network. Signed out, your network address picks the state a ranking opens on, from a database on our own server; the address is not stored for it.

How we use it

To run the service you signed up for: show your territories and plan, apply its limits, bill you, send the emails you ask for (the weekly email is off until you turn it on, and every one has an unsubscribe link), answer you when you write, and keep the site secure and working.
We do not sell or rent personal information, share it for advertising, or let any outside service train a model on it. What you tell us about a figure (for example, that a case count looks too high) is seen only by you. Before any of it is used to improve the estimates, it will be stripped of who said it, and a figure drawn from it will show only when three or more people at two or more companies contributed.

Who sees it

Your team. On a team, teammates see what the team shares: customers, lines, lists and account records, at each person’s plan.
Services that work for us, each only for what it does for MedaRep:
  • Hostinger. Hosts the servers and databases the site runs on, in its Boston, Massachusetts data center in the United States.
  • Backblaze. Keeps the off-site copies of our database backups, which include account records, for up to 90 days, in its US East region in the United States. Each copy is encrypted on our servers before it leaves them, with a key Backblaze does not have.
  • Stripe. Takes payment and runs subscriptions. Card details go to Stripe directly; we keep the Stripe customer ID and what the subscription covers.
  • Resend. Sends sign-in emails, team invitations and the weekly email: your address and the message.
  • Ollama. Runs the AI model that writes territory reports. It gets the public figures a report draws on and, where a section uses them, the lines you sell and the customers you marked. Ollama's terms say it does not use what it is sent to train models, and its privacy policy that it keeps it no longer than answering takes. It runs the model mainly in the United States and may use Europe for extra capacity.
  • HubSpot. Only if you connect your own HubSpot account: the customers, statuses and visits you choose to sync go to your portal, under your agreement with HubSpot.
  • Your AI assistant. Only if you connect Claude, ChatGPT, Gemini or another assistant: the answers you ask it for go to that service, under your agreement with it.
When the law requires it, such as a valid subpoena, or to protect the site and its users from fraud or abuse. If MedaRep LLC is sold or merged, your information moves with the service under this policy, and we will tell you first.

Physicians and clinicians

What the site shows about a clinician comes from the public sources on the data sources page: the NPI registry, Medicare enrollment, the Medicare procedure counts CMS publishes, the industry payments manufacturers report under the Sunshine Act, FDA records and published research. These records describe professional activity; no patient information is used or shown.
Some figures are our estimates, such as volume below CMS’s publishing threshold, non-Medicare cases and forecasts, and whether a practice is independent or employed. They are labelled as estimates, and how they are made is public.
A clinician can ask us to correct an error or explain how a figure was made at privacy@medarep.com. We answer within 30 days. Where an error is in the federal source, we point to where it is fixed (NPPES for addresses, PECOS for enrollment, Open Payments for payments), and the fix reaches the site at our next refresh.
Because these records are public by law, we do not remove a clinician’s records or the estimates built from them on request. An estimate is not left standing when it is shown to be wrong, though: if a clinician tells us, for example, that they have stopped a procedure, moved, or changed practice, we check it and correct or remove that estimate.

Keeping and deleting

Delete your account in Settings: the account goes at once with everything it holds (territories, lists, notes, customers, lines, account records, reports and usage). What you set for a team (its lists, customers, lines and account records) stays with the team, shown as a former member’s. A team’s owner deletes the team or hands it on first.
While an account is open we keep what you add until you delete it. Signed out, what is held against your visitor ID is kept for 13 months from your last visit. Backups, on our servers and off site, roll over within 90 days, so a deletion reaches them by then. Stripe keeps payment records as tax law requires.
To have us delete or send you what we hold, write to privacy@medarep.com.

Security

The site is served only over HTTPS. There are no passwords to steal: sign-in is by emailed link or code, or a passkey on your device. A connected assistant can be disconnected from Settings, and other signed-in devices signed out. Each subscriber’s records are kept apart in the database, so one account cannot read another’s. Report a security problem to spd@medarep.com.

Your rights

You can see, correct, export and delete your information, most of it from Settings and the rest by writing to privacy@medarep.com. We answer within 30 days and will not treat you differently for asking.
State privacy laws. Depending on where you live (for example California, Colorado, Connecticut, Virginia or Texas), you may have the right to know what personal information we hold and how we use it, to get a copy, to correct it, to delete it, and to opt out of its sale, of its sharing for targeted advertising, and of profiling for decisions with legal or similarly significant effects. We do not sell subscribers’ information, share it for targeted advertising, or use it for such profiling, and we treat a Global Privacy Control signal from your browser as an opt-out. You, or an agent you authorise in writing, can make a request at privacy@medarep.com; we confirm it is you from the account’s email address before we act. If we decline a request, you can appeal by replying to our answer, and we answer the appeal within 60 days.
Our servers, and the services above, keep information in the United States, except that Ollama may run a report in Europe as described above. MedaRep is for working professionals and is not meant for anyone under 18.

Changes and contact

We will post changes here with a new date, and email subscribers before a material change takes effect. Questions and requests: privacy@medarep.com, or by post to MedaRep LLC, 3939 NW 34th Place, Gainesville, FL 32606.