Last updated: October 24, 2026
Your recipes never leave your device. All calculation and label rendering happens in your browser. We do not receive, upload or store your ingredient lists, your recipes or your labels.
Nothing about your recipes. For a purchase, our payment processor (Creem) collects what it needs to take payment and pay us. We receive your email address only so we can send your license key.
When you activate a key — and during occasional automatic re-checks — the key is sent to our server. Lifetime keys are verified there by signature (the signing secret never leaves the server); keys issued by Creem are validated by Creem. The request is processed and discarded: we do not log keys and keep no activation database. Your key is stored in your browser's local storage.
Saved recipes are stored in your browser's local storage on your own machine. They are never synced to us and are cleared if you clear your browser data.
We do not set advertising cookies and do not run advertising or cross-site trackers. To count page views we use Cloudflare Web Analytics, which is cookieless by design: it stores no cookies and no local storage, does not fingerprint visitors by IP address or user agent, and the data is never used for advertising or sold. It reports aggregate facts only — pages viewed, referrer, country, browser and device type.
Payments are handled by Creem (creem.io), which acts as merchant of record. The site is hosted on Cloudflare Pages, and page-view analytics are provided by Cloudflare Web Analytics (cloudflare.com). Scripting libraries are loaded from jsDelivr's public CDN. Nutrition data comes from USDA FoodData Central, which is public domain and is bundled into the app rather than fetched at runtime.