Fingerprint — First-party deployment (custom subdomain / proxy)

By default the JS Agent loads its script from, and sends requests to, Fingerprint's domain — a third-party context for your site. Browsers restrict third-party storage (Safari's ITP, Firefox's ETP, and storage partitioning generally), which shortens how long an identifier survives and makes identification less consistent. Serving the agent from your own domain puts it in the same first-party context as the rest of your app, which is Fingerprint's recommended production setup. In the dashboard this step is listed under Protect against ad blockers.

Scope and consent

This changes where requests go, not what you are allowed to collect. It is for a site you operate, and it does not reduce any disclosure obligation you already have.