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 consent to an optional supporter contribution program.

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 supporter data contribution – planned

This additional feature has not yet been implemented. We plan to allow supporters to actively choose to contribute real vehicle measurements and related technical information to improve existing coverage, investigate faults and add support for further vehicle models.

Before activation, the app should explain the specific data, scope, purpose, recipients and retention criteria. Any such contribution must rely on separate, freely given, informed and withdrawable consent under Article 6(1)(a) GDPR. Withdrawal must be possible for future transfers. Participation must not be a requirement for the regular technically necessary DID resolution feature.

This website does not collect supporter consent and does not claim that the feature is already available.

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. Additional specific rules must be finalized before any supporter contribution feature is activated.

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.