Privacy policy for EzRadar
This is a draft for an app that is not yet released. It is based on the 0.17.0 build specs and will be rechecked against the release build before it is finalized.
Who we are
This policy is for the Android app EzRadar, to be published by TestaDura Labs. It describes what the app can access on your device and what is done with that access.
What the app accesses
- Wi-Fi state (read and request scans). Reads Wi-Fi scan results the phone already has. The app never joins a network.
- Precise and approximate location. Android requires location access to return Wi-Fi and Bluetooth scan results. Also used for optional map Follow and reported-camera alerts. Location stays on the phone. There is no background-location permission.
- Nearby Wi-Fi devices (Android 13 and newer). Wi-Fi scanning.
- Bluetooth scan and connect (legacy Bluetooth permissions on Android 11 and older). Passive Bluetooth LE scanning and device names, and, only if you start it, a read-only link to a Valentine One Gen2 radar detector.
- Notifications and foreground services. Scanning, optional camera alerts, the optional detector link and the recorder run only with a visible notification and Stop.
- Camera and microphone. Only for the emergency recorder you start yourself.
- Biometric. Optional unlock for the app’s own PIN lock.
- Internet and network state. Only for optional Online features. HTTPS only; cleartext is blocked.
What we collect
We do not collect, receive or sell any personal information from this app. Nothing is sent to TestaDura Labs. There are no ads, analytics or crash-reporting SDKs.
Network use
With About → Online features off, the app makes no network requests. When you turn them on, the app uses HTTPS to allow-listed official public traffic and camera hosts only — for example Caltrans and CHP in California, and the state transportation departments for the other traffic layers you turn on. Some of those layers need a developer key you paste in yourself; it is encrypted on the phone and sent only to that agency. Those servers see your IP address and the file requested, like any web request. The app sends no identifiers, location, scan data or recordings.
Data stored on your device
On the phone only: observed device records and signal history, rules, nicknames, recordings (in app-private storage), app-lock settings, map packs and any developer keys you paste in. No route history is stored. Android backup is turned off. Uninstalling the app deletes its app data.
Third-party services
No ads, analytics or crash reporting. Bundled data includes the public IEEE registry, OpenStreetMap data (© OpenStreetMap contributors, ODbL 1.0; most plate-reader pins mapped via DeFlock), and official city and Caltrans lists. Official traffic and camera images belong to the agencies that publish them. Licences are listed in the app’s Sources.
Children
The app is not directed at children under 13 and does not knowingly collect personal information from anyone.
Changes
If this policy changes we will update this page and the effective date. A further update is expected when the app is released.
Contact
For questions about this policy, contact: [CONTACT EMAIL TBD].