Privacy
Driving data is personal data in most jurisdictions we would operate in. This page describes how we intend to handle it.
Draft — not yet reviewed by counsel
This is an engineering description of our data handling, written to be accurate rather than to be a binding legal instrument. It must be reviewed by a qualified lawyer, and adapted for GDPR, UK GDPR, CCPA/CPRA and any state insurance regulation, before wahanx processes anyone's data commercially.
What we process
- Vehicle telemetry — speed, curvature or yaw rate, and timestamps, at a fixed sample rate.
- Forward-facing video, where a customer enables camera-derived signals.
- Trip and vehicle identifiers supplied by the customer, which may be pseudonymous.
What we do not want
- We do not require driver names, licence numbers or contact details to compute anything on this site.
- We do not require driver-facing video for any signal currently built or in build.
- We do not sell data to third parties, and we do not use customer data to train models for other customers without a written agreement.
Where processing happens
The detector is available as a library that runs entirely inside a customer's own environment, in which case no telemetry or video reaches us at all. Where the hosted API is used, payloads are processed to produce events and exposure, and retained only as long as the agreement specifies.
Roles
For fleet and carrier customers, the customer is normally the controller of driver data and wahanx is a processor acting on documented instructions. That allocation is set in the agreement, not by this page.
Contact
Privacy questions: privacy@wahanx.com.