Cookie Policy
Last updated: 1 September 2026
This Cookie Policy explains how Conscious Ventures Ltd, operating as Brand Atlas, uses cookies and similar technologies on brandatlas.ai and, where applicable, app.brandatlas.ai.
Read this with our Privacy Policy.
1. Who we are
Same entity as in the Privacy Policy. Conscious Ventures Ltd, company number 13189124. Registered office: 139 Middle Deal Road, Deal, England, CT14 9RJ. Contact: hello@brandatlas.ai.
2. What are cookies?
Small text files (and similar technologies: pixels, tags, local storage, scripts) placed on your device. In this Policy, “cookies” includes those similar technologies.
3. Why we use cookies
We use cookies and similar technologies to:
- make our website and platform function properly;
- support security, authentication, and session management;
- remember preferences and consent choices;
- understand how visitors and users interact with our website and product;
- measure and improve website and product performance;
- support marketing, ad measurement, and conversion tracking; and
- improve our communications and lead management.
4. Cookie categories we use
4.1 Strictly necessary cookies
Required for core functionality, security, authentication, and user-requested services (login, session, fraud prevention, load balancing, storing cookie consent). Without them, parts of the website or platform may not work.
4.2 Analytics and performance cookies
Help us understand how visitors and users interact with the website and platform (pages visited, navigation, feature use, errors). Used only with consent where required.
4.3 Advertising and marketing cookies
Used to measure marketing campaigns, track conversions, build audiences, and show more relevant advertising on third-party platforms. Used only with consent where required.
5. Cookie and tracking technologies we use
We use tools that may place or access cookies or similar technologies, including:
- Google Analytics
- Google Tag Manager
- PostHog
- Microsoft Clarity
- HubSpot
- Meta
- Google Ads
- TikTok
- Supabase Auth
- Stripe (on Stripe-hosted checkout and portal pages)
- Calendly (when you book a demo)
- Google Sign-In / Google Identity (when you choose Sign in with Google)
Google Tag Manager is used to manage and deploy other tags. It does not by itself determine whether analytics or advertising cookies are set. Those outcomes depend on the individual tools and consent settings configured through it.
5.1 Brand Atlas website (brandatlas.ai)
Demo buttons open Calendly in a new tab. Calendly then sets its own cookies under Calendly’s policies.
5.2 Brand Atlas app (app.brandatlas.ai)
Supabase Auth for login and session (strictly necessary). Where Sign in with Google is enabled, Google’s OAuth/consent pages set cookies on Google’s domains; after you return, Supabase stores the authenticated session.
5.3 Sign in with Google (Google Identity)
You leave the Brand Atlas origin briefly to authenticate with Google. Google may set cookies on accounts.google.com and related domains (Google Privacy Policy). This flow is login only. It is not the same as Google Analytics, Google Ads, or Tag Manager cookies on our site.
5.4 Payments
Stripe sets cookies on Stripe-hosted checkout and customer-portal pages (strictly necessary for payment).
6. More detail on the tools we use
6.1 Google Analytics
We use Google Analytics to understand how visitors use our website, including page views, traffic sources, and on-site behaviour. Google Analytics may use cookies to distinguish users and sessions. Category: Analytics.
6.2 Google Tag Manager
We use Google Tag Manager to deploy and manage other tags. It is not usually itself the source of measurement cookies. Category: Tag management.
6.3 PostHog
We use PostHog for website and product analytics (feature usage, user flows, product performance). Category: Analytics.
6.4 Microsoft Clarity
We use Microsoft Clarity to understand interaction patterns. This may include session replay, clicks, scrolling, and similar behaviour. Category: Analytics.
6.5 HubSpot
We use HubSpot for forms, lead management, communications, and marketing-related analytics. HubSpot may recognise returning visitors, attribute form submissions, and support CRM workflows. Category: Analytics / Marketing.
6.6 Google Ads
We use Google Ads cookies and tags to measure ad performance, attribute conversions, and support remarketing or audience-building where enabled. Category: Advertising / Marketing.
6.7 Meta
We use Meta technologies, such as the Meta Pixel, to measure campaign effectiveness, understand conversions, and support remarketing on Meta platforms. Category: Advertising / Marketing.
6.8 LinkedIn
We use LinkedIn tracking to measure campaign performance, conversions, and retargeting on LinkedIn. Category: Advertising / Marketing.
6.9 TikTok
We use TikTok tracking to measure campaign performance, conversions, and retargeting on TikTok. Category: Advertising / Marketing.
6.10 Supabase Auth
Authentication and account/session management. Necessary for secure login. Category: Strictly necessary.
6.11 Stripe
Payment checkout and customer portal. Category: Strictly necessary (on Stripe’s pages).
6.12 Calendly
Demo booking on Calendly’s domain or embed. Category: Third-party (Calendly).
6.13 Google Sign-In
Google account session and consent cookies on Google’s domains when you use Sign in with Google. Category: Strictly necessary (requested by you).
7. Cookie inventory
The table lists the main cookies and similar technologies that may be used, based on our current setup. Actual names, durations, and behaviour may vary by browser, device, consent, and vendor configuration.
| Provider / Tool | Example cookie or identifier | Purpose | Category | Typical duration | Notes |
|---|---|---|---|---|---|
| Google Analytics | _ga | Distinguishes users | Analytics | 2 years | Common GA4 first-party cookie |
| Google Analytics | _ga_<container-id> | Persists session state | Analytics | 2 years | Container-specific GA4 cookie |
| Google Tag Manager | No fixed marketing or analytics cookie by itself | Tag deployment | Tag management | N/A | GTM manages other tags |
| PostHog | ph_<project_api_key>_posthog | Analytics identifiers and session state | Analytics | Up to 365 days | May also use local storage |
| Microsoft Clarity | _clck | Persists Clarity user ID and preferences | Analytics | Vendor-dependent | First-party |
| Microsoft Clarity | _clsk | Connects page views into one session recording | Analytics | Vendor-dependent | First-party |
| Microsoft Clarity | CLID | First time Clarity saw the user | Analytics | Vendor-dependent | Third-party |
| HubSpot | __hstc | Main visitor tracking | Analytics | 6 months | |
| HubSpot | hubspotutk | Visitor identity | Analytics | 6 months | Contact deduplication |
| HubSpot | __hssc | Session tracking | Analytics | 30 minutes | |
| HubSpot | __hssrc | Detects session restart | Analytics | Session | |
| HubSpot | messagesUtk | Chatflows identity | Functionality / Marketing | 6 months | If chat is enabled |
| HubSpot | __hs_cookie_cat_pref | Cookie consent category preferences | Strictly necessary / Functionality | 6 months | If HubSpot consent tooling is active |
| Google Ads / Conversion Linker | _gcl_aw | Ad click information for conversions | Advertising / Marketing | Configuration-dependent | |
| Google Ads / Conversion Linker | _gcl_* | Ad click information | Advertising / Marketing | Configuration-dependent | |
| Google Ads / Conversion Linker | _gcl_ls | Ad click info in local storage | Advertising / Marketing | Configuration-dependent | Local storage, not a cookie |
| Meta | _fbp | Browser identifier for Meta tracking | Advertising / Marketing | Vendor-dependent | Meta Pixel |
| Meta | _fbc | Click identifier from Meta ads | Advertising / Marketing | Vendor-dependent | When a Meta click ID exists |
| bcookie | Browser identifier | Advertising / Marketing | Up to 1 year | ||
| lidc | Data centre routing | Advertising / Marketing | 24 hours | ||
| UserMatchHistory | LinkedIn Ads ID sync | Advertising / Marketing | 30 days | ||
| AnalyticsSyncHistory | Sync timing with analytics | Advertising / Marketing | 30 days | ||
| lms_ads | Off-platform advertising | Advertising / Marketing | 30 days | ||
| lms_analytics | Off-platform analytics | Analytics / Marketing | 30 days | ||
| li_fat_id | Conversion tracking and retargeting | Advertising / Marketing | 30 days | May be first-party | |
| TikTok | _ttp | TikTok first-party cookie | Advertising / Marketing | 13 months from last use | |
| TikTok | ttclid | TikTok click identifier | Advertising / Marketing | 13 months from last use where applicable | |
| Brand Atlas / Nuxt | Locale or session storage | Language and site function | Strictly necessary | Session or configuration-dependent | |
| Supabase Auth (app) | Auth/session cookies or storage | Login and secure session | Strictly necessary | Session or configuration-dependent | |
| Google Sign-In (Google’s domains) | SID, HSID, NID, __Secure-* (names vary) | Google account auth and OAuth consent | Strictly necessary (requested by you) | Vendor-dependent; set by Google | Not site analytics |
| Stripe (checkout / portal) | Stripe session / fraud cookies | Payment and fraud prevention | Strictly necessary | Vendor-dependent | |
| Calendly (Calendly’s domain) | Calendly scheduling cookies | Demo booking | Third-party (Calendly) | Per Calendly’s policy |
8. Legal basis and consent
We use strictly necessary cookies because they are required to operate the website or provide a service you requested.
We use analytics, performance, advertising, and marketing cookies only where required consent has been obtained through our cookie banner or consent management tool.
You can withdraw or update preferences at any time through our cookie settings tool.
9. Managing your cookie preferences
You can manage cookies by using the cookie banner or settings tool on our website; by adjusting browser settings to block or delete cookies; and by using privacy controls offered by third-party platforms.
Blocking strictly necessary cookies may affect login, checkout, or other core functions.
10. Cookie duration
Some cookies are session cookies (expire when you close the browser). Others are persistent. Actual duration varies by browser, device, consent, and vendor.
11. Third-party cookies and transfers
Some cookies are placed by third-party providers (Google, Meta, LinkedIn, TikTok, HubSpot, PostHog, Clarity, Stripe, Calendly, Supabase, and others listed above). They use information under their own privacy and cookie policies.
Some process personal data outside the UK or EEA. Where required, we rely on adequacy regulations, Standard Contractual Clauses, and/or the UK International Data Transfer Addendum.
12. Your rights
Where cookies involve personal data, UK/EU GDPR rights apply. See the Privacy Policy. Email hello@brandatlas.ai with subject DATA PROTECTION REQUEST.
13. Changes
We may update this Cookie Policy when our use of cookies, the Services, or the law change. Material changes will update the “Last updated” date.
14. Contact
Brand Atlas, Conscious Ventures Ltd, 13189124, 139 Middle Deal Road, Deal, England, CT14 9RJ, hello@brandatlas.ai.