Browser-fingerprinting script detected
If this finding appears in a report, the sampled page exposed a library name or code pattern associated with device or browser fingerprinting. Fingerprinting combines device or browser characteristics to distinguish devices. A detected script alone does not establish execution, a persistent identifier, its purpose or a legal breach. This reference page does not inspect your visitors.
Why this matters
Identification can affect privacy even when it uses no cookie. Cookie consent rules can also cover other storage or access technologies; a cookie-only inventory is therefore incomplete. Consent-management tools may control scripts as well as cookies, depending on implementation. A library name cannot determine whether its actual use is advertising, fraud prevention, strictly necessary functionality or an unused dependency. Legal requirements depend on purpose and jurisdiction.
How to fix it
Have the responsible developer and privacy owner identify the script, configuration, execution paths, signals accessed, data sent and retention. Use controlled browser tests before choice, after Reject, after Accept and after withdrawal to verify what actually happens. Distinguish a name match from a working identification flow. Assess the actual purpose and applicable requirements with the responsible adviser; fraud prevention is not an automatic exemption for every implementation. Remove unnecessary collection, apply appropriate choice controls where required and keep the notice accurate. Retest script behaviour and network activity, not only the cookie list. Do not declare compliance or enable identification merely to clear this finding.
Turn website findings into an action plan
Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.
Start Full Audit