Privacy Guidelines

What are Intersect’s Data Sources?

Intersect pulls only from public records, warranty databases, consumer survey responses, e-commerce website cookies, transactional data, and marketing information. Individuals build this complex network as they accept cookies while they browse the internet, fill in marketing forms, or do business/shop online.

Why Utilize Intersect’s Services?

Intersect’s audience identification technology enables website owners to de-mask approximately 40-60% of website visitors. This database serves as a fundamental data layer for subscribed organizations.

Is My Data Vulnerable?

Any data related to an individual’s identity is safely encrypted to legal standards and is only available to marketers through Intersect’s platforms on the surface – they will be able to see publicly available data but nothing more.

  1. Intersect’s services and products are built on a secure server to keep data isolated, safe, and view-protected.
  2. User organizations are given login usernames and passwords for accounts that can only access data specific to their case – no user or organization has access to the entirety of Intersect’s data.

Double-Opted-In Consumers – How Does That Work?

All source partners represent and warrant that their data can be transferred to third parties and are security certified. Should an individual opt-out within one system, changes will reflect downward – Intersect will no longer store said information.

As covered above, data comes from a variety of sources primarily tied to its point of origin:

These above sources are generally enough to cover multiple ranges of data, including:

  • First name
  • Last name
  • Address
  • Email address
  • Phone number
  • MAIDs
  • Household income
  • Age
  • Gender

How Does Intersect Comply with Privacy Laws?

Intersect’s technologies are fully compliant with all current privacy laws due to the nature of the data collected. As any data collected is based on opt-ins, public databases, and search histories already collected by other sources, when Intersect receives data its nature has already been consented to.

How Can Data Collected be Used?

There are a few ways in which gathered data may be used within Intersect’s platforms:


The data can be utilized in our internal data science programs, encompassing tasks such as customer modeling and scoring, customer audience development, campaign response analysis, customer segmentation, and prospect selection.


We may match customer or prospect data with the data using a standard matching key, such as name, address, email, mobile advertising ID, etc. This matching aims to tie (link) match keys that are not already present in the customer data files.


We can match customer or prospect data with the data using a standard matching key, such as name, address, emails, mobile advertising ID, etc. The resulting purpose of this matching is to add (enhance) the customer and/or prospect data.

Audience Development

We are authorized to utilize all available licensed touch points (hashed emails, MAIDs, etc.) to engage with customers or prospects, aiming to foster and strengthen the relationship with them.


We can link customer data to anonymized users through provided Mobile Ad IDs or hashed emails. Subsequently, we can transmit the anonymized data to destinations, including social and Ad-tech platforms (e.g., DSPs), for utilization in digital sales and marketing endeavors.


We may implement procedures where you receive an online data point (email, hashed email, Mobile Advertising ID) or a phone number and use that data point as a matching key to identify associated PII data in the dataset.

Define an “ID”

The best way to think of an “ID” is to think about yourself! Many little facts make up who you are – your name, address, job, and likes – those elements, called “data points” under Intersect’s platform (API), make up each ID. Each ID is unique and distinguishes one individual from another, ensuring there are never duplicates.

When our pixel technology monitors a website, it captures anonymized information about an individual, matched to an identity within our database. For instance, if the pixel captures an IP address, we can associate it with an identity and provide real-time information about that visitor.

Millions of combinations create a database of IDs going on 600 million and growing.