Processed locally
- High-frequency motion readings
- Three-second roughness calculations
- Impact detection and severity
- Drive distance and live app statistics
Data transparency
See what leaves the phone.
Sucky Roads is built to measure pavement, not people. These are the current Android beta's live aggregate totals and the categories of information used to build the road map.
1contributing installations
256road events
80.6 KBestimated telemetry transfer
323 Bestimated per road event
61.6 KBexact JSON payload
80.6 KBestimated cellular
0 Bestimated Wi-Fi
13batched uploads
On-device processing
The raw sensor stream stays on the phone.
High-frequency motion readings are processed on the device into compact road samples and probable-impact events before upload.
Sent to Sucky Roads
- Processed road samples and impact events
- GPS location, accuracy, speed, and event time
- App version and phone model
- Network type and bandwidth counters
- A random app-install identifier
Random install ID
The app generates a random identifier so uploads from the same installation can be grouped during beta testing. It is not a phone hardware or advertising identifier. The server stores a one-way hash of it.
Public map privacy
The public map uses road-condition evidence only. It does not expose installation identifiers, individual device histories, or the private batch records used for beta diagnostics and Fleet planning.
Why these fields exist
Each one has a road-measurement job.
Place the reading
Location, accuracy, speed, and event time place evidence on the correct stretch of pavement.
Score the road
Roughness, peak movement, and impact strength help classify measured road conditions.
Measure data cost
Network type, batch size, and bandwidth counters help size future Fleet cellular plans.
Public vs. private: the private admin dashboard can separate installations and upload batches for troubleshooting. This page intentionally publishes aggregate totals only.