Last updated: March 25, 2026
This Cookie Policy explains what cookies and similar tracking technologies we use on cookkar.com, why we use them, and how you can manage your preferences. Please also read our Privacy Policy for the full picture of how we handle your data.
Cookies are small text files that are placed on your device (computer, tablet, or smartphone) when you visit a website. They are widely used to make websites work correctly, to remember your preferences, and to provide information to website owners.
In addition to traditional cookies, we may also use similar tracking technologies such as:
Where we use the word "cookies" in this policy, we mean all of the above technologies unless we specify otherwise.
The following cookies are set by cookkar.com directly ("first-party cookies"):
| Cookie Name | Purpose | Duration | Type |
|---|---|---|---|
ph_* |
PostHog analytics — stores a pseudonymous visitor ID and session data for behaviour analytics. | Up to 1 year | Analytics |
posthog_* |
PostHog session recording and feature flag state. | Session / 1 year | Analytics |
| Local storage keys (PostHog) | Stores PostHog configuration and visitor properties in browser local storage. | Persistent | Analytics |
The specific cookies set may change as we update our technology stack. This table reflects our best knowledge at the time of the last update date shown above.
Some cookies on our site are set by third-party services that appear on our pages. We do not control these cookies — they are governed by the privacy policies of the respective third parties.
We use PostHog to collect analytics about how visitors use cookkar.com. PostHog may set cookies and use local storage to identify returning visitors and track session behaviour (page views, clicks, scroll depth, session recordings).
Our website loads fonts from Google Fonts (fonts.googleapis.com). When your browser requests these fonts, Google may log your IP address and browser information. Google Fonts does not set cookies by default, but the request does reveal your IP address to Google's servers.
Our website loads the Tailwind CSS stylesheet from a CDN (cdn.tailwindcss.com). This is a static file request and does not involve tracking cookies, but your IP address is transmitted to the CDN server.
When you submit the waitlist form, your data is sent to Mailchimp. Mailchimp may use cookies and tracking pixels in the emails it sends. For details, see Mailchimp's Cookie Statement.
The FIX app uses Supabase as its backend database and authentication provider. Supabase does not set browser cookies on cookkar.com. Within the app, the Supabase client library stores an authentication session token in AsyncStorage (local device storage) to keep you logged in. This token is not shared with advertising networks.
The FIX app uses Sentry to automatically report crashes and errors so we can fix them. Sentry operates within the app and does not set browser cookies on cookkar.com. Within the app, Sentry may use device-level identifiers (IDFV on iOS, Android Advertising ID on Android) for crash session correlation.
You have several options for controlling cookies:
Most browsers allow you to view, manage, block, and delete cookies through your browser settings. Note that disabling all cookies may affect the functionality of our website. To manage cookies in your browser, see the instructions for your browser below:
You can opt out of PostHog analytics tracking by:
Some browsers have a "Do Not Track" (DNT) feature that signals to websites that you do not want your browsing activity tracked. PostHog is configured to respect the DNT header where technically feasible.
The FIX mobile app is a native application and does not use browser cookies. Instead, the app uses the following local storage mechanisms and SDK-level identifiers to provide functionality and analytics.
The FIX app stores data locally on your device using AsyncStorage (the React Native equivalent of browser local storage). This includes cached kitchen and grocery data for offline access, and your authentication session token. This data does not leave your device via AsyncStorage and is only accessible to the FIX app.
| SDK | Purpose | Data Collected | Opt-Out |
|---|---|---|---|
| Sentry (@sentry/react-native) | Crash reporting and error monitoring | Stack traces, device OS and app version, IDFV/AAID for crash correlation, anonymised session IDs. No personal profile data is sent unless it appears in an error message. | Not applicable — crash reporting is a core reliability function. No personal data is intentionally included in crash reports. |
| Supabase (@supabase/supabase-js) | Backend database and authentication | All user-created data (profile, kitchen inventory, grocery list, recipes). Session token stored locally via AsyncStorage. | You can delete your account and all associated data via Settings → Delete Account in the app. |
| AsyncStorage (@react-native-async-storage) | Local on-device data caching | Session token, cached kitchen and grocery data. Data stays on device only. | Cleared automatically when you log out or delete your account. |
We may update this Cookie Policy from time to time to reflect changes in the technologies we use or in applicable law. When we make changes, we will update the "Last updated" date at the top of this page. We encourage you to review this policy periodically. Your continued use of our website after any changes constitutes your acceptance of the updated policy.
If you have any questions about our use of cookies or this Cookie Policy, please get in touch: