Privacy Considerations

When using our JavaScript implementation, JavaScript implementation, you may need to be aware of privacy considerations surrounding's data collection approach.

By default, collects standard web browser information about a reader, the uses of which are described below:

  • ip_address: IP address of the user; used for bot blocking and geo trends
  • user_agent: Identifier for the user's device; used for device analytics (mobile vs desktop)
  • first_party_uuid: Site-specific identifier (UUID) for user; used in loyalty analytics (new vs returning)
  • third_party_uuid: Network unique identifier (UUID) for user; used in aggregate benchmarking

To comply with Personally Identifiable Information (PII) restrictions in certain geographic regions, as well as the privacy policies of individual publishers, can selectively disable the tracking of two of these pieces of information (individually for a specific site or API key). These are ip_address and third_party_uuid.

Disabling ip_address tracking will prevent from being able to do bot blocking for your site, but may lead to better compliance with strict privacy policies that consider IP addresses to be PII. also has plans to eventually incorporate geographic information in its dashboards, but blocking IP addresses will eliminate any possibility for this feature to be deployed for publishers on which ip_address tracking is disabled.

Disabling third_party_uuid will prevent from being able to do network-wide benchmarking for your site, but it will not disable any other functionality.

To disable one or both of these, simply contact us at and one of our integration engineers can help.

Do you have an urgent support question?