All Collections
Happierleads Data
Personal Data - GDPR/CCPA
Personal Data - GDPR/CCPA

Finished articles are visible when they're added to a Help Center collection

George Georgiadis avatar
Written by George Georgiadis
Updated over a week ago

Our Web Visitors feature is fully committed to GDPR compliance. The Web Visitors tracker collects data through AWS (Amazon Web Services) infrastructure, where it is encrypted both in transit and at rest.

The GDPR/CCPA apply to individuals. Happierleads does not share private personal data.

Happierleads only identifies B2B companies and reveals employees contact details that we have found from scraping the web. This means that this information is publicity available. We can also give you the source of where we collected the data from.

We collect the behavioral data of all website visitors, which includes pages viewed, visitor sources and time spent on the site.

The visitor's IP address is collected to detect the company and geographic location.

We only show company visits and automatically filter out all users visiting from residential IP addresses.

If you use Web Visitors and want to comply with GDPR we recommend the following: State your usage of Web Visitors in the same places you state your usage of Google Analytics State your usage of Web Visitors in any places you list your usage of tracking and cookies To further comply with GDPR, when uninstalling the Web Visitors tracking script from your Pipedrive account, all of your visitor data will be deleted.

Here are some official definitions of Personal Data:

  • Understanding whether you are processing personal data is critical to understanding whether the GDPR applies to your activities.

  • Personal data is information that relates to an identified or identifiable individual.

  • What identifies an individual could be as simple as a name, a phone number or other identifiers such as an IP address, a cookie identifier, or other factors.

  • If it is possible to identify an individual directly from the information you are processing, then that information may be personal data.

  • If you cannot directly identify an individual from that information, then you need to consider whether the individual is still identifiable. You should take into account the information you are processing together with all the means reasonably likely to be used by either you or any other person to identify that individual.

  • Even if an individual is identified or identifiable, directly or indirectly, from the data you are processing, it is not personal data unless it ‘relates to’ the individual.

  • When considering whether information ‘relates to’ an individual, you need to take into account a range of factors, including the content of the information, the purpose or purposes for which you are processing it and the likely impact or effect of that processing on the individual.

  • It is possible that the same information is personal data for one controller’s purposes but is not personal data for the purposes of another controller.

  • Information which has had identifiers removed or replaced in order to pseudonymise the data is still personal data for the purposes of GDPR.

  • Information which is truly anonymous is not covered by the GDPR.

  • If information that seems to relate to a particular individual is inaccurate (I.e. it is factually incorrect or is about a different individual), the information is still personal data, as it relates to that individual.

Did this answer your question?