Like most websites, hosting and CDN providers may process basic technical request data such as IP address, user agent, request path, and timestamps to deliver the site and protect it from abuse.
Privacy
Most browsing still happens without an account, but optional email signup now exists.
Most interaction data used for recipe recommendations still stays in your browser. If you choose to join the meal-plan or newsletter list, the site also stores your email signup details server-side so it can remember that subscription.
What data exists today
Current data categories
Recipe recommendation impressions and clicks are stored in localStorage on your device so the site can adapt recommendation ordering locally when enough evidence exists.
If you opt into the meal-plan or newsletter list, the site stores your email address plus basic signup metadata such as source page, selected offer, signup time, and basic delivery state for welcome emails or unsubscribe handling.
Browser-local storage keys
What the current front-end stores
The current front end uses localStorage and sessionStorage keys such as lk-recommendation-events-v1, lk-recommendation-session-v1, lk-growth-events-v1, and lk-acquisition-context-v1, plus per-session impression markers, to keep recommendations adaptive and product instrumentation local-first.
These values stay in your browser unless you clear site data or export them manually from your own device.
Improve related-recipe ordering and inspect product behaviour without introducing a full backend before launch.
The current event logs keep the most recent 600 recommendation events and 300 product-insight events in browser storage, trimming older entries automatically.
You can clear browser storage at any time through your browser settings or by clearing site data for this domain.
Third-party services
Current service dependencies
The site runs on Vercel. That means basic site delivery, CDN caching, deployment logs, and private Blob-backed email signup storage are handled through that infrastructure. If welcome emails are enabled, email delivery will also depend on the configured sending provider for that environment.
The site does not currently embed advertising networks, remarketing tags, or marketing automation widgets in the shipped front end.
The current site relies on essential first-party browser storage for core behaviour. If external analytics, marketing tags or accounts are added later, this notice should change with them.
If the product changes later
What should stay transparent
Read how recipes are selected, what evidence-minded means here, and what the site does not claim to be.
StandardsRead the editorial rulesSee how recipes are chosen, how claims are framed, and what kinds of gimmicks this site is trying to avoid.
DirectoryUse the site without an accountYou can browse, filter, and read recipes without creating a profile or providing a payment method.
TransparencyThis notice should evolve with the productIf accounts, richer email tooling, or external analytics are added later, this page should be updated to reflect that clearly.