Device Intelligence: Data Collection & Privacy
Exactly what @atol-sh/fingerprint reads in the browser, what it never touches, what the server derives on its own, how erasure works, and the consent controls — plus what disclosure remains your responsibility as the operator.
What the browser SDK collects
@atol-sh/fingerprint reads the signals below once at AtolFingerprint.load(); nothing leaves the browser until you call identify(), which posts them to POST /api/v1/devices/identify. This is the complete list — there is no hidden collection.
- →Canvas hash — a small test scene rendered to an offscreen canvas, hashed server-side.
- →WebGL — unmasked renderer and vendor strings, supported extension names.
- →Audio hash — a numeric hash of an
OfflineAudioContextrender. Raw audio never leaves the device. - →Font subset — presence/absence of a fixed list of 30 common fonts. Names only.
- →Screen metrics — width, height,
devicePixelRatio, color depth. - →Hardware —
navigator.hardwareConcurrency,navigator.deviceMemory. - →Locale —
navigator.languages,navigator.platform, IANA timezone. - →UA Client Hints — high-entropy values:
architecture,model,platformVersionand friends, falling back to the plain user-agent string. - →Touch —
navigator.maxTouchPoints. - →Codec support — which of a fixed set of codec strings the browser accepts.
- →Media devices — the count from
enumerateDevices(). Never labels or device IDs. - →CSS preferences —
prefers-color-scheme,prefers-reduced-motion,pointer,hover, and similar media-query booleans. - →Math fingerprint — results of a fixed set of
Mathfunctions (engine/libm variation). - →Automation markers — booleans:
navigator.webdriver, injected automation globals, and headless indicators.
What is never collected
- →No geolocation. The Geolocation API is never called; any geo analysis is server-side from the IP address.
- →No client-side persistent identifiers. The device ID is assigned by the server. Nothing is written to cookies, localStorage, IndexedDB, or any other client storage.
- →No media device labels or IDs — only the count. No microphone or camera access, no raw audio.
- →No keystroke content, form contents, page contents, or browsing history. The opt-in behavioral tier records timing only — never what was typed.
The SDK identifies devices, not people. No name, email, or other directly identifying attribute is read or transmitted by the fingerprint package.
Server-side signals
Alongside what the browser submits, the control plane derives signals from the connection itself — these are inherent to serving any HTTPS request:
- →Transport fingerprints — TLS, HTTP/2, and TCP characteristics of the connection.
- →IP intelligence — VPN, proxy, and Tor verdicts, and coarse IP-based geo used for the
geo_mismatchsignal.
Raw client signals are processed server-side into the SmartSignals verdicts described in signals & posture; your application consumes verdicts and the anomaly score, not the fingerprints themselves.
Device IDs & the right to erasure
Device IDs are server-assigned — never generated or stored on the client — so erasure is a single server-side operation. Deleting the device removes its profile, fingerprint history, behavioral baselines, and device events. Independent security audit records can remain under their separate retention policy; contact your controller for other personal-data requests.
# Right to erasure: delete a device and its fingerprint data curl -X DELETE https://api.atol.sh/api/v1/devices/dev_2x9f... \ -H "Authorization: Bearer $ATOL_MGMT_TOKEN" # -> 204 No Content
Consent controls in the SDK
Collection is all-or-nothing and fails honest. When disabled, load() reads no browser APIs at all, identify() makes no network request, and no fake or placeholder data is ever produced.
import { AtolFingerprint, isCollectionDisabled } from "@atol-sh/fingerprint"; // Explicit opt-out: collection never runs. const fp = await AtolFingerprint.load({ disabled: !userHasConsented }); const result = await fp.identify({ authorize: async () => ({ scheme: "Bearer", accessToken }), }); if (isCollectionDisabled(result)) { // result = { collection_disabled: true, reason: "config" | "gpc" } } // Global Privacy Control is respected by default. Override only if // you have an independent legal basis (e.g. fraud prevention): const fp2 = await AtolFingerprint.load({ respectGPC: false });
- →
disabled: true— nothing is read or sent;getSignals()returns the sameCollectionDisabledobject. - →Global Privacy Control — when the browser advertises GPC, the SDK disables collection by default (
reason: "gpc").
Your obligations as an operator
Device fingerprinting reads information from the user's terminal equipment. Under GDPR and the ePrivacy Directive this generally requires prior user disclosure and may require prior consent. A GDPR legitimate-interest basis does not by itself waive separate terminal-access requirements. Assess any strictly necessary security exemption for your actual use before collecting.
Atol ships the controls; the disclosure is yours. You are responsible for describing fingerprinting in your own privacy policy and for obtaining any required consent before calling AtolFingerprint.load().