Privacy Policy
Last updated: October 9, 2026
Almost everything on Crunchify.net happens on your device: the large majority of tools never send your input anywhere. A small number of shared and synced features do involve a server, and this page says exactly which, and exactly what is stored. There is no tracking or advertising anywhere on the site.
No tracking or analytics
We do not use any analytics services, advertising networks, or tracking pixels. There is no fingerprinting, and no third-party scripts that monitor your behavior.
Cookies
If you never sign in, this site sets no cookies. Signing in sets one cookie, __Host-crunchify_session,
which keeps you signed in. It holds a random session id and nothing else, it cannot be read
by the page's scripts, and it is sent only to crunchify.net itself. It expires 90 days after
you last used it, and signing out deletes it.
Most tools compute locally
Calculators, converters, encoders, generators and the rest run entirely in your browser. Input you provide to them is never sent to a server: it is processed locally and discarded when you leave the page, unless you choose to save it (see below). This is the default for every tool on the site.
The exceptions are the tools built around sharing with other people — currently the Grocery List, shared to-do lists, Recipe Box and Book Box. Those are covered in their own section below.
Local storage
Some tools (such as the Meal Planner and Timesheet) save data to your browser's local storage (IndexedDB) so your work persists between visits. This data never leaves your device unless you explicitly enable Google Drive sync or use one of the shared features below.
Shared features, and what the server stores
Grocery List, shared to-do lists, Recipe Box and Book Box can share data with other people. Using those features is optional and requires signing in. When you do, the following is stored on our servers: Cloudflare D1, and for Recipe Box and Book Box a server we run ourselves (see Hosting below).
- Your email address and an account identifier, so collaborators can see who is on a shared list.
- The content you share — list items, recipes, boards, comments, membership and invitations for the lists you take part in.
- Images you upload to Recipe Box.
- A usage record. Each request these features make to our API writes a row recording your account id, which tool and endpoint was called, and when. It exists to meter usage and stop one account overloading the service. It is not used for advertising or profiling, and it is not shared with anyone.
Content you publish through Recipe Box or Book Box is intended to be public and should be treated as such. If you never sign in, none of the above applies to you and nothing about you is stored on our server.
Optional Google Sign-In and Drive sync
Certain tools offer optional Google Sign-In to sync your data with Google Drive's App Data folder — a private, app-specific area of your Drive that is not visible in your regular Drive file list. Signing in is entirely optional and only affects tools that explicitly show a sync option.
Signing in asks Google for your name, email address and profile picture, and for access to that App Data folder. We use the access to read and write your tool data there, and nothing else: we do not access any other Drive files, contacts, email, or other Google services. Our server records your email address and an account identifier when you sign in, whichever feature you signed in for.
Google issues two tokens, and they are kept in different places:
- The access token, which expires after about an hour, is cached in your browser's local storage. The shared features send it to our server with each request, where it is checked with Google to learn who is asking, and not saved.
- The refresh token is held on our server, beside your session, so you stay signed in: when the access token expires, the server uses the refresh token to get a new one. It is never sent to your browser.
Signing out from the Account page asks Google to revoke the refresh token, deletes it and your session from our server, deletes the session cookie, and clears the access token from your browser.
Google's own privacy practices apply to the sign-in flow. See Google's Privacy Policy for details.
Hosting
The site is hosted on Cloudflare Pages, and the shared features above run on Cloudflare Workers with Cloudflare D1 for storage. Recipe Box's and Book Box's content and images are stored on a server we run ourselves, which is reached through Cloudflare. Cloudflare may collect server-level access logs (IP address, user agent, referring URL) as part of normal web server operation. See Cloudflare's Privacy Policy for details.
This site is vibe coded
The tools here, and this policy, were written largely by AI. We have tried to describe what the site actually does rather than what we would like it to do, but if you find something on this page that does not match the site's behaviour, please treat that as a bug and report it. Corrections are welcome and will be made.
Changes to this policy
If we make material changes to this policy, we will update the date at the top of this page. We do not send email, including about policy changes, so check this page if you have questions. The email address held for shared-feature accounts is used to identify collaborators to each other, not to contact you.
Contact
Questions about this policy? Open an issue on GitHub.