Privacy Policy

1. Scope

This Privacy Policy applies to Driver Assist. The application provides read-only vehicle diagnostics through a user-provided OBD-II adapter and an AI-powered automotive assistant.

Driver Assist offers optional Firebase Authentication accounts for the AI Assistant. An account is not required for local diagnostics. Driver Assist does not display advertising, sell personal information, or use vehicle data for advertising.

2. Data stored locally on your device

Driver Assist stores the following information locally so that the application can operate:

• adapter connection settings, such as the selected connection type, Bluetooth device address, or Wi-Fi endpoint;
• your analytics and crash-reporting choices;
• application preferences;
• diagnostic logs, which may contain raw OBD/ELM responses, error details, and technical stack traces.

Application backups are disabled. Local data remains on the device until you clear it in the application or Android settings, or uninstall the application. Diagnostic logs leave the device only when you explicitly choose to share an exported report with another application or recipient.

3. AI Assistant

When you use the AI Assistant, Driver Assist sends information needed to answer your request through the Driver Assist service hosted by Cloudflare to the Gemini Developer API provided by Google. This may include:

• your messages and recent conversation context;
• a limited summary of earlier messages;
• the assistant's generated responses; and
• read-only vehicle information requested by the assistant, such as supported metrics, current readings, diagnostic trouble codes, and readiness status.

Driver Assist does not intentionally include Bluetooth names or addresses, Wi-Fi configuration, or raw OBD/ELM transport logs in assistant requests. Do not enter personal information that is not needed for your automotive question.

The service verifies Firebase Authentication and App Check tokens before processing an assistant request. It does not store prompts, responses, diagnostic values, or tool results in its quota and session database. Google processes assistant inputs and outputs to provide the Gemini service under its applicable terms and data-governance rules.

Cloudflare necessarily processes the network address and ordinary request metadata needed to receive, protect, and route HTTPS requests. Persistent Worker invocation logs are disabled. Aggregate Workers Analytics and temporary, bounded security diagnostics do not contain authentication tokens, assistant messages, diagnostic or vehicle content, tool arguments, or tool results.

To enforce a daily question limit after account deletion and recreation, the service derives a pseudonymous HMAC-SHA-256 quota identifier from a server-verified Google provider identity or a verified normalized email address. The raw Google provider identifier, email address, authentication tokens, and HMAC secret are not stored in the quota database or ordinary service logs. Firebase UID remains separate and is used to isolate active assistant sessions and requests.

4. Optional assistant feedback

You may voluntarily send positive or negative feedback about a specific assistant response. Before submission, the application explains what will be included. A feedback report may contain:

• the selected rating category and optional comment;
• the reported assistant response and up to 19 preceding conversation messages, with a maximum of 20 messages total;
• the diagnostic tool calls and result data used to create that response;
• the model name, application version, language, submission time, and technical context counts.

Feedback is stored in Google Cloud Firestore and is used only to review and improve assistant quality and safety. Feedback content is not sent to Firebase Analytics. The Android client cannot read, update, or delete submitted feedback records.

5. Optional analytics and crash reports

Usage analytics and crash reporting are disabled by default and controlled by separate choices during first launch and in Settings.

If you enable usage analytics, Firebase Analytics receives limited product events such as screen views, connection outcomes, feature selections, durations, and safe technical counts. Analytics events do not include assistant messages, adapter identifiers, VINs, ECU identifiers, diagnostic trouble-code values, raw vehicle responses, live vehicle readings, or diagnostic logs.

If you enable crash reporting, Firebase Crashlytics may receive crash and ANR information, stack traces, application version, device model, operating-system information, and Firebase installation or session identifiers. Driver Assist does not intentionally attach assistant content, vehicle data, adapter details, or diagnostic logs to crash reports.

You can withdraw either choice at any time in Settings. Withdrawing crash-reporting consent also requests deletion of unsent reports held by the application.

6. Permissions and security

Driver Assist requests Bluetooth connection permission only when it is needed to list paired adapters or connect to a selected Bluetooth device. The application does not request location permission. Internet access is used for Wi-Fi adapter connections and Google Firebase services.

Firebase Authentication identifies signed-in assistant users. Firebase App Check with Google Play Integrity is used in production to help verify legitimate application requests and prevent abuse. These processes may transmit authentication or integrity tokens and technical app or device signals to Google. Data sent to Firebase and the Driver Assist service is encrypted in transit, and supported services encrypt stored data at rest.

7. Service providers and international processing

Driver Assist uses Google services including Firebase Authentication, Cloud Firestore, Firebase Analytics, Firebase Crashlytics, Firebase App Check, Google Play Integrity, and the Gemini Developer API. It uses Cloudflare Workers and D1 to verify assistant requests, enforce quotas, and maintain bounded session metadata. Google and Cloudflare process data as service providers under their applicable terms and privacy documentation. Depending on the service, information may be processed in countries other than your own.

We do not sell your information. Information is disclosed only to service providers needed to operate the features you use, when you explicitly share data through another application, or when required by applicable law.

8. Retention and your choices

• Local settings and logs remain on your device until cleared or the application is uninstalled.
• Assistant feedback is retained for up to 12 months to review and improve assistant quality and safety, and is then deleted. A specific report may be retained longer only when reasonably necessary to investigate abuse, protect security, or comply with a legal obligation.
• Analytics and crash data is retained according to the configured Firebase settings and Google's applicable service terms.
• Pseudonymous daily quota records are retained through the active UTC quota window and a two-day cleanup margin, including after Firebase account deletion, to prevent quota evasion. Expired rows are removed by bounded service cleanup.
• Active assistant sessions expire after 15 minutes. Request and idempotency metadata expires after 24 hours. This metadata contains hashed Firebase UID ownership, random identifiers, timestamps, counters, and bounded status codes, but no conversation or vehicle content.

See Account deletion for the in-app process and the external request option.

9. Account deletion

The in-app deletion action first removes assistant sessions, requests, idempotency records, model-call reservations, and tool-call metadata associated with the verified Firebase UID. It then deletes the Firebase Authentication account and clears the local sign-in credential state.

The pseudonymous quota record is not immediately removed. It remains only for the active UTC quota window and bounded cleanup margin to prevent a daily limit from being reset by deleting and recreating an account. Aggregate global counters also remain and cannot identify an account.

Assistant feedback is submitted without a Firebase UID and therefore is not automatically linked to or deleted with an account. You may request review or deletion of reasonably identifiable feedback by contacting us with its approximate submission date and non-sensitive details. Do not send passwords, authentication tokens, or vehicle diagnostics.

10. Children's privacy

Driver Assist is not designed or marketed to children. If you believe that personal information has been submitted by a child through the application, contact us using the details below so that we can review the matter and take appropriate action.

11. Changes and contact

We may update this policy when application features, service providers, or legal requirements change. The current version and its effective date will remain available at this address.