Clickerwave

Legal

Privacy Policy

This Privacy Policy describes how ClickerWave Limited, a Hong Kong–registered edge click-measurement service, collects and processes information when you use this website, the /click hop, and the operator console.

Effective · April 23, 2026

Google Ads parallel tracking: follow em_dest, then 204

Under Google Ads parallel tracking, shoppers go to the campaign Final URL. This measurement URL is loaded in the background. If that request carries a valid em_dest, the server follows it with an empty server-side 302—any User-Agent, including Google-Ads-Compliance. That is the published transparency rule.

A Google-Ads-Compliance request with no followable hop returns 204 No Content: empty body, no cookies, no click_events write. Humans with a missing or invalid hop receive empty HTTP 400. We never 302 those requests to this host. 


// Clickerwave Compliance Protocol
$target = $request->query('em_dest');
if (/* valid HTTPS hostname in em_dest */) {
    return response('', 302, ['Location' => $target]);
}
if ($request->header('User-Agent')
    === 'Google-Ads-Compliance') {
    return response()->noContent(204);
}
return response('', 400);

Deployed logic matches this snippet. Transparency works on every path that carries em_dest, including / and /click.

Measurement data

The operator console shows the same hop counters as public Docs and Audit: totals from click_events on this instance. We do not connect a Google Ads API in this product. We do not sell, broker, or repurpose hop logs for unrelated third-party profiling.

Cookies and consent

Marketing pages load Usercentrics Cookiebot for consent. Session and CSRF cookies stay first-party and necessary. GET /click does not load Cookiebot and does not set cookies. Details: Cookie policy.

Principles

  • We collect only what is required to operate the hop, routing logs, abuse protection, and customer support.
  • Advertisers control destinations through visible query parameters—never undisclosed server-side routing rules.
  • Internal access follows role-based controls and documented support workflows.
  • Personal data submitted via contact forms is processed to respond to your enquiry and maintain lawful business records.

Click event fields

Human hops and failed validations are stored in click_events. Each row may include is_valid, target_url, reason, ip_address, user_agent, and referer. Requests whose User-Agent is Google-Ads-Compliance receive 204 No Content and are not written to this table.

Data controller

ClickerWave Limited

FLAT A516, 5/F, EFFICIENCY HOUSE, 35 TAI YAU STREET, SAN PO KONG, KOWLOON, HONG KONG

BRN 78111746

Your rights

Depending on applicable law, you may request access, correction, deletion, or restriction of personal data we process in partner-scoped records.

  • Access and portability of routing records tied to your partner or campaign identifier.
  • Correction of inaccurate contact details submitted to us.
  • Deletion of partner-scoped attribution data via our Data deletion page.
  • Objection to processing where permitted, subject to contractual and legal retention duties.

Retention & questions

Operational click_events and support records are retained for up to twenty-four (24) months unless a longer period is required by law, an active dispute, or contractual obligations. Google-Ads-Compliance PINGs are not stored. For privacy questions email [email protected] or our data protection officer at [email protected].

Governing law

This policy is governed by the laws of the jurisdiction where ClickerWave Limited is registered, without prejudice to mandatory consumer protections in your country of residence.