SmartDriver for Android

Privacy Policy

Version dated 1 November 2026Effective upon publicationController: Reactive Phone LLC

This is an English translation provided for convenience. In case of any discrepancy, the Russian version prevails.

1. General

1.1. This Privacy Policy (the “Policy”) explains what data Reactive Phone LLC (ООО «Реактив Фон», the “Controller”, “we”) processes when you use the SmartDriver mobile application for Android (package com.smartdriver.antiradar, the “App”), for which purposes and on which legal grounds, who receives it, and what rights you have.

1.2. The Policy is drawn up in accordance with Russian Federal Law No. 152-FZ of 27 July 2006 “On Personal Data” (“152-FZ”) and other applicable Russian legislation. Where you use the App outside Russia, section 14 also applies.

1.3. The Policy covers the App, its server side and the App’s pages on reactivephone.ru. It does not cover third-party websites and services the App may link to (Google Play, etc.); those are governed by their own terms.

1.4. By using the App you confirm that you have read this Policy. Where your consent is required (see section 4), we ask for it separately, for example with a checkbox in the support form or when you enable a feature.

1.5. The Policy forms an integral part of the SmartDriver Terms of Use.

2. In short

No account requiredYou can use the App without signing up. Your email is only needed to restore previously purchased features on another device.
Location stays on your deviceCoordinates are processed inside the App to warn you about cameras. Routes and trip history are not sent to our servers.
No ads, no analyticsThe App contains no advertising and no advertising or marketing SDKs. We do not sell data or share it for advertising.
Video stays with youDashcam recordings are stored on your device and are never uploaded.
Crash reportsWe use Firebase Crashlytics (Google) to fix bugs. Reports contain technical data and no coordinates.
One address for everythingDelete your account and data, withdraw consent, ask a question: smartdriver@reactivephone.ru.

3. What data we process

3.1. The data depends on which features you use. All categories are listed below; most of them are processed only on your device.

3.2. Data sent to our servers

CategoryDetailsWhen
User and device identifiers User ID (a random string generated by the App on first launch), device ID, push notification token (app instance identifier), your promo code. On first launch and periodically afterwards, to link the status of previously purchased features to your device and deliver notifications.
Device and app information Device manufacturer and model, type (phone/tablet), Android version, App version and build variant, language and country, time zone, availability of Google Play services. Together with the identifiers, for correct operation and support.
Account data (optional) Email address (stored encrypted in the database); one-time confirmation code sent to that address; the link between the account and the devices signed in to it. Only if you create an account or sign in to restore previously purchased features.
Previously purchased features Identifiers and status of purchases made earlier through Google Play or the T-Bank payment service (product type, date, validity, store). Card details and payment credentials are never sent to or stored by us. When the premium status is verified or restored. No new purchases or renewals are made in the App; subscriptions taken out earlier remain valid until the end of the paid period.
Camera and road object reports Coordinates and type of the object, direction, speed limit, text name (if you enter one), device ID, time of submission. Only when you tap the button to add or edit an object. See 7.4: part of this data goes to the external camera database source.
Mobile ambush and police post reports Coordinates of the point, type, speed, heading and statistics of the current trip, country, premium status, device ID, time of submission; your confirmations or refutations of other users’ reports. Only when you tap the ambush report (or confirm/refute) button during a trip. Other users nearby see the point without any information about who reported it.
Support requests Your email, the text of your request and a technical block: promo code, user and account IDs, premium status, App version, device model and Android version, language and country, Google Play services availability, date, time and time zone, permission states (location, notifications), background mode, camera database date and size. Coordinates and trip history are not included. Only when you send a request through the “Support” form. The email is composed in your mail app and sent to smartdriver@reactivephone.ru.
Crash and performance reports Stack trace, device model, OS and App version, memory state, Firebase installation ID, pseudonymous user identifier, crash time; network request timing. Automatically when the App crashes (Firebase Crashlytics) and during network requests (Firebase Performance Monitoring).
Connection data IP address, request time, App version, in server logs. On every network request the App makes to our servers.

3.3. Data processed only on your device

  • Location (precise coordinates, speed, heading) during a trip and, if you enable background mode, in the background. Used to match your position with the camera database and give alerts. Not sent to our servers, except the coordinates of an object you report yourself or a mobile ambush you mark (3.2).
  • Trip history and statistics (distance, time, number of alerts) stored in the App’s local database.
  • Dashcam recordings and microphone audio (if audio recording is enabled) saved to the App’s folder in device storage or on the memory card. You manage them yourself: view, share and delete using your device.
  • Camera and road object database downloaded to and stored on the device.
  • Car Bluetooth device: only the name of the device you selected, to auto-start the App when it connects and to choose the audio output for alerts.
  • App settings.

3.4. Special categories and biometrics

We do not process special categories of personal data (health, ethnicity, political opinions, etc.) or biometric data. Dashcam recordings remain on the device and are not transferred to the Controller.

4. Purposes and legal bases

PurposeDataLegal basis
Providing the App’s features: camera alerts, database updates, background mode, dashcam Location (on device), identifiers, device information Performance of the Terms of Use (art. 6(1)(5) of 152-FZ); access to location, camera and microphone is granted by you through Android permissions
Creating an account and restoring previously purchased features on your devices Email, confirmation code, identifiers, purchase information Performance of the Terms of Use (art. 6(1)(5) of 152-FZ)
Delivering push notifications about the App (database updates, account status, important changes) Push token, identifiers, language, time zone Performance of the Terms of Use; notifications can be turned off in Android settings
Improving the camera database and mobile ambush reports with user contributions, showing current reports to other users Object coordinates and parameters, trip statistics, country, premium status, device ID Your action of submitting a report (implied consent, art. 6(1)(1) of 152-FZ) and the Terms of Use
Handling support requests Email, request text, technical block Consent (checkbox in the support form, art. 6(1)(1) of 152-FZ)
Detecting and fixing crashes, ensuring stability and security Crash reports, connection data Legitimate interests of the Controller in keeping the App operational (art. 6(1)(7) of 152-FZ)
Compliance with legal obligations, including requests from competent authorities Data required by law Art. 6(1)(2) of 152-FZ

4.2. We make no decisions with legal effects on you based solely on automated processing. We do not profile users.

5. Location and background mode

5.1. The App’s core function is to warn you about speed cameras and road objects. To do this, the App obtains your device’s precise location during a trip via Android and Google Play location services.

5.2. If you enable background mode, the App keeps receiving location and giving alerts while it is minimised or the screen is off, for example alongside a navigation app. Android asks for a separate background location permission for this, and a persistent notification is shown while the App is running. The App can also start automatically when your phone connects to the car Bluetooth device you selected, if you set up quick launch.

5.3. Coordinates are processed on the device, are not sent to our servers and are not stored as routes. Exception: the coordinates of an object you add to the database yourself or a mobile ambush you mark (3.2).

5.4. You can turn off background mode in the App settings or revoke the location permission in Android settings at any time. Without location access, camera alerts will not work.

6. What we do not do

  • We do not show ads and do not use ad networks or SDKs.
  • We do not use third-party marketing or product analytics or install attribution services. Google Analytics for Firebase event collection is disabled in the App.
  • We do not sell personal data or share it with third parties for their own purposes.
  • We do not collect or store routes, trip history or video recordings on servers.
  • We do not access your contacts, photos, messages or other apps on the device.
  • We do not accept payments in the App and do not process card details.

7. Who receives the data

7.1. Controller’s server side. The App’s server side (accounts, status of previously purchased features, user reports of road objects, notifications) runs in Google Cloud infrastructure rented by the Controller: the database is located in the European Union multi-region (eur3) and the application servers in the europe-west region. Mobile ambush reports are processed by a separate mobile points server of the Controller in the same infrastructure (Google App Engine, europe-west region; logs are kept for 30 days). Only the Controller has access to the data; Google acts as the infrastructure provider and processes data on the Controller’s behalf under the Google Cloud terms. Infrastructure audit logs (administrator actions, no content of user requests) are kept for 400 days.

7.2. Google LLC (USA) and its affiliates, as the provider of platforms built into the App:

  • Firebase Crashlytics and Firebase Performance Monitoring: crash and performance reports (3.2);
  • Firebase Cloud Messaging: push notification delivery (push token);
  • Firebase Remote Config: fetching App settings from the server (installation ID, version, language, country);
  • Firebase Realtime Database and Cloud Storage: showing mobile ambush and police post reports near your current position (the point is published without the device ID or any other information about who reported it) and loading images for App screens;
  • Google Play services: location, Google Maps on certain screens, update checks;
  • Google Play: verification of earlier purchases under Google Play rules.

Google’s processing is governed by the Google Privacy Policy and the Firebase privacy terms.

7.3. T-Bank payment service. For purchases made earlier through this service, the Controller receives the payment status to confirm previously purchased features. No new payments are accepted.

7.4. External camera database source. The camera and road object database is downloaded to the device from an external source. When you add or correct an object, the object’s coordinates and parameters and a pseudonymous device ID (3.2) are sent to that source. Your email, name or other information about you is not sent there.

7.5. Your mail app. Support requests are sent through the mail app installed on your device; delivery is handled by your email provider. Before 1 November 2026 support requests could be handled through the Usedesk service; from that date requests are accepted only by email at smartdriver@reactivephone.ru.

7.6. Public authorities, only in the cases and manner prescribed by law.

7.7. Processing by third parties on behalf of the Controller is carried out under contracts that comply with the confidentiality and security requirements of art. 6 of 152-FZ.

8. International transfers

8.1. The App’s server database is hosted in Google Cloud infrastructure in the European Union (7.1). Accordingly, account data (encrypted email address), identifiers, device information, the status of previously purchased features and mobile ambush reports are stored on servers in EU countries. By creating an account or otherwise providing data to the Controller through the App, you agree to such cross-border transfer.

8.2. When Firebase and Google Play services (7.2) are used, technical data (installation identifiers, crash reports, push token, device information, de-identified mobile ambush reports) is transferred to Google servers that may be located in the USA and other countries. The email address is not transferred to Firebase services.

8.3. The Controller takes the measures required by art. 12 of 152-FZ, including notifying the supervisory authority of its intention to carry out cross-border transfers of personal data.

9. Retention

DataPeriod
Account data (email, device links, premium status)While the account exists. Deleted within 30 days after you request account deletion, except data we must keep by law.
Records of earlier purchases (purchase identifiers and status, no payment credentials)5 years as required by accounting legislation, then deleted or anonymised.
Device records without an account (device identifiers and device information)3 years after the App’s last activity, then deleted or anonymised. Deleted earlier on request.
Push notification tokenWhile the App is installed on the device. After the App is uninstalled the token becomes invalid and is deleted together with the device record.
Road object reportsThe objects themselves (coordinates, type, parameters) are kept in the database indefinitely in de-identified form. The link between an object and the device ID is deleted after 1 year.
Mobile ambush and police post reportsWhile the point is relevant: a report’s rating decreases over time and with refutations, after which the point is deleted automatically. The link between a report and the device ID is deleted after 1 year.
Support requests3 years after the request is closed, unless the law requires otherwise.
Crash and performance reports (Firebase)90 days.
Server logs (IP address, request time)90 days; mobile points server logs: 30 days.
Data on the device (location, trip history, video, settings)Managed by you; removed when you clear the App’s data or uninstall it (recordings are deleted manually or by the loop recording settings).

9.2. When the purposes are achieved or consent is withdrawn, data is destroyed or anonymised unless the law requires otherwise.

10. Your rights

10.1. Under arts. 14, 20 and 21 of 152-FZ you have the right to:

  • obtain information about the processing of your personal data, including confirmation of processing, purposes, methods, retention periods and recipients;
  • request rectification, blocking or destruction of data that is incomplete, outdated, inaccurate, unlawfully obtained or unnecessary for the stated purpose;
  • withdraw your consent;
  • lodge a complaint with the supervisory authority for the protection of data subjects’ rights (Roskomnadzor) or with a court.

10.2. Send requests to smartdriver@reactivephone.ru. To help us find your data, include your account email and/or the promo code (identifier) shown in the “Account” or “About” section. We respond within 10 business days of receiving the request; if necessary, the period may be extended by up to 5 business days with notice to you of the reasons.

11. Deleting your account and data, withdrawing consent

11.1. Account and data deletion. In the App: Settings → Account → Delete account (deletion is confirmed with a code sent to your email). Alternatively, email smartdriver@reactivephone.ru from the address your account is registered to (or state your device promo code). We will delete the account, the identifiers linked to it and the premium status records within 30 days and confirm by reply.

11.2. Please note: after the account is deleted, previously purchased features can no longer be restored by email.

11.3. Withdrawing consent. Consent given when sending a support request can be withdrawn by email to the same address; the request and the data in it will then be deleted unless the law requires us to keep them. Location, camera, microphone and notification access can be revoked in Android settings; background mode is turned off in the App settings.

11.4. Data on the device is removed by clearing the App’s data or uninstalling it. Dashcam recordings are deleted in the App’s “Recordings” section or through the gallery or a file manager.

12. Security

12.1. The Controller applies the legal, organisational and technical measures required by arts. 18.1 and 19 of 152-FZ: data between the App and the servers is encrypted in transit (TLS); only authorised staff have access; access is role-based and logged; purchase data is stored without payment credentials; email addresses are stored encrypted (AES) in the database; email sign-in is confirmed with a one-time code.

12.2. No method of transmission or storage is completely secure. In the event of an incident affecting personal data, the Controller notifies the supervisory authority as required by art. 21(3.1) of 152-FZ.

13. Children

The App is intended for drivers and is not directed at persons under 18. We do not knowingly collect children’s personal data. If you become aware that a child has provided us with data (for example, created an account), email smartdriver@reactivephone.ru and we will delete it.

14. Users outside Russia

14.1. If you use the App outside the Russian Federation, the laws of your country may apply, including the EU General Data Protection Regulation (GDPR). In that case the legal bases are: performance of a contract with you (art. 6(1)(b) GDPR) for the App’s features and the account; your consent (art. 6(1)(a)) for support requests; the Controller’s legitimate interests (art. 6(1)(f)) for crash reports and security. You have the right to access, rectify, erase, restrict and port your data, to object to processing, and to lodge a complaint with the supervisory authority of your country.

14.2. The contact for all questions is the same: smartdriver@reactivephone.ru.

15. Changes to this Policy

15.1. We may update this Policy when the App’s features or the law change. The new version is published on this page with its date. For material changes (new purposes, new categories of recipients) we will also notify you in the App.

15.2. The previous version of the Policy, in force until November 2026, is superseded. Among other things, it stated that we did not collect email addresses; with the introduction of the optional email account, that statement has been replaced by section 3 of this Policy.

16. Contacts and company details

Legal name
Reactive Phone LLC (Общество с ограниченной ответственностью «Реактив Фон»)
Address
33, 6-ya Podlesnaya st., Izhevsk, Udmurt Republic, 426069, Russia
Tax ID (INN) / KPP
1831142285 / 183101001
OGRN
1101831003834
Email for data protection matters
smartdriver@reactivephone.ru
Person responsible for personal data processing
Ivan A. Semenov
Website
reactivephone.ru
Questions, data deletion, withdrawal of consent
smartdriver@reactivephone.ru