What BiomeBench does not collect

No page on this site asks for a name, email address, postal address, telephone number, institution, or any identifier of a person. There are no accounts to register and no profiles to complete, because there is nowhere for that information to go.

No calculator, planner, inventory, or reference-table screen transmits what you type. Inputs are read by JavaScript running in your own browser, and the result is written back to the same page.

What your browser’s local storage holds

When you deliberately save something, it is written to your browser’s own storage for this site, under keys whose names begin with biomebench-. Nothing in this list is sent to a server, and nothing here is shared between browsers, devices, or people using the same site.

  • biomebench-planner-v1 and biomebench-planner-v2 — the plate layouts and workspace you are building.
  • biomebench-inventory-v1 — your reagent ledger, including the free-text names and notes you write yourself.
  • biomebench-experiment-v1 — results you choose to capture, each with its tool, value, unit, label, and any experiment facts you attach.
  • biomebench-preparations-v1 and biomebench-run-history-v1 — saved preparations and the record of runs you keep.
  • biomebench-pcr-workflow-v1 — PCR workflow setup carried between calculators.
  • biomebench-audit-history-v1 — a local change history for your own records. It contains no network metadata and is not telemetry.
  • bb-theme — your light or dark display preference.

Calculation inputs specifically

Sample numbers, concentrations, volumes, dilution factors, plate assignments, and anything you derive from them are processed in the page and discarded when you close or reload it, unless you used a save action above.

The site carries a small internal event mechanism that exists so a future analytics provider could be attached without touching calculator code. Today no provider is attached to it, so nothing is reported anywhere. By design it can carry only an event name and which tool was used; the values you entered are outside what it is able to represent.

Deleting what your browser stored

Delete an individual entry from inside the planner, inventory, or experiment surfaces, or clear site data for this domain in your browser settings — that removes everything the site has on your device at once. Your saved layouts and ledger are gone with it and cannot be recovered, because no copy was held anywhere else.

Because the data was never on a BiomeBench server, there is no server-side record for anyone to delete on request. The control is in your browser.

Cookies

This site sets no cookies and uses no similar browser identifier. There is consequently no cookie banner and no consent prompt: there is nothing that needs consenting to.

Analytics and third-party requests

No analytics, advertising, or tracking script from any provider is loaded on any page.

Two things are still honest to state, because a static site is not an airgapped one. Stylesheets for the site’s typefaces are fetched from Google’s font infrastructure, which means that when a page loads, that request carries ordinary technical detail about your connection — an IP address among it. And the site is served through a content delivery network, which records request-level information about traffic it carries under its own terms.

The first could be removed by self-hosting the fonts. That has deliberately not been done yet, so this page describes the site as it runs rather than as it could run.

Hosting and request logs

BiomeBench’s own application code writes no logs about you. It has no database, no session store, and no user table to write to.

The infrastructure that delivers the files to you is a separate layer, operated by a hosting provider, and any records it keeps are governed by that provider rather than by this codebase. This page will not pretend otherwise.

The site’s one API endpoint

A deployment check lives at /api/health. It answers with fixed strings describing the service and its version, takes no request body, accepts no input to store, and writes nothing. It exists so an operator can tell whether the deployment is up.

Retention

Nothing you enter is retained by BiomeBench, so there is no retention period to quote for it. What you save to your browser persists there until you delete it or your browser clears it. If you use a private or ephemeral browsing session, it disappears with the session.

Your rights and choices

The practical rights here are access, correction, and deletion, and they are all exercisable on your own device: everything the site holds about you is readable in, editable through, and deletable from your browser’s storage for this domain.

Whether any particular law gives you further rights against this site depends on where you are and on facts the repository does not record. This page makes no claim about any jurisdiction’s statutes, and it should not be read as legal advice about them.

Changes to this policy

This page ships with the site, so it changes when the implementation changes. If a future version adds analytics, an account system, a form that sends something somewhere, or self-hosted fonts, the sentences above are expected to change with it — and if they have not, that is a defect worth reporting.

Privacy questions

The Contact page explains how to reach the project and what to include. It is worth being straight about one thing first: no contact address is published for this site yet, and because the site holds nothing about you on a server, a privacy request has no record to act on. If you are asking because of something the site does rather than something it stores, that is exactly the kind of report the project wants.