Cookies & analytics
Necessary storage first. Analytics only when you choose it.
IvanEats uses a small amount of browser storage to keep the service working. Optional product analytics is separate and does not start until you allow it.
What counts as browser storage?
Websites can remember information using cookies, local storage, session storage and similar browser technologies. Some storage is needed for a feature you request, such as staying signed in, keeping an in-progress Kitchen request or remembering a setting. Analytics storage is optional.
Necessary storage
IvanEats uses necessary or functional browser storage for authentication, security, remembering your privacy choice and keeping Kitchen features consistent. These functions are available without analytics consent.
Supabase uses authentication cookies or equivalent secure storage to keep account sessions working. How long this storage remains depends on the authentication session. Clearing it may sign you out.
IvanEats uses first-party local storage to remember whether you accepted or rejected optional analytics. The choice remains until you clear site data or IvanEats needs to ask for a new consent choice.
First-party local storage can remember your serving preference, measurement system, diet setting, excluded ingredients and a short list of recently used or generated meal concepts. The recent-meal list helps Kitchen avoid repetition. This information remains until it is changed, replaced or you clear site data.
First-party session storage can temporarily keep the ingredients and meal settings in your current Kitchen workspace so they survive sign-in or a page reload. For signed-in users, the recipes from the current Kitchen request can also be kept in session storage so the results remain visible while that browser session continues. This temporary browser copy is separate from Recipe History, which is stored with your account.
Optional analytics storage
When you accept analytics, IvanEats uses PostHog to understand how the product is used. PostHog may create browser identifiers that help associate permitted usage events with the same browser. For signed-in users, analytics can also be linked to an internal IvanEats account ID.
Analytics is limited to product-use information such as pages viewed, feature activity, recipe slugs, counts and processing timings. We do not send your name, email address, ingredient text, generated recipe content or exact diet preference as analytics data.
Analytics storage remains until you withdraw analytics consent, clear the site data in your browser, or IvanEats resets it.
What happens when you reject analytics?
IvanEats continues to work normally. Optional analytics is not loaded, and activity from before consent is not saved and sent later if you change your mind.
Changing your mind
You can reopen Privacy settings from the footer or with the button below. If you withdraw analytics consent, IvanEats stops future optional analytics and clears the related local analytics identifiers it can access in your browser.
Withdrawing consent stops future analytics. It does not automatically erase analytics events already received. For a request concerning existing personal analytics data, contact contact@ivaneats.com.
Third-party content
Links to services such as YouTube open those services separately. Their own privacy and storage practices apply after you leave IvanEats. Simply having a link to another service does not give that service permission to run analytics on IvanEats.
Questions
For questions about browser storage or analytics, email contact@ivaneats.com.