Cooked.

Cookie Policy

Cooked — Last updated: June 21, 2026

This Cookie Policy explains how Noware (“we”, “us”, or “our”) uses cookies and similar browser storage when you use Cooked (“the Service”) at get-cooked.io. By using the Service you agree to the use of cookies as described here.

1. What Are Cookies?

Cookies are small text files that a website places on your device when you visit. They allow the site to remember information about your visit, such as whether you are signed in. We also use browser local storage, which works similarly but is never sent to our servers.

2. Cookies We Use

We use only strictly necessary cookies. We do not use analytics, advertising, or any third-party tracking cookies.

  • Session cookie (authjs.session-token) — stores your encrypted authentication session so you stay signed in. This cookie is HTTP-only (not accessible to JavaScript), scoped to this domain, and expires when your session ends or after 30 days, whichever comes first.
  • PKCE code verifier (authjs.pkce.code_verifier) — a short-lived, HTTP-only cookie used during the OAuth sign-in flow (Google, Microsoft, etc.) to securely complete the sign-in handshake. It is deleted automatically once sign-in is complete.
  • CSRF token (authjs.csrf-token) — a short-lived token that prevents cross-site request forgery during sign-in and sign-out. It is deleted automatically after use.
  • Callback URL (authjs.callback-url) — remembers the page you were trying to reach so we can redirect you there after sign-in. It is deleted automatically after use.
  • Invite code (cc_invite) — if you arrive via an invite link, this short-lived cookie holds your invite code through the sign-up flow. It is deleted once the invite is redeemed.

3. Local Storage

We store one item in your browser’s local storage:

  • cooked:now-cooking— remembers your active cooking session (which recipe you are currently cooking and your progress through the steps). This data is stored entirely on your device and is never transmitted to our servers.

4. No Third-Party Tracking

We do not use Google Analytics, Meta Pixel, or any other third-party analytics or advertising service. No cookies or tracking scripts from third parties are loaded on any page of the Service.

When you sign in with a third-party provider (Google, Microsoft), you are temporarily redirected to that provider’s website. Any cookies set by those providers during sign-in are governed by their own privacy and cookie policies, not this one.

5. Managing Cookies

All cookies we set are strictly necessary for the Service to function. You can delete or block them through your browser settings, but doing so will prevent you from signing in or using the Service.

Most browsers allow you to view and delete cookies via their settings or developer tools. You can also clear local storage in the same way. Refer to your browser’s help documentation for instructions.

6. Changes to This Policy

We may update this Cookie Policy from time to time. We will notify you of material changes by posting the revised Policy on this page and updating the “Last updated” date above. Continued use of the Service after changes take effect constitutes your acceptance of the revised Policy.

7. Contact

If you have questions about this Cookie Policy, please contact us at:
Noware
support@get-cooked.io
https://get-cooked.io