Effective date: 29 October 2026
1. About cookies and similar technologies
This page explains the cookies and similar technologies Crimtan uses, what each one does, and how to control them. Our Privacy Policy explains what we do with the data they collect and your rights.
A cookie is a small text file a website stores in your browser. It usually holds a random ID, the domain that set it, and an expiry date; only that domain can read it. First-party cookies are set by the site you are visiting; third-party cookies are set by another domain, such as Crimtan's, on that site.
We also use similar technologies:
- Pixels and tags: small pieces of code, such as ConsenTag, that tell us a page loaded or an action happened
- Local storage: browser storage that works like a cookie
- Mobile advertising IDs: resettable IDs provided by iOS and Android
- SDKs and server connections: used in apps and on connected TVs, where cookies don't exist
- ID tokens: encrypted industry IDs such as UID2 and RampID
In this policy, "cookies" covers all of these.
2. Where you'll come across Crimtan cookies
You may come across Crimtan cookies in three places, and the same choices apply in each.
- In ads we serve on other websites and apps; these ads may carry an ad-choices icon that links to our opt-out
- On advertiser websites that use our ConsenTag or pixels to measure visits and conversions. ConsenTag only runs once the site has your consent: either the site's tag manager loads it after you accept, or ConsenTag reads the site's TCF consent string; advertisers must tell you they work with Crimtan and link to this page
- On crimtan.com, our own website; we use cookies to run the site, understand how it's used and, with your consent, to show you Crimtan ads elsewhere
3. Cookies and technologies we use
All advertising cookies need your consent in the UK and EU and last no more than 12 months.
Advertising cookies (Crimtan ads, ConsenTag, partner sites)
| Name | Domain | Type | Purpose | Duration | Basis (UK/EU) |
|---|---|---|---|---|---|
| cid | ctnsnet.com | Third-party | Crimtan ID used to look up the pseudonymous ActiveID we may hold for your browser; ActiveID is used to build interest segments and personalise ads and count how many/which ads we’ve shown you | 365 days | Consent |
| cid_%id% | ctnsnet.com | Third-party | Random Crimtan ID; generated after the first encounter, and replaced with cid after the second encounter | 365 days | Consent |
| opt-token | ctnsnet.com | Third-party | Confirms your opt-out request; your opt-out is then recorded in your cid cookie and on our servers | 15 minutes | Strictly necessary |
| bid | consentag.eu | Third-party | Crimtan ConsenTag ID | 150 days | Consent |
| gid_%id% | ctnsnet.com | Third-party | Google cookie ID, matched to our ActiveID so we can buy ads for you via the Google Ad Exchange | 365 days | Consent |
| __tmbid | Advertiser's domain | First-party | Links your visits and actions on that advertiser's site to your Crimtan ID | 365 days | Consent |
Partner cookies. Our tags can also load tags from ad platforms we work with, such as Google, The Trade Desk and Yahoo, so they can match their IDs with ours. They set their own cookies under their own cookie policies, and only with the same consent.
Crimtan website (crimtan.com)
We group cookies on our website into the categories shown in our cookie banner. Strictly necessary cookies are always on. All other categories are off until you choose to turn them on, and you can change your choice at any time using "Cookie settings" in the footer.
Strictly necessary
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
| OptanonConsent | OneTrust | Stores your cookie choices for each category | 12 months |
| OptanonAlertBoxClosed | OneTrust | Records that you have responded to the cookie banner | 12 months |
| eupubconsent-v2 | OneTrust (IAB TCF) | Stores your consent choices in the IAB Transparency & Consent Framework format, so ad partners can respect them | 12 months |
| sid | Crimtan | Keeps you signed in to Crimtan services | 10 days |
Performance and analytics
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
| _ga | Google Analytics | Distinguishes visitors so we can count visits and pages viewed | 13 months |
| _ga_<ID> | Google Analytics | Keeps track of your current session | 13 months |
| _hjSessionUser_<ID> | Hotjar | Recognises returning visitors so we can understand how pages are used (heatmaps and session recordings) | 12 months |
| _hjHasCachedUserAttributes | Hotjar | Internal Hotjar setting | Session |
| _cs_id | Contentsquare | Recognises returning visitors so we can understand how pages are used | 13 months |
| _cs_c | Contentsquare | Stores your consent status for Contentsquare | 13 months |
| _clck | Microsoft Clarity | Recognises returning visitors so we can understand how pages are used | 12 months |
Targeting and marketing
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
| hubspotutk | HubSpot | Recognises you as a visitor and links your visits to any form you submit | 6 months |
| __hstc | HubSpot | Records when you first and last visited, and how many times | 6 months |
| __hssc | HubSpot | Counts pages viewed in your current visit | 30 minutes |
| __hssrc | HubSpot | Detects when you start a new visit | Session |
| __tmbid | Crimtan (ConsenTag) | Links your visits to crimtan.com to your Crimtan ID, so we can measure our own marketing and show you Crimtan ads elsewhere | 12 months |
Apps and connected TV. Instead of cookies we use your device's advertising ID, or an ID passed by the app or TV platform, for the same purposes and subject to the same consent and opt-out choices.
4. How we check your consent
In the UK and EU, before we set or read an advertising cookie, we check the consent signal from the website or app you're using, and if there's no valid signal, we don't set one.
| Where you are | Signal we read | What happens |
|---|---|---|
| UK and EU/EEA | IAB TCF consent string from the site's banner, or the site confirming you have consented | No advertising cookies or IDs unless you consent to Crimtan |
| Rest of World | A consent signal where local law requires one; otherwise, your opt-out choices | Personalised ads, unless you opt out (section 5) or local law requires consent you haven't given |
UK exemptions. Since 5 February 2026, the Data (Use and Access) Act 2025 lets UK sites set some cookies without consent, such as cookies that count visits to improve the site, as long as you're told and can easily opt out. These exemptions don't cover advertising cookies, so Crimtan's advertising cookies still need your consent.
Strictly necessary cookies (for example, the cookie that remembers your consent or opt-out choice) don't need consent, because the site or your choice can't work without them.
5. How to manage cookies or opt out
You can change your mind at any time, and we stop personalised ads within 72 hours of an opt-out.
- Cookie banner. Reopen the settings on the website you're visiting (on crimtan.com, use "Cookie settings" in the footer) and switch Crimtan or advertising off.
- Crimtan opt-out. Visit crimtan.com/cookies/opt-out. This sets an opt-out cookie in that browser. If you delete your cookies or switch browser, opt out again.
- Browser settings. Block or delete cookies in Chrome, Safari, Firefox or Edge. Blocking all cookies also deletes your opt-out cookie.
- Mobile. Delete or reset your advertising ID, or turn off ad personalisation, in iOS or Android settings.
- Connected TV. Use your TV's ad-personalisation or privacy setting.
- Google Analytics. Use the Google Analytics opt-out add-on.
What changes when you opt out. You'll still see ads, but they won't be based on your interests, and we can't cap how often you see the same one.
6. Updates and contact
We review this page at least once a year and whenever we add or change a cookie, and we post the new version here with its effective date.
Questions: Data Protection Officer, Crimtan Holdings Limited, 192–198 Vauxhall Bridge Road, London SW1V 1DX · dpo@crimtan.com
Our Privacy Policy explains your rights and how to complain to the Information Commission (ICO) or your local data protection authority.
