Skip to content
RouteSignalDeveloper portalStart integrating
Docs/Privacy & data handling
Privacy by designPolicy

Purpose-limited fraud prevention

RouteSignal minimizes verification data, honors configured disclosure modes, and avoids covert cross-site identity collection.

Built forPartners and reviewers
#

Privacy-safe Telemetry

Verification can process server-issued route context, coarse browser/runtime capabilities, privacy-control signals, storage availability booleans, and summarized interaction timing when allowed by the configured disclosure mode.

  • Identifiers are scoped and hashed where practical.
  • Raw visitor telemetry is not exposed to advertisers or publishers.
  • Privacy controls can limit collection without being treated as proof of fraud.
  • Optional enhanced consistency hashes require explicit enhanced consent configuration.
#

No Covert Fingerprinting

  • RouteSignal does not perform covert fingerprinting.
  • No WebRTC local or private IP discovery.
  • No microphone, camera, clipboard, files, contacts, browsing history, or keystroke contents.
  • No raw canvas images, raw WebGL renders, raw audio buffers, or full installed-font inventory.
  • No persistent cross-site fingerprint identifier by default.
#

Retention and access

High-volume verification and routing records have finite, record-class-specific retention controls. Aggregates may remain longer for reporting and disputes; financial ledgers and required audit records are durable business records. Sensitive access is role-restricted.