POLICY · COOKIES

Cookie Policy

Plain-English summary of what cookies Brokerage Atlas sets and why. Last reviewed 2026-06-17.

Current state

Brokerage Atlas sets analytics cookies only with your consent. The site is statically rendered on Cloudflare Pages. Since July 2026 it runs Google Analytics 4 in Consent Mode v2 with all storage defaulted to denied: until you press Accept in the consent banner, no analytics cookies are written and GA4 sends only cookieless, aggregated consent-mode pings. If you accept, GA4 sets _ga and _ga_V530NJLELF (see Google's policy for retention), and your choice is stored in the localStorage key brokerageatlas-consent. No advertising pixels, no session recording.

Cloudflare may set its own infrastructure cookies (e.g. __cf_bm for bot-management, __cfduid — now deprecated — for security). These are set by Cloudflare, not by Brokerage Atlas, and are governed by Cloudflare's privacy policy.

When the affiliate-redirect infrastructure is activated (Cloudflare Workers + D1, not yet live in production), clicking a /go/{vendor} outbound link will set a first-party cookie to attribute the referral:

Cookie name Purpose Retention First / third party
ba_ref Records which vendor outbound link was clicked, to attribute a referral commission if you later sign up 180 days First-party (brokerageatlas.com)

This cookie contains no personally identifiable information. It is scoped to brokerageatlas.com and is not used for cross-site tracking. We will update this policy when click logging goes live.

Affiliate network cookies

Brokerage Atlas is applying to affiliate programs operated by third-party networks including Awin and Impact. When these integrations are active, clicking an affiliate link may cause the destination vendor's site (or the network's redirect server) to set its own tracking cookie. These are third-party cookies set on the vendor's domain, not on brokerageatlas.com:

Network Cookie / parameter Purpose Where set
Awin AWC Affiliate window click — tracks the click that generated a referral, used by Awin to attribute commission Awin redirect / vendor domain
Impact irclickid Impact click ID — equivalent click-attribution token used by the Impact platform Impact redirect / vendor domain

Neither network cookie is set by Brokerage Atlas directly. Both are subject to the respective network's privacy terms: Awin privacy policy · Impact privacy policy. This section will be updated once the integrations are confirmed active.

When the attribution cookie (ba_ref) is active, the legal basis for processing is Art. 6(1)(a) GDPR — consent. We will not set this cookie until we have implemented an appropriate consent mechanism for visitors in the EEA.

Cloudflare's infrastructure cookies (security and performance) are processed on the basis of Art. 6(1)(f) GDPR — legitimate interests (protecting the site against automated abuse). Brokerage Atlas does not control these cookies.

This site is operated by a private individual based in Cyprus. The applicable supervisory authority is the Office of the Commissioner for Personal Data Protection (Cyprus): www.dataprotection.gov.cy. See the privacy policy for full controller details.

How to opt out

Decline in the consent banner and no analytics cookies are ever set. To change or withdraw a previous choice, delete the brokerageatlas-consent entry from localStorage (browser developer tools → Application → Local Storage) and reload — the banner will reappear. You can additionally:

  • Manage browser cookies: all major browsers let you view, delete, and block cookies per domain. See your browser's privacy settings.
  • Opt out of Awin tracking: use Awin's opt-out page at awin.com/gb/privacy/opt-out.
  • Opt out of Impact tracking: Impact participates in the NAI opt-out platform.
  • Block third-party cookies: modern browsers offer a native setting to block all third-party cookies, which prevents affiliate network cookies from being set by destination sites.

Changes to this policy

This policy reflects our current (minimal) cookie posture. Material changes — particularly activating the attribution cookie or adding analytics — will be logged at /corrections/ with the date and the rationale. See also our privacy policy for the full data-collection posture.

Questions

Cookie or privacy questions go to contact@brokerageatlas.com or via /contact/legal/.