This Policy explains what data the D-Konnect application processes, why, who receives it, and what rights you have. It applies to every distribution channel (app stores and direct APK installation). Differences between store builds are listed in Appendix A and concern only the set of third-party components included.
Summary
- The app requires no account and no registration. We do not ask for your name, e-mail or phone number, and we do not create a server-side user profile.
- The app has no backend of our own. Vehicle readings, settings, indicators, formulas and measurement history are stored only on your device and are never sent to us.
- The app does not collect or store your geographic coordinates. The location permission is used to obtain speed and altitude from the system for the corresponding indicators.
- What does leave the device is anonymous technical telemetry (crash reports and aggregated launch statistics) and the data required by the ad network. The ad network is present in every build of the app; the rest of the third-party services depend on the distribution channel (Appendix A).
- We do not sell user data and do not share it with third parties for their own independent use, other than as described in sections 5 and 6.
Data processed and kept on your device
The following is stored in the app’s local databases and preference files. We have no access to it: it is sent neither to us nor to third parties.
| Category | What it is | Why |
|---|---|---|
| Vehicle profiles | profile name and its set of indicators | keeping settings separate per vehicle |
| Indicators and formulas | custom and predefined indicators, units, conversion formulas, OBD request (PID) configurations | rendering readings on the dashboard |
| Connection (source) configurations | adapter initialisation command sequences (e.g. ATZ, ATE0, ATSP0) |
correct handshake with a specific adapter |
| Vehicle data | values received from the OBD-II adapter (RPM, temperature, voltage, etc.) and values computed by your formulas | display and charting |
| Measurement history | a timestamped log of readings, errors and no-data markers; bounded in size, with the oldest rows removed automatically | charts, diagnostics, reviewing past trips |
| Known adapters | MAC address and display name of Bluetooth adapters you have connected to | quick reconnection and the known-devices list |
| App settings | interface and behaviour preferences | remembering your choices |
Vehicle identifiers. The app does not request a VIN and does not tie data to a vehicle automatically. If you create an indicator that reads the VIN or another control-unit identifier, that value is processed and stored locally, like any other reading.
Deletion. All of the above is removed when the app is uninstalled, and also via the system “Clear data” function (Settings → Apps → D-Konnect → Storage). Individual items (profiles, indicators, known adapters, history) can be deleted inside the app.
Device permissions and why they are needed
Permissions are requested only when needed, with the reason shown at the time of the request.
| Permission | Purpose | If denied |
|---|---|---|
Bluetooth scan (BLUETOOTH_SCAN) |
discover a nearby OBD-II adapter. Declared with the neverForLocation flag — the app does not derive location from Bluetooth scan results |
a new adapter cannot be discovered |
Bluetooth connect (BLUETOOTH_CONNECT) |
connect to the selected adapter and read its name | the adapter cannot be connected |
Location, approximate and precise (ACCESS_COARSE_LOCATION, ACCESS_FINE_LOCATION) |
obtain speed and altitude from the system for the corresponding indicators. Coordinates are not stored, not displayed and not transmitted | the speed and altitude indicators do not work; everything else keeps working |
Foreground service (FOREGROUND_SERVICE with the location and connectedDevice types) |
keep reading from the adapter and recording history while the screen is off or the app is in the background — that is, during a drive | recording stops when the app is backgrounded |
Notifications (POST_NOTIFICATIONS) |
show the mandatory notice that background recording is active | Android may restrict background work; recording becomes less reliable |
Any permission can be revoked in Android system settings at any time.
Data collected automatically while you use the app
The app processes operational data on the device and, to the extent described below, sends part of it to third-party services:
- Crash reports: device make and model, OS version, app version, stack trace, crash time and a short technical trail of recent in-app actions (for example, “connection started”, “adapter responded”). This trail contains no vehicle readings, no coordinates and no names you have typed.
- Aggregated usage statistics: app launches and session duration, which feed audience metrics (active users, retention). We do not send custom events containing your profiles, indicators or formulas.
- Identifiers: third-party SDKs generate their own installation identifier and may use the device advertising identifier. The installation identifier is reset on reinstall and is not linked to your identity.
The legal basis for this processing is the developer’s legitimate interest in keeping the app functional and stable (see section 8). This collection can be stopped by uninstalling the app; there is currently no separate in-app toggle.
Third-party services
The set of third-party components depends on the distribution channel of your build. The full list, with links to each provider’s policy, is in Appendix A. We pass these services only the data listed in section 4 and Appendix A; each provider processes it under its own policy.
Categories of services used:
- Crash reporting and technical diagnostics — required to ship stable updates.
- Aggregated usage analytics — audience-level metrics only.
- Advertising network — present in every build of the app. An ad network may process the advertising identifier, device information and approximate location derived from the IP address in order to select and count impressions. Ads are never shown on the dashboard screen while driving.
- App store payment processing — if purchases are available in your build (section 6).
AppMetrica as part of the ad SDK
The Yandex Mobile Ads SDK ships together with the AppMetrica library: it enters the app as a dependency of the ad SDK, in every distribution channel. How it behaves differs:
- in a build where the app activates AppMetrica with its own key, the service additionally performs the task declared for that channel — crash reporting and aggregated audience metrics (section 4);
- in a build where the app does not activate it with its own key, AppMetrica runs in a limited (“simplified”) mode: the app sends no events of its own through it, and the library processes only the technical device information and identifiers the ad SDK needs.
Which of the two modes applies to your build is stated in Appendix A.
The advertising identifier can be reset or opted out of in Android settings (“Privacy” → “Ads”).
In-app purchases
If your build offers paid features, payment is processed by the app store the app was installed from. Card details are entered in the store’s own interface: the developer does not receive, see or store them. The app receives only the fact that a purchase exists, in order to unlock the paid features. Refunds and payment disputes are governed by the rules of that store.
Backup and transfer to a new device
Android may include app data in system backup and in device-to-device transfer. The backup contains settings and configuration only: profiles, indicators, formulas, connection configurations, the list of known adapters (including their MAC addresses) and app preferences. Measurement history is excluded from backup.
The backup is handled by your device’s system backup service, not by the developer. Backup can be disabled in Android system settings.
Legal bases and applicable law
This Policy is written to satisfy the law of the jurisdictions the app is distributed in, in particular:
- Russian Federation: Federal Law No. 152-FZ of 27 July 2006 “On Personal Data”. No personal data is processed on the developer’s servers — there is no such infrastructure; local data is processed on the user’s device.
- EEA and United Kingdom: Regulation (EU) 2016/679 (GDPR). Legal bases: consent — for location access, Bluetooth access and personalised advertising (given through the system permission dialog or a dedicated consent screen); legitimate interest — for crash diagnostics and aggregated statistics needed to keep the app working; performance of a contract — for providing the app’s functionality and any purchased features.
The third-party services listed in Appendix A may process data outside your country; such transfers take place under those providers’ own terms.
Retention
- Local data is kept for as long as the app is installed and you have not deleted it; the measurement history is additionally bounded in size, and the oldest records are pruned automatically.
- Crash reports and statistics are retained by the service providers for the periods set in their policies (typically from several months to about 18 months).
Your rights
You may:
- be informed about what data is processed — this Policy is the complete list;
- delete your data — through in-app functions, through the system “Clear data” action, or by uninstalling the app; local deletion is complete and irreversible;
- withdraw permissions (location, Bluetooth, notifications) in Android settings;
- limit ad profiling by resetting or opting out of the advertising identifier in Android settings;
- contact the developer (see section 15 “Contact”) to request access, correction or erasure, or to complain. We respond within 30 days. Please note that, because the app has no accounts, we have no technical means to link an anonymous crash report to a specific person; in such cases we will help you delete on-device data and point you to the relevant provider;
- lodge a complaint with a supervisory authority in your country of residence (in the EEA/UK, your data protection authority; in Russia, Roskomnadzor).
Children
The app is intended for drivers and vehicle owners and is not directed at children under 16. We do not knowingly collect children’s data. If you believe a child has provided data to the developer, write to us at the address in section 15 “Contact” and it will be deleted.
Security
App data is stored in the app’s private directory, isolated from other apps by Android. The connection to the OBD-II adapter is local (Bluetooth); no internet connection is used to transfer vehicle data. Transmission to the third-party services listed in Appendix A is performed over secure channels by their SDKs.
No technical measure guarantees absolute security. If a vulnerability affecting users is discovered, we will disclose it in the update notes and, where necessary, through the app store.
Safety notice
The app displays on-board diagnostic data and is not a measuring instrument or a certified diagnostic device. Do not interact with the app while driving. The developer is not liable for decisions made on the basis of the app’s readings.
Changes to this Policy
We may update this Policy when the app’s functionality or its set of third-party services changes. The current version is always available at the address shown on the app’s store listing and in the app’s Settings screen. For material changes (a new category of collected data, or a new recipient) we will say so in the update notes. The version date is stated at the top of this document; earlier versions are available on request.
Contact
For any privacy or data protection question:
Appendix A. Third-party services by distribution channel
The following lists which third-party components are included in the build for each channel. A component not listed for a channel is absent from that build — its SDK is not shipped.
A.1. Google Play
| Service | Provider | Purpose | Data | Policy |
|---|---|---|---|---|
| Firebase Crashlytics | crash reporting | device model, OS and app version, stack trace, technical action trail, installation identifier | firebase.google.com/support/privacy | |
| Firebase Analytics | aggregated audience metrics (launches, sessions, retention) | automatically collected session events, installation identifier, advertising identifier (AD_ID) |
firebase.google.com/support/privacy | |
| Google Play Billing | in-app purchases, where available | the fact of a purchase; payment details are handled by the store | policies.google.com/privacy | |
| Yandex Mobile Ads | Yandex LLC | advertising | advertising identifier, device and network information, approximate location from IP, impression data | yandex.com/legal/confidential |
| AppMetrica (as part of the ad SDK) | Yandex LLC | technical support of the ad SDK | installation identifier and the device information the ad SDK requires | yandex.com/legal/metrica_termsofuse |
In the Google Play build AppMetrica is not activated with the app’s own key and runs in the limited mode (section 5): crash reporting and audience metrics in this channel are handled by the Firebase services.
A.2. RuStore
| Service | Provider | Purpose | Data | Policy |
|---|---|---|---|---|
| AppMetrica | Yandex LLC | crash reporting and aggregated audience metrics | device model, OS and app version, stack trace, technical action trail, installation identifier | yandex.com/legal/metrica_termsofuse |
| Yandex Mobile Ads | Yandex LLC | advertising | advertising identifier, device and network information, approximate location from IP, impression data | yandex.com/legal/confidential |
| RuStore billing | VK | in-app purchases, where available | the fact of a purchase; payment details are handled by the store | rustore.ru/help/rules |
In the RuStore build AppMetrica is activated with the app’s own key and runs in full mode: it is the same service that serves the ad SDK and, at the same time, the crash reporting and aggregated audience metrics service for this channel. It is not listed twice above.
A.3. Other distribution channels
Builds distributed by other means (direct APK installation, alternative stores) are covered by the same Policy. Such a build is produced from the same configuration as one of those described above, so section A.1 or A.2 applies to it accordingly. The advertising network is present either way. If a configuration with a different set of third-party services appears, it will be added to this Appendix when it is released.