Cookie Policy
How MeaningStack uses cookies and similar technologies, and how you control them.
This Cookie Policy explains how MeaningStack B.V. uses cookies and similar technologies on our websites. It should be read alongside our Privacy Policy.
1. What cookies are
Cookies are small text files stored on your device when you visit a website. Similar technologies (local storage, pixels, session-recording scripts) work in comparable ways. They can be set by us (“first-party”) or by a third-party service we use (“third-party”), and they can last only for your session or persist for a defined period.
2. How we use them
We group cookies into two categories:
- Strictly necessary — required for the site and core functions (such as signing in and connecting accounts) to work. These are always active and do not require consent, in line with the ePrivacy rules.
- Optional — analytics and product-insight cookies that help us understand and improve the websites. These are off by default and load only if you accept them.
Consent comes first. Optional cookies and the third-party scripts that set them do not run until you accept them through our consent banner. You can change or withdraw your choice at any time (see Section 5).
3. Strictly necessary cookies
These support functions you actively request, so they are always active and cannot be switched off through the consent banner. They include:
- Clerk — authentication and session management, to keep you securely signed in.
- GitHub (OAuth) — set only when you choose to connect a GitHub account, to complete and secure the sign-in flow.
- Cloudflare — bot management and security (e.g. __cf_bm), distinguishing humans from automated traffic to protect the site. Short-lived.
- HubSpot (forms) — functional cookies needed for our contact and waitlist forms to operate.
- Cookiebot — remembers your cookie consent choice so we don’t ask repeatedly.
4. Optional cookies (consent required)
These load only after you accept them and are not essential to using the websites. They help us understand how the site is used so we can improve it — for example, traffic and product analytics. Optional cookies stay off until you give consent, and you can withdraw at any time.
The specific optional cookies currently in use (if any) are always listed accurately in the live cookie declaration below.
Current cookie list
The declaration below is generated and kept up to date automatically, so it always reflects the cookies actually in use on our site.
5. Managing your choices
You can review and change your cookie choices at any time:
- Use our consent banner — reopen it with the button below to accept, reject, or adjust optional categories.
- Adjust your browser settings to block or delete cookies. Note that blocking strictly necessary cookies may stop parts of the site (such as sign-in) from working.
- Withdraw consent at any time — withdrawal is as easy as giving it, and does not affect processing that already took place.
This reopens the consent banner so you can change or withdraw your choices.
6. Third-party cookies
Some cookies are set by third parties whose services we use. These providers act under data-processing agreements with us and are listed in our Privacy Policy. We do not control third-party cookies directly; their use is also governed by each provider’s own policy:
- Clerk — authentication provider (essential)
- GitHub — OAuth sign-in (essential, only when you connect)
- Cloudflare — security and bot management (essential)
- HubSpot — forms (essential) and, with consent, analytics (optional)
- Cookiebot (Usercentrics) — consent management (essential)
7. Changes
We may update this Cookie Policy as our tools change. The current version is always posted with the “Last updated” date above. Where we add a new optional cookie, it will remain off until you consent.
8. Contact
Questions about cookies or this Policy: admin@meaningstack.com.
Note: This document is a template and is not legal advice. Embed your live Cookiebot declaration and confirm the actual cookies in use before publishing.