Transport Encryption
Transport encryption is the protection of signal data while it travels from the browser to the server, so it cannot be read or tampered with in transit. In device intelligence it typically combines standard TLS with an additional application-layer transformation of the payload before it leaves the page.
How Transport Encryption works
The baseline is TLS, the same encryption that secures HTTPS, which establishes an encrypted channel between the browser and the server so that anyone observing the network sees only ciphertext. TLS protects every request and is the non-negotiable foundation for transmitting any sensitive data.
Device intelligence often adds a second, application-layer step: the collected signal payload is transformed on the client with a fast per-byte operation before it is sent, so that the data is already obfuscated at the application level in addition to being wrapped in TLS. This defends against casual inspection and simple tampering by tools that sit at the application boundary, and raises the effort required to reverse-engineer or forge the payload.
The per-byte transformation is deliberately lightweight so it does not add meaningful latency to a real-time identification call. It is not a substitute for TLS but a complement to it, adding a layer that operates inside the application rather than at the network transport, which is where much of the tampering risk against fingerprinting scripts actually lives.
Why Transport Encryption matters for fraud prevention
Signal data is exactly what an attacker wants to observe and manipulate: understanding what the script collects helps them spoof it, and altering the payload in flight could let them forge a chosen identity or evade detection. Encrypting the transport and obfuscating the payload raises the cost of both eavesdropping and tampering, protecting the integrity of the identification that downstream fraud decisions depend on.
How TRACIO handles it
TRACIO protects signal data in transit with a multi-layer approach: a fast per-byte transformation applied on the client before the payload is sent, layered on top of standard TLS. The client-side step is kept lightweight to preserve the platform's real-time latency, so payloads are hardened against inspection and tampering without slowing down identification.
Frequently asked questions
Identify every device with confidence
Start with a free plan of 2,500 API calls per month. No credit card required.