Browser-fingerprinting script detected
Browser fingerprinting is a technique that identifies and tracks visitors using details like screen size, fonts, and browser settings, rather than cookies. This check looks for known fingerprinting code such as FingerprintJS, ClientJS, or canvas-fingerprint patterns. On this site, a fingerprinting library was found loading, which is a form of tracking specifically designed to survive cookie blocking and privacy features like Safari's Intelligent Tracking Prevention. Because fingerprinting doesn't use cookies, it sits outside the reach of the cookie banner and outside what cookie-scanning tools like OneTrust or Cookiebot can see, since they only instrument cookies, not script behaviour. Under GDPR (General Data Protection Regulation), Europe's ePrivacy rules, and CCPA (California Consumer Privacy Act), this kind of identification technology generally still requires visitor consent, so an undisclosed fingerprinting script is regulated tracking happening invisibly. Your privacy lead and developer should first confirm why fingerprinting is being used. Fraud and bot defence can justify it without consent, but using it for ad-tracking cannot. If it's used for anything beyond security, gate the script behind the consent banner so it only runs after a visitor opts in, and add a line to the privacy policy naming it as an identification technology. Budget around half a day.
Why this matters
Because fingerprinting doesn't use cookies, it sits outside the reach of the cookie banner and outside what cookie-scanning tools like OneTrust or Cookiebot can see, since they only instrument cookies, not script behaviour. Under GDPR (General Data Protection Regulation), Europe's ePrivacy rules, and CCPA (California Consumer Privacy Act), this kind of identification technology generally still requires visitor consent, so an undisclosed fingerprinting script is regulated tracking happening invisibly.
How to fix it
Your privacy lead and developer should first confirm why fingerprinting is being used. Fraud and bot defence can justify it without consent, but using it for ad-tracking cannot. If it's used for anything beyond security, gate the script behind the consent banner so it only runs after a visitor opts in, and add a line to the privacy policy naming it as an identification technology. Budget around half a day.