Privacy.

What we collect, what we do with it, and what we are not going to claim. This page describes how the beta behaves today; if that changes, this page changes first.

Last updated 18 October 2026.

What this website collects

There is no form on this site. Requesting an invite opens an email in your own mail app, addressed to us. Nothing is typed into a page here and nothing is sent from one. There is no account, no database behind these pages, and no cookies.

One thing did change. This site now sends anonymous usage counts — a count is the name of something that happened and nothing else — and you can turn them off in the footer of any page. Until recently this section said the site collected nothing at all. That stopped being true when counting was added, so the section was rewritten rather than left standing.

What we end up holding is an email you chose to send us, sitting in our mailbox. We use it to reply to you and to decide who to invite next. There is no newsletter and no list. We do not pass it to insurers, brokers or employers. Ask us to delete it, by replying to anything we send, and we will.

These pages are static. Fonts are served from our own origin rather than a third party, so loading this page does not tell anyone else that you read it.

Usage counts

We count how often a few named things happen, so we can tell whether the thing works at all. A count is a name and nothing else. There is no field for anything you typed, because the message we send has exactly three parts: the name below, which site it came from, and a random number your browser made up for itself.

This is the complete list for this website. There is no other list.

  • marketing_home_viewed
  • marketing_how_viewed
  • marketing_sample_viewed
  • marketing_privacy_viewed
  • marketing_terms_viewed
  • marketing_invite_clicked

What is not in a count: your email address, your IP address, anything you typed anywhere, which pages you viewed in what order, how long you stayed, what browser or device you are on, and where you came from. The random number is used to stop one browser inflating a total and is then thrown away — it is never written down, so there is no way to join two counts together and call it a person.

What we keep is a tally: a date, a name from that list, and how many times it happened that day. Nothing else fits in the table.

It is on unless you turn it off, and the switch is in the footer of every page. Turning it off also forgets the random number. If your browser blocks storage, nothing is counted at all.

Inside the product

Beeshur itself is a beta at app.beeshur.com, behind Google sign-in and an allowlist. Inside it:

  • You type the plan numbers in. Premium, deductible, coinsurance, out-of-pocket max, and a few yes/no answers about each plan. We do not connect to your insurer, your employer, your bank or your pharmacy. The comparison works from what you type and nothing else.
  • There is no way to add an explanation of benefits or a claim to your account. The comparison holds plan numbers and nothing else. Keeping track of bills and explanations of benefits is where Beeshur is going, and the first version of it is a separate app that runs on your own device: it has no account, it is not connected to this one, and nothing you type into it is sent to us or stored on our server. It is described where it lives, not here, because this page is about what the comparison holds.
  • Nothing you type into the plan form is sent to any AI provider. All the cost arithmetic runs in deterministic code on Beeshur’s own server.
  • Your inputs are stored against your account only, and you can delete them any time. A comparison is not shared with other users.
  • Removing an email from the allowlist ends access on that account’s next request.
  1. Youplan numbers
  2. Beeshur’s serverdeterministic arithmetic
  3. Outside AIoff by default
  • The plan numbers you type are stored against your account and nowhere else.
  • No model is involved in the cost arithmetic; it is plain, deterministic code.
  • The dashed path is the plan-document upload. It is off by default and not part of the beta, so nothing you do today goes through it.

Document upload

There is a plan-document upload path in the product: a PDF of a plan summary, not a bill, a claim or an explanation of benefits. It is off by default and not part of the beta, so nothing you do today goes through it. This is what it does where it is switched on, and it is worth reading before you ever use it, because one step sends text off our server:

  • The PDF’s text layer is read on Beeshur’s own server. The file is held in memory while it is read and is not stored. Scanned or image-only PDFs are rejected; there is no character recognition.
  • Only the pages carrying the standard plan-summary headings are kept, at most eight of them, and that text is scanned for member IDs, dates of birth, Social Security numbers, labelled names and email addresses. If anything matches, the upload is rejected and nothing is sent.
  • The kept text is then sent to Anthropic, an outside AI provider, to read the plan’s field values out of it. The PDF itself is never sent. We cannot verify or control what happens to that text on their side, and we make no claim about it beyond what their own published retention policy says.
  • Every value comes back with the quote it was read from, and you confirm or change each one before it is used. Blanks stay blank.
  • Those unconfirmed values and quotes are stored as a draft on our server until you use them or discard them. A draft you abandon is marked to expire a day after upload and is deleted the next time it is opened after that. There is no scheduled cleanup yet, so an abandoned draft can sit in the database until something opens it again.

The scan reduces the chance that identifying details leave our server. It does not remove all of them, and we are not going to tell you it does. The upload page in the product carries the full version of this statement, including what Beeshur does and does not claim about health-information rules; read that one before you upload anything.

What we are not claiming

We are a small beta. We are not going to put a compliance badge on this page, and we are not going to tell you our security is bank-grade, that no machine ever reads anything, or that every trace of your data disappears the moment you close the tab. Those are the sentences that get written when the honest version is unimpressive.

The honest version: this website holds nothing at all, a comparison inside the product is visible only to the account that created it, you can delete one, and the one path that would send text to an outside company is switched off and described above. Everything beyond that is ordinary infrastructure, run carefully, by people who can still make mistakes.

Asking us something

Write to privacy@beeshur.com to ask what we hold, to have it deleted, or to tell us this page is out of date. A person reads it.

Related: Terms and what the comparison does and does not model.