Your privacy on the road

Radarbot 2.0 helps you explore camera coverage, follow your measured speed and keep optional journey records. This policy explains the rebuilt iPhone and Android app and its services. Use the Radarbot support page for privacy questions or requests.

Location and records on your device

Radarbot uses location permission to show your position, measure speed and identify approaching mapped cameras during a drive. Background location is used only when you enable background driving and start a drive. Stop the drive or change the permission in system settings to stop this access.

Saved places, recent destination selections and optional journey history are stored on your device. Precise route recording requires your history and route-recording choices. You can delete saved places, recent searches and journey history from their screens or Settings. Deleting local history does not remove copies you previously exported.

Map display requests go to OpenFreeMap and its map infrastructure. Those services receive normal connection information, including your IP address and the map areas requested. Searching sends the place or address you enter to your device's map provider; on iPhone, the visible map area also helps rank results. Choosing Directions passes the destination to Apple Maps or an available Android navigation app. Those providers apply their own privacy policies.

GPX export requires confirmation and a save location you choose. The file contains precise recorded coordinates and the journey start time. Anyone you give it to can read that information. Radarbot cannot delete copies outside the app.

Optional AI reflections

A reflection is requested only after you confirm the disclosure for that journey. Radarbot's service receives aggregate distance, duration, moving time, maximum measured speed, camera-alert count and signal-gap count. It does not receive the route, saved places, destination search or exact locations.

The service converts these totals into broad categories, such as a short journey or recorded signal gaps. OpenRouter and its selected OpenAI or Google model providers receive those categories to generate a reflection. Requests exclude providers that OpenRouter classifies as collecting request data. This setting does not promise that every service keeps no operational or security records. See OpenRouter's data policy.

The service stores the generated reflection, request identifiers and a digest of the request. If you report a reflection, it stores your chosen reason and any comment you supply. Do not include personal information in a report. Reflections can be wrong and are not navigation or driving advice.

Service identity and protection

Using protected AI features creates an anonymous Firebase Authentication identity and an installation identity. Firebase App Check, Apple App Attest or Google Play Integrity help verify requests. The service retains the installation's public verification key, request timing, replay-prevention records and a hashed network grouping to enforce usage limits and prevent abuse. Service providers also process ordinary network and technical information needed to deliver requests. No AI provider key is stored in the app.

Purchases and subscriptions

Apple or Google processes payments and subscription management. Radarbot checks native store ownership to enable purchased features. We do not receive your payment-card details. On iPhone, the existing Qonversion service observes subscription transactions and processes purchase history, device attributes and app/device identifiers for subscription analytics. It does not receive your route or saved places. See Qonversion's privacy information.

Deleting app or AI data does not cancel a store subscription. Use Manage subscription in Settings or your store account to manage billing. Restore purchases remains available independently of optional analytics choices.

Optional diagnostics and attribution

Usage analytics and crash reporting start off and have separate Settings controls. If enabled, Google Firebase receives feature-use events or technical crash information and device/application information. App-authored events exclude routes, coordinates, place names, search text and reflection content. Turning either choice off stops its future collection; it does not erase information already processed by that provider. Privacy requests can be made through Support.

On iPhone, Share marketing attribution is a separate optional choice. Meta and Apple Ads attribution through Qonversion are enabled only after your choice and Apple's tracking permission allow it. These services may process app/device identifiers and app or purchase activity to measure advertising. Routes and saved places are excluded. You can turn this choice off in Radarbot or withdraw tracking permission in iOS Settings. No core feature requires advertising permission.

The app checks whether WhatsApp is installed solely to decide a one-time rating invitation. The result stays on the device; Radarbot does not open WhatsApp, read its contents or upload the check result.

Optional iPhone notifications

Enabling Service notifications allows registration with Apple Push Notification service and Firebase Messaging. They process a device-registration identifier to deliver app messages. Turning the choice off stops registration and requests deletion of the Firebase messaging registration. This control is separate from spoken driving warnings. You can also change notification permission in iOS Settings.

Delete or request your data

Settings provides Delete AI account and data independently of paid access. It retires the installation, removes stored reflections and reports, and requests deletion of the Firebase identity. Interrupted deletion can be retried. Minimal hashed ownership, request and retirement records remain to prevent replay and abuse; they are not retained journey content.

Before uninstalling, Save a deletion code in Settings provides a private code for the online AI deletion page. Keep that code private. Without the app or code, contact Support; anonymous records may not be identifiable from a name alone.

Local records stay until you remove them or the app's local data is removed. Reflections and reports remain until AI deletion. Store transaction records, provider security records and data already processed by analytics or attribution services follow their respective retention obligations and policies. Contact Support for access, correction or deletion requests concerning those services. Support form information is used to respond to your request. Do not send payment credentials or precise journey files unless needed for the help you request.