Cookie Policy
This Cookie Policy explains the cookies and similar technologies (collectively "cookies") we use on tetrik.ai and how to control them. It complements our Privacy Policy.
We follow the EU ePrivacy Directive (2002/58/EC) as transposed in Dutch law (Telecommunicatiewet, art. 11.7a) and the consent standard set by the GDPR: non-essential cookies are only loaded after you give explicit, prior, informed consent. We do not use pre-ticked boxes, cookie walls that force consent, or "consent-by-scrolling".
1. The cookies we currently use
| Cookie | Purpose | Category | Provider | Duration |
|---|---|---|---|---|
tetrik_consent |
Stores your cookie-banner choice so we do not ask again | Strictly necessary (no consent needed) | Tetrik (first-party) | 6 months |
tetrik_session |
Session continuity when using the in-app tool | Strictly necessary | Tetrik (first-party) | Session |
_ga, _ga_* (only if enabled) |
Aggregated, IP-anonymised site analytics | Statistics (consent required) | Google Analytics 4 | up to 13 months |
| YouTube/Vimeo embed cookies (only if you play a video) | Video playback | Marketing / third-party (consent required) | YouTube / Vimeo | varies |
If you do not consent to statistics or marketing cookies, none of those scripts load. The site stays fully functional.
2. How to control cookies
- In our banner. Open the banner from the footer link "Cookie settings" at any time and toggle categories on or off. Withdrawing consent is as easy as giving it (GDPR Art. 7(3)).
- In your browser. All major browsers let you block or delete cookies. Blocking strictly-necessary cookies may break parts of the site.
- Per-tool opt-outs. Google Analytics opt-out:
tools.google.com/dlpage/gaoptout.
3. Tracking technologies we do not use
- No third-party advertising or retargeting pixels (no Meta Pixel, no LinkedIn Insight, no TikTok pixel).
- No cross-site fingerprinting.
- No session-replay tools.
If we add any of these in the future, we will update this policy and re-prompt for consent before activating them.
4. Changes
We will publish material changes at tetrik.ai/legal/cookies at least 14 days before they take effect.
Annex: Cookie-banner specification (for the front-end build)
The following is the build spec for the consent banner — keep this section in the document repo, not on the public page.
A. Behaviour
- First visit. Show the banner. Until the user makes a choice, no non-essential scripts run and no non-essential cookies are written.
- Equal-prominence buttons. "Accept all" and "Reject all" must have identical visual weight (same colour, same size). A third button "Customise" opens the category modal. (Required by EDPB Guidelines 03/2022 and CNIL.)
- No pre-ticked boxes. All non-essential categories default to off.
- Granularity. Categories: Strictly necessary (always on, no toggle), Statistics, Marketing.
- Persist the choice in
tetrik_consent(first-party, 6 months) as JSON:{"v":1, "ts":"<ISO date>", "statistics":bool, "marketing":bool}. - Footer link. "Cookie settings" link in the global footer re-opens the modal so users can change or withdraw consent.
- No cookie wall. Users who reject can still access all content.
- Re-prompt cadence. Re-prompt after 6 months or when categories materially change.
B. Copy (EN — translate to NL/DE/FR/ES for parity with the surveys)
We use cookies We use a few essential cookies to make tetrik.ai work, and — with your permission — analytics cookies to understand how people use the site so we can make it better. We do not use advertising cookies. [ Accept all ] [ Reject all ] [ Customise ] Read our Cookie Policy
C. Tag-manager configuration
If using Google Tag Manager, set GA4 and any future tags to fire only when dataLayer.push({event: 'consent_granted', category: 'statistics'}) has occurred. Use Google Consent Mode v2 with default state denied for analytics_storage, ad_storage, ad_user_data and ad_personalization.
D. Records of consent
Store consent timestamp + chosen categories server-side (Netlify Functions → append to a Google Sheet titled "Consent Log") so we can demonstrate compliance under Art. 7(1) GDPR.