Tracking Disclosure

Effective date: May 29, 2026

This Tracking Disclosure explains how the AdzOn publisher script and ad delivery APIs collect and use data for ad delivery, measurement, fraud prevention, attribution, and publisher revenue.

Where Tracking Happens

Tracking can occur when a publisher installs the AdzOn script on a website and the script loads in a visitor's browser.

The script may request eligible ads, render approved ads, send heartbeats to verify installation, and send ad events such as impressions, clicks, and closes.

Data Collected

The script and API may process publisher site ID, ad ID, delivery ID, signed delivery token, idempotency key, generated visitor ID, hashed browser fingerprint, IP address, user agent, browser, operating system, device type, IP risk signals, screen size, viewport size, pixel ratio, touch points, hardware concurrency, automation/headless indicators, page URL, page referrer, page title, placement type, event type, timestamp, time on page, session event count, session duration, cookies-enabled status, and Do Not Track status.

Why Tracking Is Used

AdzOn uses tracking data to deliver eligible ads, prevent duplicate or replayed events, enforce frequency limits, detect bots and suspicious traffic, determine whether an event is billable, calculate subscription usage and publisher revenue, diagnose publisher script installation, and investigate fraud or disputes.

Cookies, Local Storage, and Fingerprinting

The script may create an adz_visitor_id value in local storage and in a first-party cookie with a maximum age of one year. It may also generate a hashed browser fingerprint.

These technologies can be considered cookies or similar technologies under EU and UK rules. They should not be enabled before valid visitor consent where consent is required.

Consent Responsibilities

Publishers are responsible for explaining AdzOn tracking in their own privacy and cookie notices, obtaining valid consent before enabling non-essential tracking where required, passing or withholding consent signals before loading the script or before enabling tracking features, offering withdrawal or opt-out where required, and not placing the script on pages where consent or lawful basis is missing.

Do Not Track

The script can detect browser Do Not Track status and send it with tracking events. Current platform behavior records the signal for diagnostics and reporting. Publishers should use their consent management setup to avoid running non-essential tracking where Do Not Track, Global Privacy Control, or similar signals must be honored.

Reduced Tracking and Future Consent Mode

AdzOn intends to support a clearer consent mode that can separate contextual ad display from persistent visitor identifiers, fingerprinting, and billable measurement. Until then, publishers should treat the current script as requiring consent in jurisdictions where ad measurement, local storage, cookies, or fingerprinting require consent.

Contact

Tracking and privacy questions can be sent to [email protected].