This Cookie Policy explains what cookies and similar storage technologies DevStackIO uses on https://www.devstackio.com/ (the “Site”), what each one does, and how to control them. It works together with our Privacy Policy.
Last updated: 5 October 2026. Effective date: 5 October 2026.
What cookies are
Cookies are small text files placed on your device by a website. They allow a site to remember your device and preserve state between page loads, such as whether you have already given consent. Cookies may be set by the website itself (“first-party” cookies) or by a third party (“third-party” cookies). Similar technologies — including localStorage, sessionStorage, pixels and SDKs — do the same job of storing data on your device, and we treat them the same way in this policy.
The rule we apply
Under the ePrivacy Directive as implemented in EU Member States, and the Privacy and Electronic Communications (PECR) Regulations 2016 in the UK, cookies and similar technologies that are not strictly necessary may only be stored or read after you have given consent. We apply that rule to all visitors, not only to visitors in Europe, because it is the simplest way to honour the strictest applicable standard.
No analytics or non-essential cookies are set until you accept them. If you reject or ignore the consent panel, the Site still works: you can read every article, use search, and the only consequence is that we receive no measurement of your visit.
Cookies and storage technologies currently in use
| Name | Provider | Category | Purpose | Typical duration |
|---|---|---|---|---|
cookieyes-consent |
CookieYes (CookieYes privacy consent platform) | Necessary | Records which cookie categories you accepted or rejected, so we do not ask you again on every page. | Up to 12 months |
cookieyes-consent-mode |
CookieYes | Necessary | Stores consent-mode signals so Google tags stay blocked until analytics are allowed. | Up to 12 months |
wp-comment-* |
WordPress core | Necessary | Stores the fact that you have submitted a comment form and your author name, email address and website, so the comment is not lost if the page fails to submit. | Session or a few days |
Cloudflare security cookies, including __cf_bm |
Cloudflare, Inc. | Necessary | DDoS mitigation, bot detection and abuse prevention. Set by Cloudflare rather than by us. | Typically 30 minutes to 24 hours |
_ga |
Google LLC (Google Analytics 4) | Analytics — consent required | Distinguishes visitors and sessions for audience measurement. | Up to 2 years |
_ga_<container-id> |
Google LLC (Google Analytics 4) | Analytics — consent required | Persists session state for the Site’s Google Analytics property. | Up to 2 years |
_gid |
Google LLC (Google Analytics 4) | Analytics — consent required | Distinguishes visitors within a single day. | 24 hours |
We do not use advertising cookies. We do not use Google AdSense, and we run no cross-site advertising or behavioural advertising, so there is no “advertising” category of cookies in practice.
Consent categories
Our consent panel, linked in the Site footer, offers the following choices:
- Necessary. Required for the Site to operate and for us to remember your choice. Always active and cannot be switched off, because without them consent cannot be recorded and comment forms break.
- Analytics. Lets us measure how articles are used so we can decide what to write next. Off unless you switch it on.
- Functional, performance and advertising. Currently unused. We keep them in the panel so that the categories remain available if a future feature needs them; they set no cookies today.
You can accept all categories, reject all non-necessary categories, or accept them individually. Rejecting is as easy as accepting.
How to change your choice
- Use the consent panel. A “Cookie Preferences” link is present in the Site footer on every page. Opening it lets you re-run the panel and change any category.
- Clear cookies in your browser. This removes the consent record, so the panel will appear again on your next visit.
- Use a Global Privacy Control or similar signal. We treat opt-out preference signals as a rejection of all non-essential cookies, and analytics will not run for you.
- Block or delete cookies in browser settings. Blocking strictly necessary cookies may stop consent being remembered, cause the consent panel to reappear on each page, and may break comment submission.
Do Not Track
There is no industry standard for “Do Not Track” in browsers today. Rather than rely on it, we use the consent panel as described above, which produces the same result in a more reliable and visible way.
Third-party cookies and embedded content
Articles may embed or link to content hosted elsewhere, including documentation sites, video and repository hosts. We do not control the cookies those third-party pages set once you navigate to them, and they are covered by the third party’s own cookie notice. We do not embed advertising or social-media trackers.
Uptime status badge. The About page embeds an uptime status badge served from badge.uptimerobot.com. Loading it discloses your IP address and browser information to UptimeRobot. It appears on one informational page only, it is not used to profile visitors, and it is not connected to Google Analytics or to any advertising service. If you would rather not load it, ignoring the badge has no effect on anything else on that page.
Change to this policy
If the cookies or storage technologies we use change, we update this table and the revised “Last updated” date. If a change increases what we use, we will ask for your consent again rather than rely on an earlier acceptance.
Contact
Questions about cookies, or a request to delete the data associated with them, can be sent to [email protected].