App Privacy Policy

1. Controller and contact

The controller under the General Data Protection Regulation (GDPR) is:

You can contact us about data protection rights, access requests and withdrawal of consent at this address.

2. Purpose of the app

Deep DPF Inspect is a read-only vehicle diagnostic app focused on diesel particulate filters (DPF), regeneration, SCR/AdBlue and other available ECU data. It communicates with the vehicle via a suitable OBD adapter. The available measurements depend on the vehicle and the app version.

Vehicle data can be personal data, especially when it includes a vehicle identification number (VIN). This policy therefore also applies to vehicle-related information that can be associated with an individual.

3. Processing on your device

To connect to an OBD adapter and display readings, the app may process vehicle identity, ECU information, diagnostic responses, measurements, settings, connection status and necessary intermediate data on your device. Depending on the feature, it may cache data or store diagnostic history locally.

Local data is handled by the app and the operating system. Removing the app may remove stored data, while operating system backups follow separate policies. Bluetooth, Wi-Fi or other device permissions may be required depending on the connection method and platform.

4. Vehicle identification and server-side DID resolution

To identify the correct vehicle-specific diagnostic identifiers (DIDs), read parameters and decoding formulas, the app contacts our server. Once you have approved the relevant vehicle-specific data exchange in the app, the following categories may be transmitted and processed:

• vehicle identification number (VIN) and vehicle attributes derived from it;
• manufacturer, model and ECU identification, hardware and software identifiers where available;
• diagnostic protocols, ECU addresses, identified ECUs, supported identifiers and status flags;
• diagnostic responses requested for identification or matching, including any measurement and status values in those responses;
• technical connection details such as IP address, timestamps and request or error states.

The server uses this information to resolve the appropriate read commands, formulas, units and availability conditions. Vehicle identifiers, requests, diagnostic responses and matching results are also recorded in server-side database and log records when processed for the purposes described here. More than one request or diagnostic round may be needed. Without this exchange, automated vehicle-specific diagnostic coverage can be limited or unavailable.

Legal basis: Article 6(1)(b) GDPR where needed to provide the diagnostic function you request; additionally Article 6(1)(f) GDPR for secure operation and troubleshooting. Approval of regular vehicle resolution is distinct from the optional data sharing described in section 6.

The exchange with the server ends as soon as the app has received the vehicle-specific read plan. After that, the app does not send measurements or diagnostic values to this service during normal use. It only contacts the service again when you refresh the vehicle data or delete the stored vehicle data in the app. Measurements are shared only if you switch on the optional data sharing described in section 6.

5. Technical logs and security

To ensure the technical provision and security of the regular vehicle diagnostic and DID resolution service, server requests, timestamps, connection information, diagnostic metadata and error events may be processed. Diagnostic responses required for DID resolution are described in section 4.

Technical security and operational logging is based on Article 6(1)(f) GDPR.

6. Optional data sharing “Help improve the app”

In the app settings you can switch on “Help improve the app”. It is switched off by default. Data is only transmitted after you have confirmed the notice shown when you switch it on.

Purpose and your benefit. We use the shared data to improve the app’s vehicle support: we check whether values are matched and converted correctly, find and fix errors, and add values and vehicles. You benefit as well: your vehicle gets better support, may receive more values, and we can find and fix problems with your vehicle faster.

What data. While the feature is switched on and the app is connected to your vehicle, it transmits:

• the vehicle identification number (VIN);
• OBD support data: which OBD parameters your vehicle’s control units report (supported bitmaps) and the raw data of OBD parameters that contain support, selection or validity information, each with the control unit address – the first time and afterwards only when they change;
• the control units’ answers to the queries the app runs for your vehicle and to queries we set to check and improve support, including values the app does not show (yet): the query, the answer status (for example “not supported” or “not available yet”), the raw data of the answer and the values calculated from it. These queries are read once when the app connects and afterwards reported only when an answer changes. Answers that contain identification numbers (for example the VIN or control unit serial numbers) are transmitted with their status only;
• the values read by the app for the page currently shown: name of the value, value read, unit, source (manufacturer or standard OBD value) and read status – at most once per minute and when you switch to another page, only while the app is shown;
• app identifier, app version and build number;
• technical connection data such as IP address and time (see section 5).

The app only reads; nothing on the vehicle is changed. No location, contact or account data is transmitted.

Recipients. The data is sent encrypted to our server (separately from the vehicle identification described in section 4) and stored in a database there. Hosting providers process it as processors (section 7).

Our control. The app asks from time to time whether and which data we need from your vehicle. If we need no further data, the app stops sending data for this vehicle until we request data again.

Legal basis and voluntariness. The transmission is based on your consent (Article 6(1)(a) GDPR). It is voluntary. Vehicle identification and all app features remain available to you without this data sharing.

Withdrawal. You can withdraw your consent at any time with effect for the future by switching the feature off. The app then requests deletion of the data shared for your vehicle through this feature on our server; if no connection is available, it does so later. You can also request withdrawal and deletion by email to info@dancingbyte.de.

7. Recipients and international transfers

Technical hosting, server operations, infrastructure and where applicable error logging may involve service providers acting under our instructions. Where they process personal data on our behalf, Article 28 GDPR requirements apply. Other disclosures take place only when needed for the requested function, required by law or supported by valid consent.

App stores may process personal data independently when delivering or updating the app; their own privacy notices apply. Transfers of personal data outside the European Economic Area require appropriate safeguards under Articles 44 et seq. GDPR where applicable.

8. Retention and deletion

Local app data generally remains available for as long as it is held by the app or device operating system. Server-side requests, vehicle and diagnostic data and technical logs may be retained while needed for diagnostic matching, traceability of results, service security, troubleshooting and – where legally permitted – further development of the diagnostic service. Once no relevant purpose remains, personal data must be deleted or effectively anonymized, subject to legal obligations.

Actual retention and deletion processes depend on the relevant datasets and technical systems. You may request information about your personal data and applicable retention via info@dancingbyte.de.

Data from the optional data sharing described in section 6 is kept for no longer than 12 months from receipt and then deleted automatically. If you withdraw your consent, we delete it earlier. Our decision not to accept further data for a vehicle is kept, without the shared values, for as long as it is needed. You can request deletion of your app data here.

9. Data security

Protected connections and appropriate technical and organizational safeguards are used for communication with our services. No system involving OBD adapters, mobile networks and internet connections can guarantee uninterrupted or completely risk-free operation. Please use trusted adapters and secure your device against unauthorized access.

10. Your GDPR rights

Subject to the GDPR, you have rights of access (Article 15), rectification (Article 16), erasure (Article 17), restriction (Article 18), data portability (Article 20) and objection to processing based on legitimate interests (Article 21). You may withdraw consent with effect for the future at any time (Article 7(3)). You can also complain to a competent data protection supervisory authority (Article 77).

We may need proportionate verification that a request relates to data concerning you.

11. Contact, updates and scope

When you email us, we use the contact details and message to respond (Article 6(1)(b) or (f) GDPR). We update this policy when app features or processing change. Visiting the website is covered by the separate website privacy policy. Use of the app is also governed by the terms of use.