Privacy Policy

What BevFacts knows about you — which is, by design, nothing.

Current version

The short version: BevFacts has no accounts, no tracking pixels, no analytics, no ads, and no server of ours receiving your data. Every label is computed inside your browser. The only place your drink data lives is in the page URL — and it only goes where you choose to send that URL.

1. What we collect

Nothing, directly. The BevFacts site is a static application: there is no sign-up, no login, no form that submits to us, and no BevFacts-operated backend receiving requests. We do not use analytics services, advertising identifiers, fingerprinting, or tracking pixels of any kind.

2. Where your drink data lives

When you build a drink, the label state (drink name, nutrition values, modifiers, optional cup settings) is encoded into the page URL fragment — the part after #. Two properties of fragments matter for privacy:

Browsers do not send URL fragments to web servers. Your drink state is not transmitted to us or to our host when the page loads.
If you share a link or print a QR code, everything needed to reconstruct that label travels inside it. Share links the way you would share their contents.

The app does not use cookies, localStorage, or sessionStorage. Closing the tab discards everything except URLs you saved yourself.

3. Hosting

The site is served by GitHub Pages. Like any web host, GitHub may log basic technical request data (such as IP addresses) for security and operational purposes, governed by the GitHub General Privacy Statement. We do not receive or have access to these logs in any per-visitor form.

4. Exports and printing

PNG downloads and sticker printing are generated locally in your browser. The files are written to your device only; nothing is uploaded.

5. Children

The site is a general-audience informational tool. It collects no personal information from anyone, including children.

6. Future services

The technical documentation describes a draft hosted API (labels, cup deposits, webhooks). It is not live. If and when any hosted BevFacts service launches, it will ship with its own specific privacy policy before accepting a single request — and the cup-identity privacy rules in DBNF-1 Part 6 §6.6 (no PII in QR codes, anonymous returns, aggregate-only reporting) are binding design constraints on it.

7. Changes and contact

Changes to this policy are made in the open — the full history is visible in the public repository. Questions or concerns: open an issue there.