Skip to main content

GDPR and B2B Visitor Identification: What to Check Before You Buy

Before you install a visitor identification script, there are six compliance questions to put to any vendor in writing. Data residency, sub-processors, transfer mechanisms, retention terms, breach notification and contract flexibility. This guide covers all of them.

B2B visitor identification tools process personal data on your behalf. Most teams only think about the compliance questions after a demo. Getting them answered before you sign saves time and avoids renegotiating contract terms after the fact.

Why GDPR comes up early in the buying process

GDPR and B2B Visitor Identification: What to Check Before You BuyB2B visitor identification tools work by collecting IP addresses from your website visitors and matching them to company data. Under UK GDPR and EU GDPR, IP addresses are personal data where they can identify an individual directly or indirectly. That means any tool you install is processing personal data on your behalf, and you are the data controller responsible for how that processing is done.

Is B2B visitor identification legal under GDPR?

Yes, in most cases. Tools in this category generally rely on legitimate interests as their lawful basis. The argument is that identifying which businesses visit a B2B website is a proportionate and reasonable commercial activity, that the processing is limited to business data rather than sensitive personal data, and that the impact on individual privacy is low.

That position is widely accepted in practice. The UK Information Commissioner's Office and most EU data protection authorities recognise legitimate interests as a valid basis for B2B marketing activity, provided the interests test is documented and the processing is proportionate.

You still need to:

  • Document your own legitimate interests assessment
  • Update your privacy policy to disclose the processing
  • Review the vendor's data processing agreement before going live

None of that is complicated, but it needs to be done before you install the tracking script, not after.

The six things to check in any vendor's DPA

Before signing with any visitor identification tool, get the data processing agreement in writing and work through these questions.

  1. Where is visitor data stored? Ask for the specific country or region, not a general reference to cloud infrastructure. The answer determines which data protection regime covers your visitor data and whether any transfer mechanisms are needed.
  2. Who are the sub-processors? The DPA should list every third party that touches your visitor data. Enrichment providers, analytics platforms and cloud hosting providers all count. A long sub-processor list is not automatically a problem, but you need to know what it contains.
  3. What transfer mechanisms cover data leaving the UK or EEA? Under UK GDPR, transferring personal data outside the UK requires either an adequacy decision for the destination country or appropriate safeguards such as standard contractual clauses. If data leaves the UK or EEA, ask which mechanism covers it.
  4. What is the data retention period? How long does the vendor keep your visitor data, and what happens to it when you cancel? Some vendors retain data for extended periods after contract end. Check the deletion terms before you sign, not when you want to leave.
  5. How is a data breach handled? Under UK GDPR you have 72 hours to notify the ICO of a breach that poses a risk to individuals. Your vendor should commit to notifying you within a timeframe that gives you room to meet that obligation.
  6. What is the contract term? If your legal position changes, a monthly contract gives you the ability to exit. An annual contract locks you in regardless of what changes.

What DSGVO means for German buyers

DSGVO is the German abbreviation for Datenschutz-Grundverordnung, the German name for the EU General Data Protection Regulation. It is the same regulation as GDPR. The legal substance is identical.

German data protection authorities have historically taken an active enforcement position relative to some other EU member states. If your business operates in Germany or processes data about individuals in Germany, the documentation requirements above deserve close attention, particularly the legitimate interests assessment and the sub-processor disclosure.

Data residency and why it matters

Where your visitor data is stored determines which legal framework governs it and how straightforward your compliance documentation needs to be.

If data stays within the UK, it falls under UK GDPR and no transfer mechanism is needed. If data stays within the EEA, it falls under EU GDPR with no transfer concerns. If data moves outside either jurisdiction, you need a valid transfer mechanism in place and documented.

For UK buyers, a tool with UK data hosting means your visitor data stays within UK GDPR jurisdiction from collection through to storage. No transfer analysis required.

For EU buyers, the UK holds an adequacy decision from the European Commission. That means data transfers from the EU to the UK are permitted under EU GDPR without additional safeguards, in the same way transfers within the EEA are handled.

When evaluating any tool, ask the data residency question directly and get the answer in writing as part of the DPA.

LeadJaw's position

LeadJaw is built and hosted in the UK. Visitor data collected through the tracking script is processed and stored on UK servers. Data does not transfer outside the UK as part of normal operation.

For UK buyers, the full processing chain sits within UK GDPR jurisdiction. For EU buyers, the UK adequacy decision covers the transfer.

Pricing starts at £39 (€45 EUROS / $49 USD) per month on a monthly basis with no annual contract. The 10-day free trial does not require a payment card.

The practical summary

GDPR compliance in this category is achievable for any reputable tool. The differences between vendors are in data residency, sub-processor exposure, contract flexibility and how readily they provide clear answers to the questions above.

Before you install any visitor identification script, get the DPA, work through the six questions and document your legitimate interests assessment. That process takes an hour and covers your compliance position regardless of which tool you choose.

Perry Jones

Perry Jones

Perry Jones writes about B2B sales, marketing technology and revenue operations. He has spent over a decade working with sales teams across SaaS, professional services and managed IT, helping them build repeatable pipeline from inbound and outbound channels.

Common questions

Yes, in most cases, provided the vendor has a valid lawful basis and you have documented your legitimate interests assessment. Most tools in this category use legitimate interests as their lawful basis for processing business IP data. You are still responsible for reviewing the DPA and updating your privacy policy before going live.

DSGVO stands for Datenschutz-Grundverordnung, the German name for the EU General Data Protection Regulation. It is the same regulation as GDPR. The legal substance is identical to the regulation that applies across the EU.

Check where visitor data is stored, who the sub-processors are, what transfer mechanisms cover any data leaving the UK or EEA, how long data is retained after you cancel, how breaches are notified and what the contract term is. Get all of this in writing before you sign.

Yes. IP addresses are personal data under UK GDPR and EU GDPR where they can identify an individual, directly or indirectly. Business IP addresses linked to a named company fall within scope. The lawful basis and proportionality assessment are different from consumer data processing, but the regulation applies.

A legitimate interests assessment is a three-part test that documents why you believe your processing is lawful under the legitimate interests basis. It covers whether you have a genuine legitimate interest, whether the processing is necessary to achieve it and whether your interests override the privacy rights of the individuals affected.

If a vendor stores your visitor data on UK servers, the processing sits within UK GDPR jurisdiction from end to end. No data transfer mechanism is needed. For EU buyers, the UK holds an adequacy decision from the European Commission, so transfers from the EU to the UK are permitted without additional safeguards.