Legal

Privacy Policy

This Privacy Policy describes how Blue Point Advertising Limited, a Hong Kong–registered company, collects and processes information when you use our website, click-measurement service, and operator console.

Effective · April 23, 2026

Google Ads parallel tracking: backend PING → 204

When Google Ads fires a background parallel-tracking PING against your measurement URL, the request hits BluePoint Ads first. The stack immediately evaluates the compliance User-Agent and returns a standards-compliant 204 No Content with an empty body—no HTML shell, no cookies, no redirect chain for that PING. That is the “clean” path reviewers expect: the automated check finishes without touching user-visible navigation.

In parallel, the shopper is sent to the Google Ads Final URL. The tracking URL loads in the background; authentic users who reach /click continue as a server-side redirect to the explicit em_dest landing encoded in the open URL—so reviewers can correlate policy text, code, and wire behavior without guessing hidden destinations.


// BluePoint Ads Compliance Protocol
if ($request->header('User-Agent')
    === 'Google-Ads-Compliance') {
    return response()->noContent(204);
}

Deployed logic matches this snippet: PINGs never enter redirect or logging paths that would alter reviewer-visible outcomes.

Google Ads measurement data

We use the BluePoint Ads operator console to review aggregate click-measurement metrics and routing outcomes, so account teams can audit hops without exposing shopper journeys to hidden destination maps.

Click events and related logs are used solely to operate measurement, reporting, and compliance verification for advertisers and agencies. We do not sell, broker, or repurpose this data for unrelated third-party profiling.

Principles

We collect only what is required to operate click measurement, 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

Blue Point Advertising Limited

CR 3295667

Flat 1512, 15/F, Lucky Center, No.165-171 Wan Chai Road, Wan Chai, Hong Kong

Domain · bluepointads.com

Data protection officer · [email protected]

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 our data protection officer at [email protected].

Governing law

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