Privacy
Canotto Lab, last updated 9 September 2026.
The short version: nothing is collected. Your recipes and bakes stay in your browser unless you choose to sync them, and when you do they go to your own Google account rather than to us. We do not count you, profile you, or hold a record of you anywhere. We do not sell anything, and there is nothing to sell.
What stays on your device
Everything you make is stored in your browser and goes nowhere else: recipes, bake logs, schedules, scores, notes, equipment, and settings. There is no account to create, and none of it is ever sent to us. Clearing your browser data deletes all of this, which is why the app offers a JSON download.
These are the only things written to your browser's storage:
| Key | What it holds |
|---|---|
canotto-lab/v1 | Your recipes, bakes and settings |
canotto-lab/theme | Light, dark, or match my device |
canotto-lab/drive-connected | Present only if you connected a Google account |
canotto-lab/drive-file-id | Which file in your own account holds your library |
canotto-lab/drive-account | The address of the connected account, so the app can tell you which one it is after a reload without asking Google again |
canotto-lab/drive-last-sync | What the last sync did and when, so the result stays on screen instead of vanishing with a notification |
canotto-lab/drive-token | The key Google issued for your own account, kept for the life of the tab so a reload does not need another one. In session storage, so closing the tab discards it. Google expires it after about an hour regardless. |
Photographs you attach to a bake are kept in this browser too, in IndexedDB rather than the list above, because a single photograph is larger than everything else here put together. They are scaled down and re-encoded before they are stored.
If you connect a Google account they go there as well, each as its own file in the same hidden folder as the rest, which is how they reach your other devices. They still never come to us: we have nowhere to put them and no way to read them. They are not in the JSON export, which stays small and readable. Removing a photograph deletes it here and from that folder on the next sync, and deleting a bake takes its photographs with it.
No cookies are set by this app, for tracking or anything else.
If you connect a Google account
Sync is optional and off unless you turn it on. If you do, the app asks Google for one narrow permission, drive.appdata: a hidden folder that only this app can see. It cannot see, list or touch any other file in your Drive, and Google's own consent screen says so.
Your library, and the bake you have in progress, then go straight from your browser to your Google account. Nothing we run sits in between, and none of it touches the one database we keep. We cannot read it. You can delete it from the Setup screen, or revoke the app entirely in your Google account settings.
The app also reads your email address, for one reason: to show you which account is connected, on your own screen, so you are not left guessing when you use two. It is kept in this browser so the app can still tell you after a reload, it is never sent to us, and disconnecting deletes it.
Signing in is something you start. The app never asks Google for anything because a page loaded; it asks when you press sync, and Google may briefly show its own window then to hand over a fresh key. That key is kept for as long as the tab is open and is discarded when you close it. It is never sent to us, and there is no long-lived credential behind it: Google does not issue one to a page like this, which is why an hour is the most any of it lasts.
What we never do
- No advertising, and no advertising identifiers.
- No third-party analytics. No Google Analytics, no Firebase Analytics, no tag manager, no pixels.
- No selling, renting or sharing of anything, to anyone, for any purpose.
- No profiles, no behavioural records, no mailing list. We have no way to contact you and no wish to.
- Nothing you make is ever sent to us. Not a recipe, a bake, a score or a note. There is nowhere for it to go: the app writes to no service of ours at all.
- No counting. Not how many people use this, not how often, not from where. We genuinely do not know, and have chosen not to.
Requests that reach Google
The app is a static page, but loading any page on the internet means contacting whoever serves it. In the interest of stating this accurately rather than comfortably:
- The site is hosted on Firebase Hosting, which is Google. Like every web host, their request logs record IP addresses. We do not read those logs and cannot use them to identify anyone.
- The page loads its typefaces from Google Fonts, so Google sees your IP address when the page loads. That is Google's collection, not ours, and it is governed by Google's own privacy policy.
- If you connect an account, Google handles the sign-in and holds the file.
This page you are reading now makes no external request of any kind.
Children
This is a tool for making pizza dough. It is not directed at children and collects nothing that could identify anyone of any age.
Changes
If what the app does ever changes, this page changes with it in the same commit. The app is open source and has no build step, so the code running in your browser is the same text as the source, and the claims here can be checked rather than taken on trust. Optional sync is in src/lib/drive.js, and it is the only part of the app that talks to anything at all.