← Back to dashboard

Privacy Policy

Last updated: November 6, 2026

The short version

bodop reads health data from portals and lab results you already have access to (with the Chrome extension) and shows it back to you on this dashboard (by reading the Google Sheet you point us to). bodop never stores your biomarker values. They live only in your own Google Sheet. To read and analyze them, data passes transiently through our API to an inference provider that retains nothing — it’s never written to any database we control. That Sheet lives in your own Google Drive, which you own and control. Our servers only ever see your readings in transit, briefly, while processing a scan or answering a question you ask our AI advisor.

The profile details you choose to enter about yourself — date of birth, sex, a wellness goal, health conditions, diabetes status — live in that same Sheet too, not on our servers. What we do store is your account: email, name, a password hash, which Sheet is yours, and the connection to any wearable you link. Each is listed plainly below.

bodop sets only the cookies needed to keep you signed in. There are no advertising, analytics or tracking cookies, and nothing from another company loads when you open a page.

If you run a study in bodop and, at the end, choose to add your result to a group result, we store that one result — a single difference, not your readings — without linking it to your account. Section 2h explains exactly what that is.

1. Who we are

bodop ("we," "us," "our") provides a Chrome extension and web dashboard that help you collect and visualize your own health data. This policy explains what we collect, why, and what your rights are. It applies to the bodop Chrome extension and the bodop web application (this site).

2. Information we collect

a. Account information (stored on our servers, via Supabase)

  • Email address and a securely hashed password (we never see or store your plaintext password)
  • First and last name
  • Session tokens that keep you logged in

b. Profile information you choose to provide (stored in your own Google Sheet, NOT on our servers)

You can optionally enter: date of birth, sex, a wellness goal, health conditions you're managing, and whether you have diabetes or prediabetes. These are written to a “Your details” section on the Home tab of your own Google Sheet, where you can see and edit them, and are read from there each time they are needed. Date of birth, height and diabetes status are entered in the Chrome extension, which also keeps a copy in your browser so it can calculate age-based and diabetes-aware scores while scanning. They are used only to personalize the AI advisor's responses and dashboard calculations. We treat them as sensitive information — see Section 7 for your rights over them.

c. Your health data — biomarkers, lab values, scan results (NOT stored on our servers)

When you use the Chrome extension to scan a health portal, lab result page, or PDF, the extension reads the visible content of that page locally in your browser, sends the extracted text to an AI model to structure it into biomarker values, and writes the result directly to a Google Sheet in your own Google Drive — not to any database we control. When you view your dashboard, this web app reads that same Sheet directly from Google, on the fly, using your Google authorization. We do not copy, cache, or persist the contents of that Sheet on our servers at any point.

Some PDF pages are also sent as images. Reports laid out in columns or cards lose their meaning when flattened into a line of text — a number ends up next to the wrong label. When the extension detects that it has read a PDF page badly, it draws that page as a picture in your browser and sends the picture to the same AI provider to be read again. This happens only for PDFs, only for pages that did not read cleanly, and at most six pages per scan. It never happens for web pages.

We want to be direct about what this means, because it is more than the text we otherwise send. A picture of a page contains everything printed on that page — which can include your name, a medical record or patient number, your date of birth, your doctor’s or clinic’s name, and any images in the report. We cannot filter a picture the way we filter text, so we do not claim to. The picture is sent transiently, to be read and discarded, under the same terms as everything else in Section 3; it is never stored by us, and it is never written to your Sheet.

If you would rather this never happened, scanning your reports from your health portal in the browser rather than as PDF files avoids it entirely — the extension has no page image to draw in that case.

d. Google account access

To show your dashboard, we ask you to connect a Google account and select the one Google Sheet the extension created for you, using Google's file picker. We request the narrowest permission Google offers for this (drive.file scope) — this grants us access only to the specific file you select, not to search, list, or read anything else in your Google Drive. We do not request access to your Gmail, Calendar, Photos, or any other Google product.

e. Questions you ask our AI advisor

If you ask the AI advisor a question about a biomarker, your question, the relevant recent readings, and limited profile context read from your Sheet (sex, goal, conditions, and your age) are sent to our backend, forwarded to our AI processing provider to generate a response, and the response is returned to you. We do not log or store the content of these questions or answers.

f. How we use data from Google APIs (Chrome Web Store Limited Use)

bodop’s use and transfer of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Concretely, that means: the extension collects and transmits data only to the extent strictly necessary for its single disclosed purpose — reading the health results you point it at and writing them into your own Google Sheet. bodop ships no analytics, telemetry, advertising, crash reporting, or usage tracking of any kind — not in the extension, and not in this dashboard. We do not collect data for any unreleased future feature, we do not sell or transfer your data to third parties for advertising or creditworthiness purposes, and no human at bodop reads your health data.

g. Cookies, and what runs in your browser

bodop sets only the cookies needed to keep you signed in and to finish a connection you start. That means a sign-in session cookie for your Google sign-in, the sign-in cookies of our account provider (Supabase), and a short-lived security cookie when you connect a wearable such as Oura or Dexcom, which confirms that the reply came from the connection you started. There are no advertising, analytics or tracking cookies, and none set by other companies. Because every cookie bodop sets is strictly necessary for the service you asked for, there is no cookie banner: there is nothing to accept or decline.

Nothing from another company loads when you open a page — no tracking pixels, tags or analytics scripts. Our fonts and the report redactor’s PDF reader are served from bodop’s own site. Two things load from Google only when you click for them: Google’s file picker, when you choose your Sheet, and the beta feedback form, which is hosted by Google Forms. Google’s privacy policy applies to those.

Your browser’s own storage holds two things: study plans you choose to save for later in Studies, and the reference numbers of any studies you asked us to share (so you can see our decision). Neither is ever sent to us except as described in 2h.

h. Studies, and the optional group result

A study runs from your own Google Sheet: its plan, its schedule, your nightly answers and the result all live there. Two small records reach our servers, and neither contains your readings.

Glucose studies. If you use a FreeStyle Libre, you download your readings from Abbott’s LibreView site and choose the file in bodop. Your browser reads it there; only the readings from 30 minutes before to 3 hours after each of your study meals are written to the CGM Readings tab of your own Sheet. The file, including the name at its top, is never sent to us. If you use a Dexcom sensor, its readings arrive through your Dexcom connection and are written to the same tab, as with your other Dexcom data.

When you lock a study plan, we store a fingerprint of the plan (a scrambled code computed from it; the plan itself stays in your Sheet), a random number we draw to help pick your schedule, and the date. We do not store your account with it. To stop misuse, we also count how many plans each account locks per day; that count is deleted within a week.

When a study finishes, you may choose to add your result to the group. It is off unless you click “Add my result.” If you do, we store: which study it was (including the measure and the device), your result as one number (the difference the study found between the treatment and the control, or in a group study, your change), how precise that number is, which assignment you had, your plan’s fingerprint (so one plan can only count once), and the date. It is a health number derived from your data, so we treat it as health information. We do not link it to your account, your name or your email. As described under server logs below, our hosting provider’s standard request logs briefly record that a request was made from your connection at that time.

Group figures are shown only once enough people have contributed that no single person’s result can be worked out: the group average appears at 5 people, the range a new person is likely to land in at 10, and how much people differ from one another at 20. Nobody, including us, is shown anyone else’s individual result.

If you ask us to share a study you designed, so that other people can run the same study, we store its protocol: the treatment, the control, the measure, the design and how often it’s done. Never your readings or your results. We do not store your account with it; to stop misuse we count how many requests each account makes per day, and that count is deleted within a week. We review each request. If we approve it, the protocol is shown to every signed-in bodop user under Community N-of-1, so don’t put anything in a study’s description you wouldn’t want others to read. Group results for community studies follow the same rules as above.

Because a contribution is not linked to your account, deleting your account does not remove it, and we cannot find it on our own. To have it deleted, send us the code in the “Plan Fingerprint” column of the Trials tab in your Sheet, and we will delete the matching result.

3. Third parties we share data with

We use a small number of service providers to operate bodop. None of them receive your data for any purpose beyond providing the specific service listed:

ProviderWhat they receivePurpose
GoogleOAuth identity, access to the one Sheet you selectSign-in and reading your health data Sheet
SupabaseAccount email, name, password hash, which Sheet is yours, and wearable connection tokens. From studies: plan fingerprints, daily counts that stop misuse, approved shared-study protocols, and — only if you opt in — one study result not linked to your account. No health readings.Account infrastructure and authentication
CerebrasYour advisor question + recent readings (webapp); extracted page text and, for PDF pages that did not read cleanly, images of those pages (extension) — transientlyAI processing to answer your question or structure your biomarkers
GroqExtracted page text and, for PDF pages that did not read cleanly, images of those pages (extension only), transientlyAlternate AI processing provider for the extension's scanning feature
VercelStandard web traffic/hosting logsHosting this web application

Both Groq and Cerebras state in their terms of service that data submitted through their commercial APIs is not used to train or fine-tune their models, and neither retains your inputs/outputs beyond what's operationally necessary to return a response.

For the extension's scanning feature, bodop provides API access to these AI providers by default — you do not need to create your own account with either one, and this traffic runs under bodop's account with that provider. If you'd prefer to use your own personal Groq or Cerebras API key instead, you can enter one in extension Settings; in that case, that traffic runs under your own account, not ours.

We do not sell your data. We do not share it with advertisers. We do not use it for marketing to third parties.

4. Data retention

  • Account information: retained until you delete your account.
  • Profile information (date of birth, sex, goal, conditions, diabetes status): never stored by us — kept in your own Google Sheet, and in the extension’s storage in your own browser, for as long as you choose.
  • Health data (biomarker readings): never stored by us — retained only in your own Google Sheet, for as long as you choose to keep it there.
  • Study plan fingerprints: kept so that a finished study can show it was planned before its data existed. Not linked to your account.
  • Group results you choose to contribute: kept for as long as the group result is offered, because the group figures depend on them. Not linked to your account; deleted on request if you send us the plan fingerprint (Section 2h).
  • AI advisor questions/answers: not retained; each request is processed and discarded.
  • Extension scan content: read locally, processed transiently, discarded after writing to your Sheet.
  • Server logs: retained briefly by our hosting provider on a short rolling window, then discarded. See below.

Server logs — what they contain, and one thing worth knowing

Like any website, bodop runs on a hosting provider (Vercel) that keeps standard web-server logs of requests made to it: the date and time, the address of the page requested, the response status, how long the request took, and technical details about the request such as IP address and browser user-agent.

These logs never contain your biomarker values. When you ask the AI advisor a question, your question and readings travel in the body of the request, which is not written to the logs — we have verified this against our own production logs, not just assumed it.

One thing we want to be upfront about: pages on this dashboard are addressed by the name of the marker you’re looking at — for example /dashboard/variable/ApoB or /dashboard/system/thyroid. Because logs record page addresses, they therefore record which markers and body systems you viewed, and when. They never record the values. We’d rather tell you this plainly than let you discover it: it is a normal consequence of how web addresses work, it applies to essentially every health app you use, and most privacy policies simply don’t mention it.

We do not use these logs for analytics, profiling, advertising, or tracking. bodop runs no analytics, telemetry, crash-reporting, or usage-tracking service of any kind — not on this website and not in the Chrome extension.

5. Security

We use industry-standard practices to protect account information: encrypted connections (TLS) for all traffic, hashed passwords, database-level access controls that restrict each account to its own data, and the minimum OAuth permissions needed for each feature. No system is perfectly secure, and we can't guarantee absolute security, but protecting your information — especially the invariant that your biomarker values are never stored in any database we control — is a core design constraint of this product.

6. Your choices

  • Edit or remove profile information — anytime, from your Account page, the extension’s settings, or directly in your Google Sheet.
  • Disconnect Google access — anytime, from your Google Account's third-party access settings. This immediately revokes our access to your Sheet.
  • Delete your account — from your Account page, or by emailing us (Section 9). This permanently removes your account, any wearable connection, and our record of which Sheet is yours from our systems. It does not delete your Google Sheet itself — that lives in your Drive and is yours to keep or delete. It also does not remove a group result you chose to contribute, because that result isn’t linked to your account; see Section 2h for how to have one deleted.
  • Your Google Sheet — you can share, export, or delete it at any time directly in Google Drive; it is entirely under your control.

7. Additional rights for specific states

Washington residents — My Health My Data Act

If you're a Washington resident, the categories of consumer health data we process are the profile information described in Section 2(b) and the biomarker data described in Section 2(c). We process both transiently and store neither: both live in your own Google Sheet. We collect this to provide the personalization and AI advisor features you request. We do not sell consumer health data, and we do not share it for advertising. You have the right to confirm whether we process your consumer health data, access it, and request deletion — contact us using Section 9 to exercise these rights.

California residents — CCPA/CPRA

California residents have the right to know what personal information we collect, request deletion, and opt out of the sale of personal information (we do not sell personal information). To exercise these rights, contact us using Section 9.

8. Children's privacy

bodop is not directed to, and we do not knowingly collect information from, anyone under 18. If you believe a minor has created an account, contact us and we will delete it.

9. Contact us

Questions about this policy, or want to exercise any right described above? Email bodop.app@gmail.com.

10. Changes to this policy

If we make material changes to this policy, we'll update the "Last updated" date above and, for significant changes, notify you directly.