Privacy Policy

1. Summary

Pure Dash does send two kinds of diagnostic and usage data to Google Firebase, a service we use to find out when the app is broken:

• Crash and error reports (Firebase Crashlytics) — stack traces and device state when the app crashes or hits a handled error.
• Basic usage analytics (Firebase Analytics) — anonymous counts of which features are used.

Neither carries your name, e-mail, contacts, messages, location history or any content you create. Each has its own on/off switch in Settings → About — both on by default — and both are described in detail in section 5.

Pure Dash contains no advertising, no ad SDK and no cross-app tracking, and does not collect an advertising ID.

This corresponds to a Google Play Data safety declaration of “Crash logs”, “Diagnostics” and “App interactions” collected, and “Device or other IDs” collected — not shared with third parties beyond our service provider, and not used for advertising or tracking.

2. Who we are

Pure Dash is created and supported by Compwiz Creations (“we”, “us”), https://compwiz.io. For the purposes of the EU/UK General Data Protection Regulation (GDPR), we are the controller of any personal data we receive from you.

In practice we receive none. The only circumstance in which we obtain personal data is if you choose to contact us directly (see section 10).

3. Data the app accesses on your device

The app reads the following data only on your device, only while it is running, and only to render the features you have enabled. None of it is uploaded, logged to a server, or retained beyond what is described below.

3.1 Location (GPS) — optional

The app reads only the speed value from the GPS fix. It does not record, store, or build any history of your coordinates, routes, journeys or places visited.

3.2 Media / “Now Playing” information — optional

Android requires notification-listener access to read media sessions. Pure Dash’s notification listener does not read, store, forward or act on the content of your notifications — messages, e-mails, alerts and their contents are ignored entirely. The listener exists solely so that Android will expose the active media session to the app.

3.3 Installed applications

Visibility is scoped to launcher-capable apps only; Pure Dash does not use the QUERY_ALL_PACKAGES permission and cannot see your full app inventory.

3.4 Images you choose (logo / wallpaper) — optional

If you set a custom logo or wallpaper, the app opens the Android system file picker. Only the single file you pick is made available to the app; Pure Dash stores a reference (URI) to it in its private settings and displays it. It is never copied off the device. The app has no broad storage permission and cannot browse your photos.

3.5 Screen brightness

3.6 Display over other apps

3.7 Device restart — GitHub sideload build only

The Google Play build contains no reboot feature, declares no accessibility service, and does not request Accessibility access.

The separately signed GitHub sideload build can show a Reboot button on rooted head units. It checks a fixed list of common su file paths locally. When a root binary is found, the button appears; it runs su -c reboot only after you tap the button and confirm. When root is unavailable, the button stays hidden. The command adds no new data collection; a failure can appear in the optional diagnostics described in section 5.1.

4. Data stored on your device

Pure Dash saves your preferences to Android’s private per-app storage (SharedPreferences, named PureDashPrefs), which is readable only by Pure Dash. This includes: chosen theme and accent colour, layout side, speed unit, the package names of your selected quick apps / navigation app / voice app / dock apps, the position of the floating music window, and references to any logo or wallpaper image you selected.

These are settings, not personal data about you, and they are permanently deleted when you uninstall the app. They stay on the device, with one narrow exception: a few of them (theme, accent, layout side, speed unit, how many quick-app slots are filled, and the package names of your navigation and voice apps) are attached to crash reports as diagnostic context — see section 5.1, and section 8 to turn that off. You can also clear them at any time via Android Settings → Apps → Pure Dash → Storage → Clear data.

5. Diagnostic and usage data we collect

Pure Dash targets unusual hardware — generic car head units whose ROMs frequently misreport what they can do. Without crash reports we have no way to learn that the app is failing on a particular unit. We therefore include two Google Firebase SDKs. This is the only data that ever leaves your device.

5.1 Crash and error reports (Firebase Crashlytics)

The “diagnostic context” row is deliberately specific because it includes the package names of two apps you chose. We attach them because “the navigation button does nothing” is unfixable without knowing which app it pointed at. Nothing else about your installed apps is sent.

5.2 Usage analytics (Firebase Analytics)

Analytics is switched off entirely on development builds, so only released versions report at all.

5.3 What we still never do

Pure Dash does not:

• collect your name, e-mail address, phone number, contacts or accounts;
• create user accounts or require registration;
• collect an advertising ID, or serve, target or measure advertising;
• track you across other apps or websites, or build a profile of you;
• sell or rent data to anyone, or share it for advertising purposes;
• perform automated decision-making or profiling within the meaning of GDPR Article 22.

Verbose diagnostic logging also exists in the source code for development; it is written only to the local Android log and only on development builds.

6. Legal bases (GDPR Article 6)

Because no personal data is transmitted to or processed by us, no processing by us requires a legal basis. For the on-device processing carried out by the app on your behalf, the applicable bases are:

• Consent (Art. 6(1)(a)) — for optional, permission-gated features: location for the speed widget, notification access for the music widget, the display-over-other-apps overlay, and access to an image you pick. Each is requested through Android’s own permission prompts and can be withdrawn at any time (section 8).
• Performance of a contract / legitimate interest (Art. 6(1)(b)/(f)) — for reading launchable apps and storing your settings locally, which are strictly necessary for a launcher to function.
• Legitimate interest (Art. 6(1)(f)) — for the crash reporting and usage analytics in section 5, whose purpose is keeping the app working on hardware we cannot test. We consider this proportionate because the data is pseudonymous, minimised to diagnostics, never used for advertising or profiling, and you can object to either kind at any time with its own switch in Settings (section 8).

Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal.

7. Retention, recipients and transfers

• Retention: location and media metadata are held in volatile memory only and are discarded immediately when the relevant widget stops displaying or the app closes. Settings persist on your device until you clear the app’s data or uninstall it. Crash reports are retained by Firebase Crashlytics for up to 90 days; analytics events are retained for the period configured in our Firebase project (currently 14 months for event data). We do not copy either into any system of our own.
• Recipients / processors: Google LLC / Google Ireland Ltd, acting as our processor for Firebase Crashlytics and Firebase Analytics under the Google Cloud / Firebase Data Processing Terms. No other recipient. We use no other cloud provider, hosting service or sub-processor.
• International transfers: crash and analytics data may be processed by Google on servers outside the EEA/UK. Google relies on the European Commission’s Standard Contractual Clauses, and on the EU-US Data Privacy Framework where applicable, as the transfer mechanism. Nothing else leaves your device.
• Security: on-device data stays within Android’s per-app sandbox, protected by the operating system’s isolation and by your device’s lock screen and encryption. Diagnostic uploads to Firebase are encrypted in transit (HTTPS/TLS).

8. Your controls and your rights

Controls in the app and in Android

• Turn off crash reporting: open Pure Dash → Settings → About and switch off “Send crash reports”. This stops the automatic crash handler as well as the handled-error reports — nothing further is sent from that point on.
• Turn off usage analytics: in the same place, switch off “Share anonymous usage data”.

  The two switches are independent, so you can keep crash reports on while opting out of analytics, or the reverse. Both are on by default. Reports already delivered cannot be recalled, because they carry no identifier that would let us find yours.

• Reset the diagnostic identifiers: Android Settings → Apps → Pure Dash → Storage → Clear data. This generates a new Crashlytics installation UUID and a new Firebase app-instance ID.
• Revoke location: Android Settings → Apps → Pure Dash → Permissions → Location.
• Revoke notification access: Android Settings → Apps → Special app access → Notification access → Pure Dash.
• Revoke overlay: Android Settings → Apps → Special app access → Display over other apps → Pure Dash.
• Revoke brightness control: Android Settings → Apps → Special app access → Modify system settings → Pure Dash.
• Erase everything the app holds: Android Settings → Apps → Pure Dash → Storage → Clear data, or simply uninstall the app.

GDPR rights

If you are in the EEA or UK you have the rights of access, rectification, erasure, restriction, portability and objection under Articles 15–22 GDPR, and the right to withdraw consent at any time.

The diagnostic data in section 5 is pseudonymous: it is keyed to a random, device-generated identifier and we hold nothing that links it to your name, account or device owner. Under GDPR Article 11 we are not required to acquire additional information purely to identify you, so in practice we usually cannot locate “your” reports in order to produce or delete them individually — which is also what limits how far that data can be used. You can achieve the same result directly and immediately by turning diagnostics off and clearing the app’s data, as described above.

If you have contacted us by e-mail and want that correspondence deleted, write to us at support@compwiz.io and we will erase it.

You also have the right to lodge a complaint with your national data protection supervisory authority.

California / US residents

We do not sell or share personal information as those terms are defined by the CCPA/CPRA — we do not disclose anything for monetary value, for cross-context behavioural advertising, or for any advertising purpose. We do not process sensitive personal information. The diagnostic and usage data in section 5 is collected solely to maintain and repair the app, and you can switch it off in Settings.

9. Children

Pure Dash is a car head-unit launcher intended for a general adult audience. It is not directed at children and contains no advertising. We do not knowingly collect personal data from children; the diagnostic data in section 5 is device-level and is not used to identify any individual, child or adult.

10. Contact

Questions about this policy or about privacy in Pure Dash:

We aim to respond to any privacy request within 30 days.

11. Changes to this policy

If Pure Dash’s data practices ever change, we will update this policy, revise the “Last updated” date above, and publish the new version at the same URL before the change takes effect in a released version of the app. Material changes affecting data collection will also be reflected in the app’s Google Play Data safety section.