Visitor identification and GDPR
The technical ability to identify a company from a website visit does not answer the legal question. GDPR and ePrivacy require a purpose, a legal basis, transparency and respect for individual rights.
What data is involved
Visitor identification can process IP addresses, page paths, referrers, device and browser metadata, a local visitor identifier, company identifiers and professional contact data. Some of this is personal data; some is company data. The boundaries depend on the facts.
An IP address is often treated as personal data because it can be linked to an individual or household, even when the immediate use is company identification. Do not assume that “company-level” means “outside GDPR.”
Legal bases to examine
- Legitimate interests: possible for some B2B analytics, but requires a documented purpose, necessity and balancing test, plus an easy objection mechanism.
- Consent: may be required where cookie or ePrivacy rules apply, or where the processing is not covered by another basis.
- Contract: rarely the basis for identifying anonymous website visitors, but relevant to customer account data.
- Legal obligation: relevant to specific records, not to general marketing identification.
The correct basis depends on what is collected, why, who receives it and the jurisdiction. A vendor cannot choose the customer's legal basis for the customer's website.
Transparency and notices
The privacy notice should explain the identification purpose, the categories of data, the recipients, international transfers, retention and how to object or opt out. If a script runs before consent in a jurisdiction that requires consent, the notice alone may not fix the issue.
Keep an inventory of every tracking technology on the site. Visitor identification is one processing activity among analytics, ads, chat and CRM tools.
Retention and access
Define how long visitor-level records, account records and contact records are kept. A short retention period for raw events does not necessarily mean the derived account or contact record disappears. Document each category separately.
Access, correction, deletion and objection requests need an owner, a response process and a record. A suppression request may require retaining a minimal record to honor the objection.
Opt-out in practice
- Publish a clear explanation of what is identified and why.
- Provide an easy request channel with no sales requirement.
- Verify identity or authority where necessary.
- Suppress future identification for the relevant site or browser where technically possible.
- Record the request and the action taken.
- Review the process periodically and after vendor changes.
Vendor diligence questions
- What personal data does the script collect?
- What is the source of company and contact data?
- Is there a DPA and a current subprocessor list?
- Where is data processed and transferred?
- How long is each data category retained?
- How are opt-out and deletion requests handled?
- Can collection be disabled by page, country or domain?
- What security and breach-notification terms apply?
Primary sources
- GDPR, Regulation (EU) 2016/679 — Articles 5, 6, 13, 14, 17, 21 and 30 are a useful starting point.
- EDPB Guidelines 1/2024 on Article 6(1)(f) — legitimate interests assessment.
- ICO guidance on legitimate interests — practical balancing test.
- CNIL guidance on cookies and trackers — useful for French/EU website operators.
- ePrivacy Directive 2002/58/EC — cookie and electronic communications rules.
How Kiodo approaches the distinction
Kiodo identifies companies from network signals and suggests relevant contacts at those companies. It does not claim that an IP address proves which individual visited. Customers remain responsible for their notices, legal basis, retention and outreach.
Read the Privacy Notice and RB2B GDPR and opt-out guide for the vendor-specific questions.
Visitor identification and GDPR FAQ
Is an IP address personal data under GDPR?
In many interpretations, yes. An IP address can be linked to an individual or household, directly or indirectly. The fact that it often identifies a network rather than a person does not automatically remove it from scope.
Can legitimate interests justify visitor identification?
It can be considered, but it requires a documented assessment and a balancing test. It is not a blanket permission. Consent or another basis may be required depending on the data, jurisdiction and ePrivacy rules.
What must a privacy notice explain?
The data collected, purposes, legal basis, recipients, transfers, retention and how to exercise rights, including objection and opt-out. It should be specific enough for a visitor to understand what is happening.
Does Kiodo identify a person from an IP?
No. Kiodo identifies companies from network signals and suggests relevant contacts at those companies. It does not claim that an IP proves which person visited.
Is this legal advice?
No. This page is general information. GDPR and ePrivacy analysis depends on the facts, the jurisdiction and current regulatory guidance. Consult qualified counsel before launch.
Start with a defensible company-level workflow.
Start freeGeneral information, not legal advice. Laws, regulatory guidance and contracts vary by jurisdiction and change over time. Consult qualified counsel for your specific processing.