Cookie Policy
This site runs on a live CDPForge instance. This page explains exactly what gets recorded in your browser, for how long, and how you can change your mind at any time.
1. Tracking is off by default
On your first visit no consent state is written at all: the choice is simply absent, not set to "denied". Until you answer the banner at the bottom of the page, tracking writes no identifier to your browser and sends none to our servers: the events of the page you are on stay in memory only, and are lost if you move to another page. The site's content, including personalised content, still loads, but the request goes out with no identifier and no cookies, so you get the generic content. Tracking only turns on if you choose "Accept": the identifier is saved and the current page's events are sent. If you decline, the site remains fully usable — only the availability of browsing data to the platform changes.
2. What we record in your browser
CDPForge tracking relies mainly on the browser's localStorage and sessionStorage (data that stays on your device, unlike traditional cookies which are sent automatically with every request), but it does also set one cookie — cdpf_did, written by our event-collection server on the cdpforge.com domain. The identifiers (did, bid, sid, cdpf_did) and the event queue are only written once you have accepted tracking. On top of that, this site sets a technical cookie to remember your language choice. Here is every entry, what it does, and how long it lasts:
| Name | Type | Purpose | Duration |
|---|---|---|---|
| did | localStorage | Anonymous identifier for your browser, so we can recognise later visits as the same person. Only written after consent, and deleted if you withdraw it. | Persistent, until you clear your browser data or withdraw consent |
| bid | localStorage | Alternative identifier used only if you arrive via a link with a dedicated parameter (e.g. to recognise you across different domains). Only written after consent, and deleted if you withdraw it. | Persistent, until you clear your browser data or withdraw consent |
| sid | sessionStorage | Identifier for the current browsing session. Only written after consent. | Until the browser is closed |
| eventsqueue | localStorage | Temporary queue of events (e.g. pageviews) waiting to be sent. It only exists after consent: before that, events stay in memory on the page and are neither written nor transmitted. | Until the next send, then cleared |
| cdpf_consent | localStorage | Your tracking consent choice, read on every visit to decide whether to activate tracking. | Persistent, until you change your choice |
| cdpf_user_traits | localStorage | Avoids re-sending the same personal details (e.g. after filling in a form) more than once a week. | 7 days |
| cdpf_experiments | localStorage | Which A/B test variant of a personalisation component you were shown, to correctly attribute conversions. | 7 days |
| cdpf_ad_match_id_sent | localStorage | Avoids re-sending the same advertising identifier more than once (see next section). | Persistent, until you clear your browser data |
| topicsSent | sessionStorage | Avoids sending the Google Topics API signal more than once per session (if supported by your browser). | Until the browser is closed |
| cdpf_consent_synced_at | localStorage | When your consent choice was last re-transmitted, so it isn't resent on every page but is still refreshed roughly every 6 months. | Permanent, until you clear your browser data |
| cdpf_personalize_shown | localStorage | When each personalised component was last shown to you, so it isn't displayed again too often. | Permanent, until you clear your browser data |
| cdpf_did | Cookie (cdpforge.com domain) | Server-side copy of the same anonymous identifier as the did entry, set by our event-collection endpoint only after consent: without consent, tracking requests go out with no cookies, so it is neither read nor set. It lets us recognise you even if browser storage is cleared; being on the cdpforge.com domain, it can also be read by other sites running on the platform. | 400 days |
| cdpf_i18n_redirected | Cookie (this site) | Remembers that the automatic redirect to your browser language has already happened, so your manual language choice isn't overridden. | Per your browser settings |
3. Third-party cookies (read, not set by us)
If Meta's or TikTok's pixels are already active on the page, tracking can read (never set) the cookies those pixels create — _fbp and _fbc for Meta, _ttp for TikTok — to enrich ad attribution. On this site, today, neither pixel is active: this capability is documented for transparency, but currently has no practical effect.
4. Advertising parameters in the URL
If you arrive from an ad (Google, Meta, LinkedIn or TikTok Ads), the page URL may contain a click identifier (e.g. gclid, fbclid, ttclid). It's read once from the page address to link the visit to the ad: it isn't a cookie and isn't carried over into the URL of later pages.
5. How to change your choice
You can accept or reject tracking at any time from the "Cookie preferences" link in the footer of every page, or from the button below. Your choice, including a refusal or a withdrawal, is recorded on our servers as proof of the choice, without cookies, together with an identifier: the one already saved if you had accepted, otherwise one valid only for the current page and never saved. If you withdraw consent, the identifiers and the event queue are deleted from your browser and later requests go out again with no identifier and no cookies; the cdpf_did cookie, which the site cannot delete by itself, is no longer used by tracking, and you can remove it by clearing cdpforge.com's cookies.