Belgium is also a market with a formalised procurement culture, shaped by the density of EU institutions, federations and advisory firms around Brussels. This page sets out the legal framework, what a Belgian buyer's review typically checks, and how lead.box fits into it.
At a glance
- Framework
- GDPR + Act of 30 July 2018 on the protection of natural persons
- Supervision
- APD/GBA — Autorité de protection des données / Gegevensbeschermingsautoriteit
- Usual legal basis
- Legitimate interest, Art. 6(1)(f) GDPR, with a documented balancing test
- Processing location
- ISO-certified EU data centres
The legal framework in Belgium
Regulation at a glance
- FrameworkGDPR + Act of 30 July 2018 on the protection of natural persons
- SupervisionAPD/GBA — Autorité de protection des données / Gegevensbeschermingsautoriteit
- Usual legal basisLegitimate interest, Art. 6(1)(f) GDPR, with a documented balancing test
- Processing locationISO-certified EU data centres
The GDPR applies directly, and the Belgian Act of 30 July 2018 on the protection of natural persons with regard to the processing of personal data completes it at national level: it sets up the supervisory authority, defines specific rules for processing by public bodies, employment contexts and certain sector rules, and lays out the sanction and litigation mechanisms available domestically. For a website operator this means a record of processing activities that can be produced in French, Dutch or English depending on who is reviewing it.
The supervisory authority is the Autorité de protection des données in French and the Gegevensbeschermingsautoriteit in Dutch — commonly abbreviated APD or GBA depending on the language used, and referred to interchangeably as APD/GBA in bilingual correspondence. It publishes guidance, handles complaints, and cooperates with the other EU authorities on cross-border cases, which matters in a country where many organisations operate across the language border or serve EU institutions directly.
Belgium's institutional density adds a layer that is procedural rather than substantive: many Brussels-based organisations — federations, permanent representations, public affairs consultancies — run vendor onboarding through formal procurement processes that expect a data processing agreement, a named sub-processor list and a clear description of the data flow before a tool is approved, independent of the size of the contract.
What the Belgian market expects
Belgium is functionally trilingual for business documentation: Dutch in Flanders, French in Wallonia and Brussels, and English as the working language of much of the EU-institutional and international ecosystem in and around Brussels. A vendor whose legal documents exist only in one of these tends to slow down a review that would otherwise be routine. lead.box keeps its market pages and core legal documents available in the languages that matter for this audience.
The second expectation follows from the concentration of associations, chambers and public affairs firms around Brussels: procurement is often formalised even for modestly priced tools, with a checklist covering the legal basis, the sub-processor list, the data retention period and the location of processing, reviewed before a purchase order is raised rather than after.
The third is a plain, non-promotional account of what the tool actually does. Belgian compliance reviewers, used to EU-level regulatory language, respond better to a precise description — company-level resolution, no device storage, no natural-person identification — than to a claim that a product is broadly 'compliant'.
Start free
Install the snippet and see the first named companies on your own traffic.
What you actually see
Named companies in your dashboard, with industry, size and the pages they read.
Where identification pays off here
The pattern that benefits most is the Brussels institutional and associative ecosystem: EU affairs consultancies, sector federations, law firms and NGOs whose prospects research quietly across a bilingual or trilingual site before a formal request follows. Seeing the organisation name early lets a business development contact reach out while the comparison is still open.
It also suits logistics, life sciences and industrial suppliers along the Antwerp-Brussels-Liège corridor, where a defined set of regional accounts makes even a handful of recognised companies per week a useful list, independent of overall traffic volume.
How lead.box works here
GDPR-compliant visitor identification: the 5 rules
1. Company level only
Identification resolves the organisation behind a visit through network and IP-to-company matching. Individual people are never identified, and a visit that cannot be matched to a company stays anonymous.
2. Legal basis: legitimate interest, Art. 6(1)(f) GDPR
Company-level identification is commonly based on legitimate interest under Art. 6(1)(f) GDPR, documented with a balancing test. Consent is not required where no personal identifiers are processed; the final assessment stays with you as the controller.
3. No personal identifiers
No names, personal e-mail addresses, device fingerprints or cross-site profiles are created. Raw network addresses are not available in the interface, exports or API — only the resolved company is stored.
4. EU data processing
Personal and visitor data concerning the EU is processed in ISO-certified data centres in the European Union. EU visitor data is not moved outside the EU for this purpose.
5. Transparency and opt-out
Disclose the identification in your privacy policy — a copy-ready paragraph is on this page. Every visitor can object at any time through the public opt-out page.
lead.box applies all five rules by design.
Questions from this market
It is workable under the GDPR, which applies directly, together with the Belgian Act of 30 July 2018 on the protection of natural persons with regard to the processing of personal data, which sets up the national supervisory authority and completes the GDPR on matters left to member states. The usual legal basis is legitimate interest under Art. 6(1)(f) GDPR, documented through a written balancing test that weighs the commercial interest in company-level identification against the expectations of the visitor, and the practice is disclosed in the privacy notice available in whichever of Dutch, French or English the reviewer works in. lead.box acts strictly as processor under a data processing agreement; the final assessment of whether this legal basis fits your own website and audience always stays with you as controller, and none of this constitutes legal advice for your specific situation.
The Autorité de protection des données, known as the Gegevensbeschermingsautoriteit in Dutch and commonly abbreviated APD or GBA depending on language, is Belgium's single national supervisory authority, structured with separate directorates including a chambre contentieuse / geschillenkamer that handles enforcement decisions and cooperates with the other EU authorities on cross-border complaints. Its published guidance on cookies and trackers follows the same EU-level logic as the ePrivacy framework: it addresses storing or reading information on a visitor's device, which is not how company-level identification operates, since no identifier is placed on the device and no natural person is singled out. Belgian organisations that already deal with the APD/GBA on other matters — many do, given the density of federations and public bodies in and around Brussels — tend to recognise this device-versus-network distinction quickly once it is spelled out plainly.
Belgian legal and procurement reviewers, particularly the many federations, permanent representations and public affairs consultancies concentrated around Brussels, typically work through a standard vendor checklist even for a modestly priced tool: the written balancing test under Art. 6(1)(f) GDPR, an entry ready for the record of processing activities required under Art. 30 GDPR, the data processing agreement under Art. 28 GDPR, and the sub-processor list, all reviewed before a purchase order is raised rather than after. Because Belgium is functionally trilingual for business documentation, the reviewer conducting this check may work in Dutch, French or English depending on the region and sector, so having the same set of documents available in all three avoids a translation delay at exactly the stage where procurement is otherwise ready to proceed.
lead.box resolves the name and domain of the visiting organisation from network-level signals tied to the visit; it does not set a cookie, does not read from or write to the visitor's device, and does not build a cross-site advertising profile of any kind. It also does not identify the individual employee behind a visit, does not automatically enrich a session with a contact's name or email address, and does not perform a lookup against the Banque-Carrefour des Entreprises or Kruispuntbank van Ondernemingen (BCE/KBO) as part of the core identification step — a Belgian sales team that needs the registered legal name, VAT number or BCE/KBO details for a prospective account typically checks that register separately once a lead looks worth pursuing. The output stays a company name and the pages viewed, never a person and never a verified commercial record.
Belgium's business culture around Brussels is shaped by its institutional density: federations, chambers, EU affairs consultancies and permanent representations often research vendors quietly across a bilingual or trilingual site for weeks, and decisions inside these organisations tend to be consensus-driven across language communities rather than made unilaterally by one manager, which can lengthen the path from first visit to first call. Sales and business development teams commonly run HubSpot or Salesforce, and identified organisations are pushed there by webhook so a regional account owner — often organised by Flanders, Wallonia and Brussels rather than by a single national territory — sees a new lead without manual entry. For logistics and industrial suppliers along the Antwerp-Brussels-Liège corridor, a simple weekly export naming which regional accounts looked at which pages is often enough to justify a direct call.
The data processing agreement under Art. 28 GDPR and a versioned sub-processor list are published in the languages a Belgian reviewer is likely to need, so a data protection officer, an in-house counsel or an external Délégué à la protection des données / functionaris voor gegevensbescherming can complete a first review before a purchase order is raised. Data concerning EU visitors, including Belgian visitors, is processed in ISO-certified EU data centres and is not moved outside the EU for this purpose, which matters in a country whose courts and public institutions pay close attention to international transfer questions given Belgium's role as an EU institutional hub. Because Belgian procurement checklists specifically ask for the processing location and retention period as separate line items, having both published in advance removes two of the more common points where a review otherwise stalls.
Getting started means adding a first-party JavaScript snippet to the site, most often deployed through a tag manager, after which identified organisations typically begin appearing within the first days of traffic without any waiting period tied to a contract term. From there, results can be exported as CSV or Excel, filtered by region, sector or page visited, or pushed automatically by webhook into whichever CRM the team already runs, which matters for organisations split across Flemish, French-speaking and Brussels-based teams that may otherwise track leads in separate spreadsheets. Seats can be added as the team grows, and cancellation happens through self-service account settings rather than a formal written notice, which fits how many Belgian organisations prefer to trial a new tool on a limited basis before a longer commitment is discussed internally.
Identification depends on how a visit reaches the internet, and a visitor on a fixed office connection through a major Belgian operator such as Proximus, Orange Belgium, Telenet or VOO is generally resolved reliably, while mobile connections, personal VPNs and shared connections are harder or impossible to attribute correctly. Brussels adds a specific complication: many federations, permanent representations and public affairs consultancies share a single office building and a single internet connection, which can produce a resolved name that reflects the building's main occupant rather than the specific organisation actually browsing the site, and the same applies to holding structures where several subsidiaries share one group-level connection. Visitors near the language and national borders with France, the Netherlands or Germany can also occasionally resolve to a parent entity registered abroad. lead.box treats every match as a signal to qualify, not a confirmed fact, and a sales team should verify the account before treating it as a qualified lead.
See which Belgian companies are already visiting your site
Install a first-party snippet, watch the first companies appear, and hand your reviewer the data processing agreement in the language they need.