Privacy
Roast Reckoner — nothing leaves your browser
On Roast Reckoner —
Every number you put into the Roast Reckoner — the inputs, the arithmetic, and the result — lives in your browser's local storage on your machine. There is no server. There is no account. There is no analytics ping. There is nothing for us to leak.
The threat model most reckoners SaaS ignores
kitchen and food data is the kind that matters. It maps priorities, routines, and futures. In most tools in this category — web calculators festooned with ads, spreadsheet templates you paid for once and lost — that data lives in a database in a data centre, protected by whichever policy is currently in force at a company you have never met.
The safest calculation is the one that never entered a database in the first place.
How the file behaves on the wire
Load the Roast Reckoner once. Open dev tools. Watch the network tab. There is nothing there. The file makes no fetch, no analytics beacon, no font call, no telemetry. Once cached, it runs airplane-mode, forever.
The one exception is if you click a link that leaves the file. The file itself never leaves.
What "no account" actually buys you
No email to breach. No password to lose. No session to hijack. No support ticket where a stranger reads your calculation to help you.
The trade-off, honestly: we cannot recover your file for you. That is the shape of ownership.
What the Roast Reckoner does not do
- No cloud syncData stays on the machine you typed it into.
- No analyticsWe do not know you use it, or which field you fill first.
- No third-party fonts, scripts, or CDNsEvery asset is embedded. Airplane-mode works from the second open.
- No accountNothing to sign up for; nothing to log into; nothing to be locked out of.
Questions people ask
Where is my input stored?
In your browser's local storage on your machine. Export to JSON any time; it is plain text you can read.
Can Offline.Ltd see anything?
No. There is no back-channel. Not for support, not for improvements, not for anything. We built the file so this is architecturally impossible, not just policy.
What if my laptop is stolen?
Standard disk encryption on your OS is the correct answer, as for any private file. The Roast Reckoner does not add a separate password because the OS already does that job properly.
The most private calculation is the one that never enters a database in the first place.