Cookie Policy

Effective date: August 5, 2026

This Cookie Policy explains how Orchestrate IQ, LLC ("Trazomo") uses cookies and similar storage technologies on our website and learning platform. It supplements our Privacy Policy.

1. What are cookies and similar technologies?

Cookies are small text files stored on your device when you visit a website. Similar technologies include localStorage, sessionStorage, and pixel tags. In this policy, we refer to all of these as "cookies" for simplicity. Most of the non-essential storage Trazomo uses is localStorage rather than cookies, and we say which is which in the inventory below.

2. Categories we use

  • Strictly necessary. Required to run the Services and keep you signed in. Cannot be disabled.
  • Functional. Remember your interface preferences and enable the in-app support Messenger.
  • Analytics. Help us understand how the Services are used so we can improve them.

We do not use advertising or cross-site tracking cookies, and we do not sell or share personal information for cross-context behavioral advertising under US state privacy laws.

3. Consent: what is live today

We want to be exact about this rather than describe a control that is not yet running.

A category-level consent banner is not yet live on this site. Today the analytics identifier described in Section 4 is written to your browser's local storage on your first visit, and the support Messenger loads on every page, without asking you first. The control in our footer currently opens this policy, because there is no preference manager behind it yet. We also do not currently detect or act on the Global Privacy Control (GPC) signal.

Until the consent control ships, you have two ways to stop non-essential storage:

  • Block or clear site data for trazomo.com in your browser settings. Blocking storage entirely will also prevent login, because the authentication session needs it.
  • Write to [email protected] and ask us to suppress analytics for your account. We will confirm when it is done.

Building the opt-in gate is on our roadmap, and we will update this policy and the Privacy Policy with a new effective date when it is in place.

4. Inventory

Strictly necessary

  • Supabase Auth session cookies. Maintain your signed-in state. Purpose: authentication and session continuity. Duration: session plus a short refresh window. Provider: Supabase.
  • Cloudflare security cookies (for example __cf_bm, cf_clearance). Bot management, traffic protection, and rate limiting. Duration: session to 30 days. Provider: Cloudflare.

Functional

  • theme (localStorage). Remembers your light or dark mode choice. Duration: persistent until cleared. Provider: Trazomo (first-party).
  • Brevo Conversations widget storage. Set by the in-app support Messenger when it loads, so that a chat you have open is recognized as yours as you move between pages. Purpose: live chat. Duration: set by the provider. Provider: Sendinblue SAS (d/b/a Brevo). We do not list the individual keys, because the widget writes them itself rather than through our code. See Brevo Privacy.

Analytics

  • trazomo_anon_id (localStorage). A random identifier created on your first visit so that a sequence of events can be recognized as one visit rather than many unrelated ones. Contains no name, email address, or IP address. Duration: persistent until cleared. Provider: Trazomo (first-party).
  • trazomo_distinct_id (localStorage). Written once you sign in, holding your account identifier so that events before and after signup can be joined. Cleared when you sign out. Duration: until sign-out or cleared. Provider: Trazomo (first-party).

The values above are read by our own code and sent, with the analytics event, to PostHog EU Cloud at eu.i.posthog.com. PostHog does not set its own cookies on this site: we do not load the PostHog browser library, so there is no PostHog-managed cookie or storage key to list. Events are the specific ones we have defined in our code, such as starting onboarding, viewing a plan, or completing a lesson. See PostHog Privacy and GDPR compliance.

Two analytics flows carry an email address rather than a pseudonymous identifier. They are described in Section 6.1 of our Privacy Policy, and we would rather point you at them than let the word "pseudonymous" do work it cannot do.

5. No session replay, no automatic capture

We do not use session replay. Nothing records your screen, your mouse movement, your keystrokes, or the contents of any form, including AI-evaluation fields and the support Messenger. We also do not use automatic event capture: the only analytics events that exist are the ones we have explicitly written into the code. If this ever changes, we will update this policy before turning the feature on.

6. Browser controls

You can manage cookies through your browser settings (for example, to clear cookies, block third-party cookies, or enable tracking prevention features). Disabling strictly-necessary cookies will prevent login and core functionality.

7. Changes to this policy

We may update this Cookie Policy from time to time. Material changes will be posted with a new effective date.

8. Contact

Questions about this Cookie Policy:
Orchestrate IQ, LLC
643 N York St, Suite 70, Elmhurst, IL 60126, USA
[email protected]