Optional diagnostic recording

Notice version 1 · 13 September 2026 · TAVOLON 0.8.53

This separate, optional setting extends the technical summary reporting described in section 8 of the Test Version Terms. Accepting the Terms alone does not enable detailed recording. You can use diagnosis without enabling this setting.

What is recorded

When you allow diagnostic recording in the app, TAVOLON captures instrumented program steps, searched file paths, file checks and loading results, timestamps, errors, and captured requests and responses between the app, VCI and vehicle. Events are associated with the VCI serial number, phone installation, app version and a diagnostic session. Diagnostic data may contain vehicle identifiers. Access credentials, sensitive security replies and programming payloads are omitted; screenshots and other images are not uploaded automatically.

Where it goes and how long it stays

Records are sent automatically over an encrypted connection to our server at motra.ml24shop.de, including when the app's background work runs. The additional local recording queue is limited to 8 MB and expires after 24 hours, with cleanup when the app or its background work runs. Offline records wait within these limits. Successfully acknowledged upload blocks are removed from the local queue. Server records expire after 3 days and are removed earlier after completed analysis or when storage limits require it. Existing technical summary reports keep their 24-hour retention; manually selected support attachments expire after 3 days and are removed earlier after completed analysis.

Your choice

The app asks before detailed recording is enabled. You may change your choice under Support → Diagnostic recording. Selecting “Decline” stops detailed recording and clears its local queue. Records already sent remain subject to the server retention period. This setting does not authorize advertising or unrelated data use. Contact TAVOLON Support for questions about your data.

Technical limits

The recording shows instrumented events, not every internal operation of every vehicle program. Closed native libraries may perform operations that do not expose a log or callback. Capacity limits, process termination and unavailable connections can leave gaps. Recorded success or a received response is not proof that every vehicle function is supported.

Existing Test Version Terms of Use