RoadSense exists to publish a community road-quality map, not to build profiles of individual drivers. This page explains what the app collects, what it does not collect, how long data is kept, and what controls contributors have before anything reaches the public map.
Last updated: April 24, 2026.
01 · What we collect
Only the signals needed to score roads
When a contributor opts in, the iPhone can collect accelerometer data, precise location, speed, headings, timestamps, and limited crash/performance diagnostics. The backend also sees network metadata needed to operate the service, such as IP addresses for rate limiting, but those fields are not part of the public map.
Why this data existsWe use motion plus location to match roughness samples to roads.Without those two signal types together, the service cannot tell whether a bump happened on Barrington Street, Robie Street, or in a driveway that should never be published.
02 · What we don't collect
No account, no ads, no personal profile
RoadSense does not ask for your name, email, phone number, home address, or a user account to contribute road-quality data. It does not use advertising IDs, ad trackers, or session replay tools.
The public web app is read-only. It does not expose raw traces, contributor identifiers, or per-driver history.
03 · On-device filters
Your home never leaves your phone
RoadSense filters privacy zones on-device before upload. The public web app is read-only and never exposes raw traces, contributor identifiers, or account-level history.
Built in, not bolted onZones are evaluated locally in the app.Drive samples inside a zone are discarded before the upload queue is even touched. The server never receives a signal that a zone exists near you.
04 · Retention and deletion
Short-lived raw data, longer-lived aggregates
Contributors can delete all local data from inside the app at any time. On the server, raw drive samples are kept for up to 6 months and then deleted on a rolling basis. Aggregate road-quality outputs may remain longer because they are published community statistics rather than personal trip histories.
Because RoadSense does not use accounts, some server-side data cannot be tied back to a known person in the way a typical consumer app can. That is a deliberate privacy choice, not an excuse to be vague about retention.
05 · Web experience
No trackers, no session replay
The web interface does not use ad trackers or session replay tools. It exists to explain community road conditions, not to build behavioral profiles on visitors.
Published road-quality and coverage views use aggregated segment-level data only. Individual drives cannot be isolated from the public surface; per-contributor activity stays server-side and is used only to recompute the aggregates you see here.
06 · Contact and requests
Questions, corrections, and privacy requests
Contributors can wipe their local contribution data from inside the app at any time. If you have a privacy question, a correction request, or want to challenge how this policy is being applied, contact graham.mann14@gmail.com.
We will answer in plain language. If the implementation changes in a way that affects what data is collected or published, this page will be updated before broader public testing.
Want a per-source view with live counts? See Privacy & counts — every telemetry source named, with current aggregates from the public stats view.