Operated by: TechEd Analyst LLC (Connecticut, USA).
Effective: October 5, 2026. Last updated: October 19, 2026 (footer social links). This Cookie Policy explains how TechEd Analyst ("we," "us," or "our") uses cookies and similar technologies on our websites and web applications, and how you can exercise choices. It should be read together with our Privacy Policy.
Cookies are small text files stored on your device when you visit a site. Similar technologies include local storage, session storage, and pixels or tags that help remember preferences or understand how pages are used. We use these technologies for purposes described below, depending on how our Services are configured.
We group cookies and similar technologies into the following categories. We list only categories that apply to our current stack; we do not name specific third-party advertising cookies unless they are actually deployed.
Required for core operation: for example, maintaining secure sessions after you sign in (including cookies or storage used by our authentication provider, such as Supabase), routing requests through our hosting and edge network (for example, Vercel or similar), load balancing, security and fraud prevention, and remembering essential preferences such as language where implemented. These are typically session- or short-lived and are set based on our legitimate need to deliver the Services.
May be used to remember non-essential choices that improve your experience (for example, UI preferences) where we enable such features. If functional storage is not used in a given area of the product, this category may not apply beyond what is strictly necessary.
We count page views on techedanalyst.com with our own Privacy Analytics, which sets no cookies, stores nothing on your device, and keeps no identifier for you: a visit is counted when a page is loaded from another website or typed in directly (see the table below and our Privacy Policy). We do not run third-party analytics, advertising, or error-tracking tools. Because the public site uses only what is needed to show the page and what you ask for (such as the support chat), we do not show a cookie banner. If we ever add an optional tool, we will name it here and, where required by law, ask for consent before it runs.
We do not describe marketing or advertising cookies here unless they are actually used on our properties. If we deploy third-party ad or remarketing pixels in the future, we will list them in this policy and obtain consent where required. The social media icons in our footer are plain links: they load nothing from those platforms and set no cookies. A platform sets its own cookies only after you click through to it.
The table below reflects technologies identified in our codebase as of October 5, 2026.
| Name / key | Type | First-party | Purpose | Duration |
|---|---|---|---|---|
sb-*-auth-token (Supabase) | Cookie | Yes | Authentication session (strictly necessary) | Session / provider-defined |
teched_cookie_consent | localStorage | Yes | No longer set (our cookie banner was removed on October 5, 2026). Browsers that saw the banner may still hold the old choice; you can clear it. Choices recorded on our server before then (hashed IP address, no name) are deleted after 13 months | Until cleared |
| Vercel edge / routing cookies | Cookie | Yes | Hosting, load balancing, security (strictly necessary) | Session / short-lived |
theme | Cookie | Yes | Remembers light or dark mode (functional) | 1 year |
sidebar_state | Cookie | Yes | Remembers whether the app sidebar is open (functional) | 7 days |
last-selected-team | Cookie | Yes | Remembers which team you last opened (functional) | 30 days |
onboarding_token | Cookie | Yes | Links an onboarding preview you made to the account you then create (strictly necessary for that flow) | 7 days, or until used |
te_support_session_id | localStorage | Yes | Random ID that keeps a support chat together when you are not signed in. Created only when you send your first chat message, never just by visiting | Until cleared |
auth_last_method | localStorage | Yes | Remembers which sign-in method you used last, to suggest it next time (functional) | Until cleared |
tea_workflow_context | sessionStorage | Yes | Keeps your answers between steps of a guided workflow; similar short-lived keys hold an onboarding preview or tool inventory while the tab is open (strictly necessary for that flow) | Until the tab closes |
tea-business-profiles-v2 | localStorage | Yes | Keeps your business profile answers in your browser, only if you tick "Keep a copy in this browser"; never sent to us (an older single-profile key is moved into it and removed) | Until you clear it, untick the box or clear your browser |
lang | Cookie | Yes | Remembers your language if you change it in account settings (functional; only shown when more than one language is offered) | Browser session |
| Stripe checkout cookies | Cookie | Third-party (Stripe domains) | Payment processing and fraud prevention during checkout | Per Stripe policy |
| Privacy Analytics | Cookieless / first-party | Yes | Counts page views without cookies or device storage. No visitor identifier: a visit is a page load from outside the site. Raw page views are deleted after 14 days | N/A |
| Marketing / ad pixels | — | — | Not deployed as of this update | — |
When you use Stripe Checkout or the Stripe customer portal, Stripe may set cookies or use storage on Stripe-controlled domains to process payments, prevent fraud, and comply with regulations. Those technologies are governed by Stripe's policies. Our authentication and application hosting providers may also set first-party or closely related cookies required for the Services.
Session cookies expire when you close your browser (or when the session ends). Persistent cookies remain for a defined period or until you delete them. Exact lifetimes depend on the cookie and provider; security and session cookies are typically short-lived, while preference cookies may last longer if used.
Most browsers let you block or delete cookies through settings. Blocking strictly necessary cookies may prevent sign-in or core features from working. You can also use browser "Do Not Track" signals; we do not respond to all such signals in a uniform way today, but we honor applicable opt-out rights for targeted advertising and similar processing where required by law (see our Privacy Policy). Some U.S. state laws require businesses to treat certain universal opt-out signals (for example, the Global Privacy Control signal) as a request to opt out of "sale" or "sharing" for cross-context behavioral advertising where those activities apply; we describe how we handle such signals in the Privacy Policy.
For mobile apps (if offered), device settings may provide additional controls.
Where local law requires consent before non-essential cookies or similar technologies are used (for example, certain analytics or marketing tools), we will present a consent mechanism (such as a banner or settings panel) before activating those technologies. The mechanism we use will match the categories of cookies and scripts actually deployed on our properties.
We may update this Cookie Policy when our practices or technologies change. The "Last updated" date at the top will change, and we will post the revised policy on this page.
Questions about this Cookie Policy can be sent through our Contact page.
We check which cookies and browser storage our site uses whenever we change it, and update this page to match. This policy describes our own site; it is not legal advice for yours.