Our Web Visitors function is totally GDPR compliant. The Web Visitors tracker captures data using GCP (Google Cloud Platform) infrastructure, which encrypts information both in transit and at rest.

The GDPR/CCPA apply to persons. Leadsourcing does not disclose sensitive personal information.

Leadsourcing only identifies B2B organizations and provides employee contact information that we discovered while scraping the web. This signifies that this information is publicly available. We can also provide you with the source from which we collected the data.

We collect behavioural data from all website visitors, such as page views, visitor origins, and time spent on the site.

The visitor's IP address is collected to determine the firm and geographical location.

We only display company visits and immediately filter out any visits from home IP addresses.

If you use Web Visitors and wish to comply with GDPR, we recommend the following: Indicate your use of Web Visitors in the same locations you specify your use of Google Analytics. State your use of Web Visitors in any place you disclose your use of tracking and cookies. To ensure compliance with GDPR, when you uninstall the Web Visitors tracking script from your Leadsourcing account, all visitor data will be deleted.

Here are some official definitions of Personal Data:

• Understanding whether you process personal data is key to determining if GDPR applies to your activities.
• Personal data is any information that relates to an identified or identifiable individual.
• Identifiers can be as simple as a name, phone number, IP address, cookie identifier, or other factors.
• If you can identify an individual directly from the information you process, it may be personal data.
• If direct identification isn't possible, consider whether the individual is still identifiable through other means. Consider all information you process and any reasonable methods that you or others might use to identify that person.
• Even when an individual can be identified from the data, it only counts as personal data if it "relates to" that individual.
• To determine if information "relates to" an individual, consider the content, your processing purposes, and the likely effects of that processing on the person.
• The same information might be personal data for one controller but not for another, depending on how it's used.
• Data with removed or replaced identifiers (pseudonymized data) still counts as personal data under GDPR.
• Truly anonymous information is not subject to GDPR.
• Inaccurate information about an individual (whether factually wrong or about a different person) still counts as personal data if it relates to that individual.