Trust Signals: Data Collection and Privacy
This page lists the device and contextual data the Trust Signals SDKs collect and transmit to Futurae infrastructure, and describes how that data is protected.
All fields are optional. A field is omitted from an observation when the required permission is missing, or when the data source is unavailable on the device.
Data collected by the Mobile Sensor SDK
| Data collected | Platform |
|---|---|
| Latitude, longitude, accuracy, speed | Android, iOS |
| Nearby Wi-Fi access points: SSID, BSSID, timestamp | Android, iOS |
| Connected Wi-Fi network: SSID | Android, iOS |
| Connected Wi-Fi network: BSSID, RSSI, connected devices | Android only |
| Nearby Bluetooth LE devices: name, address, timestamp | Android, iOS |
| Connected Bluetooth LE peripherals | Android, iOS |
| Combined nearby BLE and Wi-Fi devices | Android only |
| Devices discovered through Bonjour on the local network | iOS only |
| Public IP address | Android, iOS |
| Timezone ID | Android, iOS |
| Timezone display name | Android only |
| Device model, OS version, screen resolution, uptime | Android, iOS |
| Manufacturer | Android only |
| OS name, screen scale and brightness, proximity sensor state | iOS only |
| User-assigned device name, such as “John’s iPhone” | iOS only |
| Vendor identifier (IDFV), which persists across app reinstalls | iOS only |
| Thermal state, low power mode | iOS only |
| Language and region | Android, iOS |
| Connection type, VPN active, proxy host | Android only |
| Whether a phone call is active | Android, iOS |
| Debugger attached | Android, iOS |
| Developer mode enabled | Android only |
| Host application version | Android, iOS |
| Host application installer source | Android only |
| Host application build number | iOS only |
| Battery level and charging status | Android, iOS |
Data collected by the Browser Sensor SDK
Which behavioral data is collected depends on the features you enable. The fingerprint feature collects its data points as a single combined object. The table lists the relevant ones, and leaves out low-level values used only as internal inputs to its computation.
| Data collected | Type |
|---|---|
| Mouse events: timestamps and coordinates | Behavioral |
| Keystroke durations (key-down / key-up pairs) | Behavioral |
| Form input focus and blur events | Behavioral |
| Window resize events | Behavioral |
| Window inner dimensions and device pixel ratio | Behavioral |
| Browser name, version and operating system | Fingerprint |
| User-agent string | Fingerprint |
| User-agent client hints: platform, architecture, bitness, model, platform version | Fingerprint |
| Browser platform string, raw OS and CPU string | Fingerprint |
| Browser vendor string and rendering-engine flavor | Fingerprint |
| Screen resolution | Fingerprint |
| Hardware concurrency (logical CPU cores) | Fingerprint |
| Device memory (GB) | Fingerprint |
| Touch support: max touch points, touch event and touchstart availability | Fingerprint |
| Timezone, date and time locale, browser language list | Fingerprint |
| Color depth, color gamut, HDR support | Fingerprint |
| Display and accessibility preferences: reduced motion, reduced transparency, inverted colors, forced colors, monochrome, contrast | Fingerprint |
| Browser audio volume, audio subsystem base latency | Fingerprint |
| WebGL: version, vendor, renderer, shading language version (masked and unmasked) | Fingerprint |
Storage availability: cookies, local storage, session storage, IndexedDB, openDatabase | Fingerprint |
| Installed fonts and font-rendering metrics | Fingerprint |
| Installed browser plugins, such as PDF viewers, and PDF-viewing capability | Fingerprint |
| Ad-blocker presence | Fingerprint |
Math function precision, from the output of Math functions for a fixed set of inputs | Fingerprint |
| Apple Pay availability, Privacy-Preserving Ad Click Attribution API support | Fingerprint |
IP address of the browser, passed on by your collection proxy in X-Forwarded-For | Network |
Data in transit
All communication between the SDKs and the backend is encrypted over HTTPS.
Data at rest
Sensor observations and derived signal outputs are stored on Futurae cloud infrastructure with encryption at rest, for a guaranteed retention period of 24 months.
Privacy and access control
Pseudonymization recommendation. The accountId used across the Trust Signals SDKs and Signals API is defined and managed entirely by you. Futurae has no independent means of resolving it to a real-world user identity.
To limit the personal data held on Futurae infrastructure, Futurae recommends supplying a randomly generated, opaque identifier such as a UUID, in place of a username, email address, or any other value that could directly identify the end user. This gives you full control over whether sensor observations can be linked to a specific individual, with no impact on signal quality. The recommended convention is in Identifier Strategy.
Access control is strictly enforced: only authorized service components may access observation data, scoped to the tenant that collected it.
GDPR and data sovereignty
- Futurae processes personal data as a Data Processor on behalf of the service provider, who acts as the Data Controller.
- A Data Processing Agreement (DPA) is available on the Futurae website.
Consent
You are responsible for informing your end users about the sensor data collected by the Trust Signals SDKs, in accordance with applicable privacy regulations.