Template EmpireCookie Policy
Cookie Policy
Last updated: 22 May 2026
What we set, and when
Our default position is that nothing optional runs until you actively consent via the banner. Strictly necessary state — the Supabase Auth session cookie and your consent choice (stored in your browser's local storage as cookie-consent, not as a cookie) — are always on because the site can't function without them. Everything else stays off until you click Accept.
You can withdraw consent at any time by clearing the cookie-consent entry in your browser's local storage; the banner will reappear on next visit. If your browser sends the Global Privacy Control signal, we treat it as a binding rejection of optional analytics — Microsoft Clarity never loads — regardless of any prior accept stored in your browser.
Cookies we may set
| Cookie / Storage key | Set by | Purpose | Retention |
|---|---|---|---|
cookie-consent | Template Empire | Stores your accept / reject choice so we don't re-ask | Until cleared |
| Supabase Auth session cookies | Template Empire (Supabase) | Keeps you signed in to /account between visits | HttpOnly, ~1 week sliding |
_clck, _clsk | Microsoft Clarity | Anonymised session replay + heatmaps for UX analysis. Only loaded after you Accept. | ~1 year (Clarity-managed) |
| Vercel analytics request markers | Vercel | Aggregated page-view counts. No cookies set — uses no-cookie request analytics. | N/A |
| Stripe checkout session | Stripe | Set only when you open the checkout form. Required for payment processing. | Stripe-managed |
Third-party sub-processors
Where a third-party tool sets cookies on our behalf, we list them in our Privacy Policy sub-processor table along with their legal-basis classification. Microsoft Clarity is the only optional sub-processor that depends on your consent; the rest are strictly necessary or analytics-without-cookies.
Questions or complaints
Email support@templateempire.io. UK / EU residents can also complain to the Information Commissioner's Office.