Cookie Policy

1. What This Policy Covers

This Cookie Policy explains how Idea to Life uses cookies and similar browser storage technologies when you use our website and application. Cookies are small text files placed on your device by a website; browsers also offer local storage, which serves similar purposes. This policy should be read together with our Privacy Policy, which describes how we handle personal data more broadly.

Our approach is deliberately minimal: we use only the cookies needed to sign you in and remember your preferences. We do not use third-party advertising cookies, cross-site tracking cookies, or social media tracking pixels anywhere on the Service.

2. Session Cookies (Strictly Necessary)

When you sign in, we set authentication cookies that identify your session. These cookies are essential: without them you could not stay logged in, start builds, manage projects, or access your billing settings. They typically contain an opaque session token or a signed authentication token, never your password.

• Purpose: keeping you signed in and protecting your account from request forgery.
• Set by: our application and our authentication provider (Supabase Auth) acting on our behalf.
• Duration: session cookies expire when the session ends or after a fixed lifetime, after which you must sign in again. Refresh tokens allow the session to renew while you remain active.
• Security attributes: authentication cookies are marked HttpOnly where applicable so scripts cannot read them, Secure so they are only sent over HTTPS, and use SameSite restrictions to limit cross-site sending.

Because these cookies are strictly necessary to provide a service you have requested, they do not require consent in most jurisdictions, and the Service cannot function with them disabled.

3. Preference Cookies

We store a small number of preference values so the app looks and behaves the way you chose:

• Theme: whether you prefer light mode, dark mode, or following your system setting.
• Locale and formatting: your chosen language and regional formatting preferences, where applicable.
• Interface state: minor interface preferences such as dismissed announcements or collapsed panels, so you do not see the same notice repeatedly.

These values may be stored in cookies or in browser local storage. They contain no tracking identifiers and are not shared with third parties. If you clear them, the app simply reverts to defaults.

4. What We Do Not Use

• No third-party advertising cookies: we do not run ad networks on the Service and no advertising company sets cookies through our pages.
• No cross-site tracking: we do not participate in cookie-based profiling of your activity on other websites, and we honor the absence of such trackers by design rather than by opt-out.
• No selling of cookie data: information from cookies is never sold or shared for behavioral advertising.

If we use any first-party analytics, it is configured to operate without cross-site tracking identifiers, and any change to that approach would be reflected in an updated version of this policy before taking effect.

5. Managing Cookies

You can control cookies through your browser settings: most browsers let you view, delete, and block cookies globally or per site, and let you clear local storage. Please note that blocking or deleting strictly necessary cookies will sign you out and prevent the authenticated parts of the Service from working. Deleting preference cookies resets your theme and locale choices but has no other effect.

Instructions for managing cookies are available in the help documentation of every major browser (Chrome, Firefox, Safari, and Edge). Because we do not use advertising cookies, there is no need to use industry ad-choice opt-out tools for our Service.

6. Changes to This Policy

If we introduce new categories of cookies or materially change how existing ones are used, we will update this policy, revise the date at the top, and, where required by law, ask for your consent before setting non-essential cookies. Questions about this policy can be sent to the privacy contact address listed in the application and in our Privacy Policy.