Cookie policy
Last updated: August 17, 2026
This policy describes the cookies and similar technologies used by Stack32, how to accept, refuse or customise them, and how that choice is stored. It complements the Privacy policy.
This document is a structured legal draft intended to inform users. It has not been reviewed by a lawyer and does not constitute legal advice. If in doubt, consult a qualified legal professional.
1. What cookies are
Cookies are small files stored on your device by your browser. Similar technologies include local storage, pixels and scripts that read a device identifier. They can be strictly necessary to run the service, or used for measurement and advertising — in which case we ask for your consent first.
2. Your choices (EU/France, UK, US, Canada)
A banner lets you accept all optional cookies, reject all optional cookies, or customise categories. Accept and reject are equally available. Until you choose, analytics and advertising stay off. Your choice is stored for 13 months (CNIL), then we ask again. You can reopen the panel from “Cookie settings” in the footer, from this page, or via “Do not sell or share my data” (US). A Global Privacy Control (GPC) signal is treated as a refusal of advertising cookies.
3. Strictly necessary cookies
These do not require consent: stack32.locale (language, 12 months), stack32.theme (appearance, 12 months), stack32_consent (your cookie choice, 13 months), Supabase authentication cookies (signed-in session and security), and technical cookies set by hCaptcha on sign-up when that protection is enabled. Blocking them may prevent login or security checks from working.
4. Analytics cookies (optional)
If you accept analytics, we load PostHog (US cloud ingest at us.i.posthog.com, acting as our processor under a data-processing agreement / standard contractual clauses) to measure page views, product usage and session replay. Form fields are masked in replay. Typical cookies include ph_* / distinct_id identifiers, with a lifetime up to 12 months. These scripts do not load if you refuse analytics, if no PostHog key is configured, or after you withdraw consent.
5. Advertising cookies (optional)
If you accept marketing, we may load the Meta (Facebook) Pixel and the TikTok Pixel to measure campaigns and, where those platforms allow, retargeting. Typical cookies include _fbp, _fbc (Meta, up to 90 days) and _ttp / _tt_enable_cookie (TikTok, up to 13 months). These partners may process data in the United States. They do not load if you refuse marketing, if no pixel ID is configured, if your browser sends GPC, or after you withdraw consent.
6. Local storage
Stack32 uses your browser’s local storage to remember language and theme, and, in development/mock mode, to store demo data on your device. PostHog may also use local storage when analytics is accepted.
7. Processors and transfers
Necessary hosting and authentication: IONOS and Supabase. Optional analytics: PostHog (US ingest). Optional advertising: Meta Platforms and TikTok, only if those pixels are configured and you consent. Transfers outside the EU rely on appropriate safeguards such as the European Commission’s standard contractual clauses.
8. How to change or delete cookies
Use Cookie settings on this site to change analytics or marketing. You can also delete cookies and local storage in your browser. Withdrawing consent stops new collection; it does not always erase copies already held by an advertising platform — you can also opt out in your Meta / TikTok account settings. Contact hello@stack32.com for access or deletion requests.