01Scope of the check
The application source and a fresh local browser session on Home, Contact, Gravity Assessment, Cases and Insights were reviewed on 25 October 2026. No cookies were observed in that signed-out local session, and no advertising or analytics tags were identified in application code.
A separate browser check of the published site found platform-injected /~flock.js and /__l5e/events scripts, analytics/event requests and session-id and __dpl cookies. Local preview results therefore do not describe all published-site processing. The cookie purposes and consent controls require review before publication.
02Storage identified
Navigation uses sessionStorage key tsr-scroll-restoration-v1_3 to restore scroll position during your current browser session. This is functional navigation state, not audience profiling.
Restricted editor authentication is configured to persist a sign-in session in browser storage and refresh it. The generated authentication key, session lifetime and any hosted authentication cookies depend on the configured environment; their final inventory and necessity assessment are To be confirmed before publication.
Contact fields and assessment answers are held in page state, not stored as tracking cookies. Assessment handoff information may appear in the Contact URL and browser history.
03Hosting analytics cookies
The published hosting analytics script uses a session-id cookie. Its inspected implementation sets a 30-minute lifetime and uses it with page and performance measurements; the associated requests can include URL, referrer and browser metadata. This audience measurement cannot simply be described as strictly necessary navigation.
A __dpl cookie was also observed. Its purpose and necessity have not been verified: To be confirmed before publication. No purpose is inferred from its name.
The scripts are injected by hosting rather than referenced in the application. No documented pre-consent disable control was verified during this audit. The owner must resolve platform-level disabling or prior-consent gating before treating this policy as final.
04External fonts and infrastructure
Google Fonts requests occur when pages load. A font request is not itself a cookie, but it shares request metadata with a third party. Hosting, content delivery and conditional error diagnostics may also process technical request data. See the Privacy Policy for the verified implementation and unresolved details.
05Cookie preferences
Preferences control is not yet available for the hosting-injected analytics. No nonfunctional accept/reject toggle has been added, because it would not stop those scripts. No consent is inferred from visiting or continuing to use the site. This is an unresolved issue, not a consent-compliant implementation.
You can clear site storage through your browser settings. Clearing authentication storage signs editors out; clearing navigation session storage resets scroll restoration. Browser blocking may affect requested functions. Clearing cookies is not a substitute for prior-consent controls.
Before publication as final, nonessential hosting analytics must be disabled or gated behind prior informed opt-in, equally accessible rejection, granular preferences and a way to withdraw or revisit consent. Necessary storage must remain separate from optional categories.
Questions? hello@datatoday.be
