Wine Cellar — Privacy Policy
Wine Cellar runs entirely in your browser. This page sets out exactly what data exists, where it goes, and who can see it.
What the App Stores
Only what you type in: for each wine its vintage, name, colour, region, grape, bottle count, value, drinking window, where it is kept, where it came from, the day it was added and any notes; for each bottle you mark as opened, the day, your rating and a short note — plus your settings, your colour theme and which tab you had open. There is no profile and no usage tracking of any kind. No account is needed to use the app.
Where That Data Lives
In your browser (always). Everything is stored in your browser's local storage on your own device. If you never sign in, this is the only copy that exists — none of your data is ever transmitted anywhere. Clearing the site's browser data deletes it, which is why the app offers a JSON backup you can keep yourself.
A copy of the app itself, so it opens offline. The page, its stylesheet and its icons are kept on your device — the same public files anyone can read on GitHub, and nothing else. Your wines are never put there.
Google sign-in / Firestore (optional, off until you choose it). If you press “Sign In to Sync”, your cellar is stored in a Firebase/Firestore database operated by the developer so the same data appears on your other devices, and Firebase Authentication records your Google account's email address and display name. Security rules confine every account to its own document — no other signed-in user can read yours. This only ever happens if you sign in; the app never does it on its own.
Backups you download. “Download Backup” writes a JSON file straight to your device. It is never uploaded, and where it goes afterwards is up to you. It contains everything the app holds, in plain readable text.
Read-only links you create (optional). “Share” builds a link containing
the wines you pick — and, only if you tick the boxes, their notes and locations and your
opened bottles. That data is packed into the link itself, after the
# — the part of a web address a browser never sends to any server. Nothing is
uploaded and nothing identifying travels. A link is a frozen snapshot and
cannot be withdrawn once sent. Opening someone else's link never alters
the data saved in your own browser.
What Is Never Collected
- No analytics, no advertising, no third-party trackers, no cookies for tracking.
- No location data — “where it is” is just words you typed.
- No contacts, no photos, no device identifiers.
- Nothing is sold or shared with anyone, in any circumstances.
Third Parties
Your cellar reaches Google Firebase (Authentication and Firestore) if, and only if, you sign in. Their handling of that data is covered by Firebase's privacy documentation.
Google's code is fetched only when you ask for it. Nothing of Google's
loads on an ordinary visit. The Firebase and sign-in scripts come from
www.gstatic.com and accounts.google.com the moment you reach for
the “Sign In to Sync” button — pointer, keyboard or press — and not before. The one
exception: if you are already signed in on this device, the app loads
Firebase as the page opens, because asking Firebase whether your session is still good is
the only way to find out. It knows to do that from a note kept in your own browser and
rewritten every time your sign-in state changes, so signing out stops the requests
too.
When those requests happen they tell Google your IP address, your browser's user-agent and which page asked — the ordinary information any request carries. None of your wines goes with them. The page itself is served by GitHub Pages, which sees the same ordinary request information involved in serving any page.
Deleting Your Data
Signed out: clear this site's data in your browser, and it is gone. Signed in: “Delete All Data” in the Back Up window clears the stored copy too. To have the whole stored document deleted, email eagleadams86@gmail.com from the Google account you signed in with, and it will be removed.
Changes
If what the app stores or where it sends it ever changes, this page and its effective date change in the same release.