RB2B, GDPR and opt-out
Website visitor identification sits at the intersection of sales, analytics and privacy. This guide explains the questions to ask RB2B or any vendor before collecting visitor data, and how Kiodo approaches the problem.
Start with the data, not the label
“GDPR compliant” is not a badge a vendor can simply print on a page. The analysis depends on what data is collected, why it is collected, who receives it, how long it is retained, what rights visitors have and which contracts govern the processing.
For visitor identification, the relevant data can include IP addresses, device and browser signals, page paths, referrers, company identifiers and professional contact data. An IP address can be personal data in many interpretations, even when it usually identifies a network rather than a person.
Legal basis and transparency
Under GDPR, a business needs a legal basis for processing. Legitimate interests is commonly considered for B2B analytics, but it requires a documented balancing test and respect for individual rights. Consent may be required in some cases, particularly where cookie or ePrivacy rules apply.
Whatever the basis, transparency matters. The privacy notice should explain what is collected, the purpose, the categories of recipients, retention and how to object or opt out.
Questions to ask RB2B
- What personal data is collected by the script and by the identity graph?
- What is the legal basis for each processing activity?
- Is a DPA available, and what does it say about subprocessors and transfers?
- How long is visitor-level data retained?
- How does the opt-out process work, and how quickly is it honored?
- Can the customer disable collection for specific pages, countries or domains?
- How are access, deletion and objection requests handled?
- What security controls and incident notification terms apply?
What a good opt-out process looks like
- A public page that explains identification in plain language.
- A simple request channel that does not require a sales conversation.
- Identity and authority verification where necessary.
- A documented response deadline and internal owner.
- A suppression mechanism for future identification where technically possible.
- A record of the request and the action taken.
An opt-out is not the same as deleting every record. A business may need to retain a minimal suppression record to honor the request, subject to applicable law.
How Kiodo approaches it
Kiodo identifies companies from network signals and reveals relevant contacts from its data workflow. It does not claim that an IP address proves which individual visited the site. Suggested contacts are people at the company, not proof of visitor identity.
Kiodo supports exclusions, country filters and tracking controls, and the customer remains responsible for its website notices, legal basis and contact outreach. Review the Privacy Notice and Terms for the current product description.
If you use RB2B and Kiodo together
Keep one inventory of tracking technologies and one owner for privacy requests. If a visitor opts out, make sure the preference is reflected across every vendor and workflow, not only in one dashboard. Avoid collecting person-level data you cannot justify or securely retain.
GDPR and opt-out FAQ
Is RB2B GDPR compliant?
Compliance is not a yes/no label. It depends on the legal basis, the data collected, the contracts, retention, security and how opt-outs are honored. Ask the vendor for its DPA, subprocessor list and current privacy documentation, and have counsel review your use case.
Does a website visitor have to opt in?
That depends on jurisdiction, the data collected and the legal basis. GDPR does not always require consent, but legitimate interests must be assessed and balanced. Cookie and ePrivacy rules may also apply. This is not legal advice.
What should an opt-out process include?
A clear public explanation, an easy request channel, identity verification where necessary, a documented response process and a way to suppress future identification for the relevant website or browser where technically possible.
Can IP addresses identify a person?
An IP address is personal data in many legal interpretations. It usually identifies a network or company more reliably than a specific person. Kiodo does not claim that an IP identifies the individual visitor.
What is a DPA?
A data processing agreement allocates responsibilities between the customer and the processor. It should cover instructions, confidentiality, security, subprocessors, international transfers, breach notification and deletion or return of data.
Use company-level intent with a clearer data story.
Start freeThis page is general information, not legal advice. Laws and regulatory guidance vary by jurisdiction and change over time. Consult qualified counsel for your specific processing.