Cookie Policy

1. What Are Cookies

Cookies are small text files stored on your device when you visit a website. They are widely used to make websites work efficiently, provide a better user experience, and supply information to site owners. Similar technologies include local storage, session storage, and browser fingerprinting.

This Cookie Policy explains how AdProtektor Inc. (“AdProtektor,” “we,” “us,” or “our”) uses cookies and similar tracking technologies on our website (adprotektor.app), our application (app.adprotektor.app), and through the tracking script installed on our customers’ websites.

2. Cookies and Browser Storage in the AdProtektor Application

When you use the AdProtektor application at app.adprotektor.app, browser storage supports sign-in and application state. The application stores its authentication token in localStorage, rather than relying only on a session cookie:

Clearing or restricting this storage can prevent sign-in or reset application preferences.

3. Tracking Technologies Used by the AdProtektor Script

The AdProtektor tracking script runs both on our customers’ websites and on our own marketing site at adprotektor.app, where we use it to protect our own advertising. In all cases, it uses the following technologies to detect and prevent click fraud:

3.1 Visitor Identification

The tracking script uses visitor identifiers and device and browser characteristics to help recognize related visits. It stores the visitor identifier in an adp_vid cookie, localStorage and IndexedDB where available. The adp_vid cookie is set with a 180-day lifetime that can be refreshed on a visit; browser restrictions or deletion can shorten this. Local storage and IndexedDB copies may remain until removed or replaced. A surviving copy can be used to restore the identifier in another storage layer. The tracking service can also issue a signed, HttpOnly adp_sid cookie with a 180-day lifetime to validate a returning identifier, subject to browser cookie restrictions.

3.2 Local Storage, Session Storage and IndexedDB

The script uses browser storage for visitor and session identifiers, tracking state and related behavioral identifiers. The marketing site also uses sessionStorage to retain advertising parameters as you navigate toward registration. Storage is scoped by browser origin; other code running with access to that origin may also access JavaScript-readable values.

3.3 Session Recording

When a customer enables session recording for their domain, the script records visitors’ page interactions using industry-standard session-recording technology. Input field values are masked by default to protect visitor privacy.

3.4 Behavioral Tracking

The script monitors on-page interaction and engagement signals. These signals are analyzed by our systems to distinguish legitimate visitors from invalid or automated traffic.

3.5 Advertising and Conversion Cookies

The script reads and can write _fbc and _fbp values used for Meta click and browser attribution. It can also write _adp_ cookies containing advertising click identifiers and campaign parameters, including Google click IDs and UTM values. These cookies normally use a 90-day lifetime that can be refreshed, subject to browser restrictions. When the corresponding conversion flow is used, a short-lived _adp_idh cookie can hold hashed customer identifiers across checkout steps; it has a two-hour lifetime and is cleared when the purchase flow uses it. Which cookies are written depends on the available parameters and configured integrations.

4. Payment, Advertising and Analytics Integrations

The following integrations may use cookies or similar technologies when configured or used:

• Our payment provider — cookies for payment processing and fraud prevention during checkout
• Google and Meta integrations — configured browser tags and identifiers for advertising attribution and conversion measurement

Our marketing site uses the AdProtektor tracking script. Depending on the configured destinations and consent state, that script can load Google tags and the Meta Pixel and communicate with those services for attribution and conversion measurement. A cookie being stored on a first-party domain does not mean its information is never shared with a configured advertising or analytics destination.

5. How to Manage Cookies

You can control and manage cookies through your browser settings. Most browsers allow you to:

• View what cookies are stored and delete them individually
• Block third-party cookies
• Block cookies from specific sites
• Block all cookies
• Delete all cookies when you close the browser

Please note that blocking or deleting cookies may affect the functionality of the AdProtektor application, particularly authentication and session management.

For visitors to websites that use the AdProtektor tracking script: the script uses cookies, browser storage and device and behavioral signals. Clearing cookies alone may leave identifiers in localStorage or IndexedDB. Use your browser’s site-data controls to manage those storage types as well. To learn more about how the tracking script works, please refer to our Privacy Policy.

6. Customers’ Responsibilities

Our customers who install the AdProtektor tracking script on their websites are responsible for:

• Disclosing the use of the tracking script and its data collection practices in their own privacy and cookie policies
• Obtaining any required consent from their website visitors under applicable laws (including GDPR and ePrivacy Directive requirements for cookies and similar technologies)
• Implementing cookie consent mechanisms where required by law

7. Changes to This Policy

We may update this Cookie Policy from time to time to reflect changes in our practices or applicable laws. When we make material changes, we will update the “Last updated” date at the top of this page.

8. Contact Us

If you have questions about this Cookie Policy, contact us at:

AdProtektor Inc.
Email: support@adprotektor.app