Home
ClikBy
ClikBy Knowledge Base
Compliance

Privacy-regulations map

Which regimes most often sit next to cookies and pixels, what the ClikBy Policy covers, and where to look at an external reference such as CookieYes Regulations.

10–12 min Updated: July 2026
99-3Belarus
GDPREU/UK
картаLaw 25 · FADP · DMA

Коротко

  • The map is an overview of regimes people ask about with cookies, pixels, and smart links. Not a certification and not a substitute for a lawyer.
  • In depth on product roles and data: Personal data and cookies и Policy.
  • External reference on regulation wording: CookieYes Knowledge Base → Regulations.
  • ClikBy does not replace a full CMP for all jurisdictions of the client's site — it provides controls on the link redirect and in the Cookie Consent module.

Not legal advice

Material for the account owner and marketer: which laws often come up next to cookie banners, Consent Mode, and pixels, and how that maps to ClikBy product facts.

Any oral or written information from CMP sites (including CookieYes) and from this help article is not legal advice. If needed, contact a lawyer / DPO.

Why a marketer needs the map

  • Pixels and retargeting on smart links often mean third-party cookies and identifiers.
  • The account client = controller of clickers; ClikBy = processor — responsibility for the policy and consents lies with you as the campaign operator.
  • Different regimes require different things: opt-in (GDPR/ePrivacy), opt-out (CCPA/CPRA), platform industry rules (DMA for gatekeepers).
  • One «Accept all» banner without regard to audience and vendors is a typical mistake with multilingual traffic.

ClikBy core: 99-3 / GDPR / CCPA

Belarus, Law No. 99-3 — the basis of the operator Proactive Technology LLC Policy: data-subject rights, roles, cross-border transfer — see the guide and the full policy text.

GDPR (EU/UK) — for the EEA the policy names a representative in Barcelona; consent and legal bases for non-essential cookies are usually stricter than «we just notified».

CCPA / CPRA (California) — more about transparency and opt-out of sale/share; in the product — consent and notice controls, not a «Compliant» stamp by itself.

Detailed breakdown of roles, visits/stats, and cookie consent: Personal data and cookies: BY / GDPR / CCPA.

Canada: Law 25 (Quebec)

Law 25 (modernization of personal-information protection in Quebec) is often compared to GDPR: stricter than federal PIPEDA on consent and sensitive data. Campaigns with an audience in Quebec need clear notices and consent for tracking — do not rely only on the US opt-out model.

Overview in the CookieYes KB: What is Canada Law 25? (Regulations section).

Australia: Privacy Act

The Privacy Act 1988 and Australian Privacy Principles (APP) regulate collection and use of personal information. Transparency, notice of collection (including via cookies), and a way to refuse extra tracking are expected. Applicability thresholds and penalty reforms change — check currency with a lawyer.

Switzerland: FADP (nFADP)

The revised Swiss Federal Act on Data Protection is close to GDPR on transparency, data minimization, and data-subject rights. If you send traffic to CH and place pixels on redirects — record purposes, vendors, and legal bases in your policy.

EU: Digital Markets Act and Digital Services Act

DMA primarily concerns large gatekeepers (platforms with a special status): competition, access to data, consent in ad ecosystems. For an advertiser this affects how Google and other platforms request consent and pass signals — not the «ClikBy banner» directly.

DSA — about a safe digital space and duties of intermediaries/platforms. A marketer needs to understand: platform requirements ≠ automatic coverage of your cookie duties as campaign controller.

CookieYes KB: articles on DMA / DSA in Regulations.

What the ClikBy product actually provides

  • A cookie notice on the redirect of a link with pixels (pixel_notification) and the cookie consent{link_id}.
  • The «Cookie notice window» module (/cookies): accepted / declined / ignored for the client's sites.
  • Customer (controller) / ClikBy (processor) roles for clicks on links — as in the privacy-policy.
  • Pixels from Meta, Google, Yandex, VK, and others live under vendor policies — you initiate connecting them.

We do not promise: automatic choice of a «GDPR vs CCPA vs Law 25» regime by geo IP, a full IAB TCF v2.3 like CMP platforms, or a «certificate of compliance» with every law on the CookieYes list.

CMP, Consent Mode, and smart links

Many sites put a CMP such as CookieYes on the landing page and configure Google Consent Mode separately. A ClikBy smart link is another layer: click → (optionally) a consent window → pixels → destination URL.

  • Align the texts of the site banner and the window on the redirect — otherwise the user sees two different promises.
  • If the site refuses analytics, but on the redirect a pixel still fires without consent — that is the controller's risk.
  • For the EEA an opt-in model before non-essential cookies is more often needed; for California traffic — a clear opt-out / Do Not Sell where applicable.

Practical product guide: Cookie Consent in ClikBy · trust: Trust.

Checklist before an international launch

  • You defined audience geo (BY / EU / US-CA / CA-QC / AU / CH) and who the campaign controller is.
  • You updated the policy and cookie notice for pixel vendors on the links.
  • You enabled the notice on the redirect where you place marketing pixels.
  • You checked alignment with the CMP on the site (if there is one) and with Consent Mode in GTM/Ads.
  • You recorded the DSAR process: clicker → you; account client → ClikBy via Policy contacts.
  • You checked law wording in the external KB: cookieyes.com/kb/regulations.

What’s next?

Check the policy and consents

Start with the personal-data and cookies guide, then enable the notice on links with pixels.