COOKIE POLICY
How DeciderStack uses cookies.
This page explains what cookies and similar technologies DeciderStack stores on your device, why we store them, and how you can control them. It is generated by Complianz, the consent plugin we use, and reflects the configuration we have in production.
Last reviewed: September 24, 2026
What is a cookie
A cookie is a small text file that a website asks your browser to store on your device. It can be read back by the same site later. Cookies are used to keep you signed in, remember preferences, and measure traffic. Some cookies are set by us directly; others are set by third parties whose code we load (for example, an analytics provider).
Categories of cookies we use
We group cookies into four categories. The consent banner on your first visit lets you accept or decline categories 2, 3, and 4. Category 1 is always on because the site cannot work without it.
1. Functional (always on)
These cookies keep the site working. They remember your cookie consent choice, your preferred language, and basic session state. They do not track you across other sites.
2. Analytics (opt-in)
If you opt in, we use a privacy-respecting analytics tool that counts how many people visit each page and where the traffic came from. We use this to prioritize which articles to update and which categories to expand. We do not use Google Analytics. We do not sell or share analytics data.
3. Marketing (opt-in, currently unused)
We do not run marketing cookies today. If we add remarketing or conversion pixels in the future, this category will be empty in production until you opt in. We will update this page if anything changes.
4. Third-party embeds (opt-in)
Some articles embed videos or interactive demos from external services. Loading those embeds sets cookies from the third party (for example, the video host). We do not enable embeds by default; if you choose to load one, the third party cookies are set at that moment.
Specific cookies we set
Below is the exact list at the time of the last review. We keep this in sync with the output of Complianz and the actual cookies set by the production build.
| Name | Category | Provider | Purpose | Expiry |
|---|---|---|---|---|
| cmplz_consent_status | Functional | DeciderStack | Stores whether the user has given consent. | 1 year |
| cmplz_policy_id | Functional | DeciderStack | Tracks which version of this policy was shown. | 1 year |
| cmplz_statistics | Functional | DeciderStack | Stores the opt-in choice for analytics. | 1 year |
| cmplz_marketing | Functional | DeciderStack | Stores the opt-in choice for marketing. | 1 year |
| cmplz_functional | Functional | DeciderStack | Stores the opt-in choice for functional extras. | 1 year |
| PHPSESSID | Functional | DeciderStack | Server-side session identifier. | Session |
| wordpress_logged_in_* | Functional | DeciderStack | Keeps the editorial team signed in. Not set for visitors. | Session |
How to control cookies
You can change your consent choice at any time by clicking the small Cookie settings link in the page footer. You can also block cookies in your browser, but parts of the site may stop working.
Questions
For privacy questions, see the Privacy Policy. For everything else, the Contact page lists the channels we watch.