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

Fingerprint's production setup serves the JS Agent from your own domain, through a custom subdomain or a proxy integration. The docs call this required for correct identification. By default the agent loads 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, storage partitioning generally), so identification from that context is shorter-lived and inconsistent, and for some visitors it fails outright, which means no fraud check runs for them. Serving the agent first-party fixes this. 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.