RU EN
www.
Technical audit · 26.05.2026

crossroads.be

Belgian Digital Media Production Studio
BE

crossroads.be — the website of Crossroads digital media, a Belgian production studio working in museography (museum exhibition scenography), documentary film, serious games, and corporate video. Clients include museums and cultural institutions, television, and corporations. For the purposes of this measurement, the site operator, Crossroads, is treated as the controller. Measurement: 108 requests, 5 domains, captured on a clean browser.

Request timeline

+0 ms · portal load
Content and resources served from crossroads.be (OVH hosting, Belgium/EU).
+215 ms · Google WebFont Loader before consent
ajax.googleapis.com/ajax/libs/webfont/1.4.7/webfont.js — the Google web font loader. The visitor's IP address goes to Google (USA).
+231 ms · jQuery from CloudFront
d1tdp7z6w94jbb.cloudfront.net/js/jquery-3.3.1.min.js — a library served from AWS CloudFront (USA).
+257 ms · Google Fonts before consent
fonts.googleapis.com (Open Sans) and fonts.gstatic.com — Google Fonts. The visitor's IP address goes to Google (USA).
session state — no consent
No consent manager present. Zero Set-Cookie headers for the entire session; no user choice was made.
policy not found
No privacy policy page was found on the site; there is no disclosure of data recipients.

Declared versus actual

+ Google Fonts, Google WebFont Loader, jQuery via CloudFront — transmit the IP address to Google and AWS (USA) before consent — not declared
+ No privacy policy found on the site — not declared
+ No consent manager present — not declared

Transfer timings

+215 ms ajax.googleapis.com

Google WebFont Loader. Google, USA.

+231 ms d1tdp7z6w94jbb.cloudfront.net

jQuery. AWS CloudFront, USA.

+257 ms fonts.googleapis.com

Google Fonts (Open Sans). Google, USA.

Detected trackers

Indicators of GDPR non-compliance

Context

crossroads.be is a Belgian website on the crossroads.be domain, hosted on OVH infrastructure. The nature of the owner’s activities cannot be established from a single browser measurement and is not assumed here. Measurement: 108 requests, 5 domains, captured on a clean browser.

Google (USA) — IP address via Google Fonts and Google WebFont Loader; AWS CloudFront (USA) — IP address via the jQuery load.

Declared versus actual

Comparison against a policy is not possible here for an objective reason: no privacy policy page was found on the site. This alone is significant: where processing transmits data to third parties, the absence of any policy means the obligation to inform the visitor of data recipients, purposes, and legal bases is not fulfilled at all.

The measurement records data transfer to external recipients. At +215 ms, the Google WebFont Loader loads from ajax.googleapis.com; at +257 ms, Google Fonts CSS and files (Open Sans) load from fonts.googleapis.com and fonts.gstatic.com; both requests transmit the visitor’s IP address to Google (a US company). At +231 ms, the jQuery library loads from d1tdp7z6w94jbb.cloudfront.net — the AWS CloudFront distribution network (USA). There is no consent manager on the site, not a single cookie is set for the entire session, and no user choice is made — meaning all external requests occur before any consent.

External resources load at +215–257 ms, at the start of the session. There is no consent mechanism; the transfer of the IP address to Google and AWS occurs unconditionally, before and outside of any user choice.

What cannot be claimed from the measurement

The measurement covers the homepage. Google and AWS may use edge nodes within the EU, so the conclusion is drawn based on the recipients’ affiliation (US companies), not the physical location of the nodes. The nature of the site’s activity and the identity of the operator cannot be established from the measurement. The absence of a policy is noted based on a check of the site; if the policy is hosted at a non-standard address not linked from the site, this should be verified separately. Server-side processing is not visible in a browser-based measurement.

Conclusion

The crossroads.be website, before consent and with no consent manager present, transmits the visitor’s IP address to Google (via Google Fonts and WebFont Loader) and to AWS (via the jQuery load from CloudFront). At the same time, no privacy policy page was found on the site, meaning disclosure of data recipients is entirely absent. The combination of data transfer to third-party recipients in the USA before consent and the absence of a policy indicates non-compliance with the requirements for consent, disclosure of recipients, cross-border transfer, and informing the data subject. Remedy: host the fonts and libraries locally, implement a consent mechanism that holds back third-party requests until a choice is made, and publish a privacy policy listing the data recipients.

Evidence

How to verify: download the file and compute its checksum — sha256sum file.har (Linux, macOS) or certutil -hashfile file.har SHA256 (Windows); it must match the one shown. The conclusions apply to the scope of this measurement — see the limitations of the method.

Original (audit)
HAR file: be/crossroads-be-2026-05-26.har
SHA-256: a1d3c6276076a14820aa398b2602581c9a1db28fa58adfd58ccbbc53837cd3fa
Re-check snapshot
Awaiting changes
HAR files are stored on EU infrastructure (Proton Drive). SHA-256 is published for integrity verification.
Want a response from the company about this audit? → Open the tool

Fill in once — it will be inserted into every letter below:

All fields are required to print the document — this is a formal requirement of the letter itself (the particulars of an official submission), not data collection: nothing is sent or saved anywhere, it all stays in your browser and disappears when you close the page. See the methodology for details.

Step 1. Data access request (GDPR Art. 15)

Send this letter directly to the company first — before contacting the regulator it has the right to respond (GDPR Art. 12(3) — 30 days).

Subject: Data access request (GDPR Art. 15) — crossroads.be

To: [insert the company's address — DPO / support / legal department]
From: [Your name], [contact email]

I request access to my personal data processed in connection with the website crossroads.be.

1. Categories of data and purposes of processing (Art. 15(1)(a)-(c))
Based on an independent technical analysis of the site, I request confirmation and detailed disclosure of the following categories of processing:

1) No privacy policy was found on the site. Meanwhile, the site transmits visitor data to third-party recipients (see below). The absence of any policy means the requirement to inform the data subject of recipients and processing purposes is not met at all.

2) Before consent, on page load, the following load: Google WebFont Loader (ajax.googleapis.com, +215 ms), Google Fonts (fonts.googleapis.com + fonts.gstatic.com, Open Sans, +257 ms), and the jQuery library from CloudFront (d1tdp7z6w94jbb.cloudfront.net, +231 ms). These requests transmit the visitor's IP address to Google (USA) and to AWS infrastructure (USA). The recipients are disclosed nowhere.

3) There is no consent manager on the site. All external requests occur on page load, before any choice. Zero Set-Cookie headers for the entire session.


2. Recipients, retention periods, and transfers outside the EEA (Art. 15(1)(c)-(d), 46)
I also request the full list of third-party recipients, the applicable retention period for each category, and the legal basis for any transfer of data outside the EEA. The full technical audit with evidence (saved network log, SHA-256 checksum) is published at: https://gdpru.eu/en/audits/be-crossroads-be/

3. Automated processing and profiling (Art. 15(1)(h))
Please state whether I am subject to automated decision-making or profiling, and if so, disclose the logic involved.

Sincerely,

[Your name]
[contact email]
[Country]


[Date]
IMPORTANT: before filing a complaint with the regulator, first contact the company directly and give it 30 days to respond. Without this step the regulator may reject the complaint. Details and a template letter to the company are in the Methodology.
Ready-to-send complaint letter

Where to file: Autorité de protection des données (APD) — file a complaint online →

The regulator reviews complaints in its national language. There is an officially translated template from the European Data Protection Board (EDPB) — you can use it instead of or alongside this letter: Official EDPB complaint form (PDF, your language)

Subject: Complaint regarding personal data processing — crossroads.be

1. Subject of the complaint
I am filing a complaint regarding the processing of my personal data by the website crossroads.be.

2. Circumstances
I visited the website crossroads.be and found indications that the processing of my personal data does not comply with the GDPR. The technical analysis published on gdpru.eu on 26 May 2026 (open methodology, reproducible measurements) documents the following indications:

1) No privacy policy was found on the site. Meanwhile, the site transmits visitor data to third-party recipients (see below). The absence of any policy means the requirement to inform the data subject of recipients and processing purposes is not met at all.

2) Before consent, on page load, the following load: Google WebFont Loader (ajax.googleapis.com, +215 ms), Google Fonts (fonts.googleapis.com + fonts.gstatic.com, Open Sans, +257 ms), and the jQuery library from CloudFront (d1tdp7z6w94jbb.cloudfront.net, +231 ms). These requests transmit the visitor's IP address to Google (USA) and to AWS infrastructure (USA). The recipients are disclosed nowhere.

3) There is no consent manager on the site. All external requests occur on page load, before any choice. Zero Set-Cookie headers for the entire session.

Full technical documentation is published at: https://gdpru.eu/en/audits/be-crossroads-be/

3. GDPR provisions I ask you to examine
GDPR Art. 13 — absence of information; GDPR Art. 13(1)(e) + Chapter V — disclosure of recipients and transfer; ePrivacy (Belgian implementation) — third-party resources before consent

4. Request
I request that you examine the circumstances described and, if non-compliance is confirmed, apply the measures provided for in Article 58(2) GDPR.

5. Attachments
The full evidence base — the HAR file, its SHA-256 checksum and the quotation from the site's privacy policy documenting the stated contradiction — is published and verifiable at the link in point 2 above.

Sincerely,

[Your name]
[contact email]
[Country]


[Date]