Cookie Policy
Last updated: 5 August 2026 · Version 1.2
This policy explains the cookies and similar browser-storage technologies (localStorage) that Tech Professor uses, why we use them, and how you can control them. It should be read alongside our Privacy Policy.
1. What these technologies are
A cookie is a small file a site stores in your browser. localStorage is a similar first-party store that keeps small values (like your theme) on your device. We describe both here because both put data in your browser.
2. Strictly necessary
These are required for the Service to function — to sign you in, keep you signed in, take payment and remember core interface choices. They cannot be switched off, and under ePrivacy rules they do not require consent.
| Name / pattern | Type | Purpose | Set by |
|---|---|---|---|
sb-*-auth-token | Cookie | Keeps your authenticated session so you stay signed in | Supabase Auth |
tp-cookie-consent | localStorage | Remembers your cookie choices so we don't re-ask | Tech Professor |
tp-theme, tp-theme-dark | localStorage | Your color theme (and last dark variant), applied before paint to avoid a flash | Tech Professor |
tp-workspace | localStorage | Your active personal/team/organization workspace | Tech Professor |
tp-nav, tp-rail-* | localStorage | Sidebar and side-rail collapse state | Tech Professor |
tp-repo-order | localStorage | Your sidebar repository order in each workspace | Tech Professor |
| Paddle checkout cookies | Cookie | Set only during checkout to process a payment securely | Paddle |
We also keep some other tp-* / legacy techprof-* preference keys in localStorage (for example your last active repository). These are first-party, non-tracking
conveniences in the same "strictly necessary / functional" bucket.
3. Analytics (optional browser capture — off by default)
We measure product usage with PostHog (EU cloud) to improve the Service. The
PostHog library may load so feature flags can evaluate, but it starts with capture opted out and
memory-only persistence — no ph_* cookies or localStorage until you opt in. Browser analytics events (page views and in-app product events) are collected only after consent — never the
content of your repos or generated material. When you are signed in, events may be linked to your account
id (and email as a person property). Session replay is disabled. You can withdraw this at any time,
which stops future browser collection immediately.
Separately, when you use authenticated API or MCP endpoints with a personal API token, the server may send coarse PostHog usage events (method, tool name, status — no content). Those events do not set cookies and are not controlled by this cookie banner; see the Privacy Policy.
| Name / pattern | Type | Purpose | Set by |
|---|---|---|---|
ph_* / PostHog localStorage | Cookie / localStorage | Distinct id and session for opted-in analytics (only after consent) | PostHog |
4. Managing your choices
Use the button below (also available as "Cookie preferences" in the footer) to review or change your choices at any time. You can also block or delete cookies in your browser settings, though disabling strictly necessary storage will break sign-in and other core features.
5. Changes
If we add a new cookie or storage category, we will update this page and, where the new category is non-essential, re-request your consent through the banner.