Privacy Policy

What we collect and why

Stored locally on your device only

• Vehicles you add (make, model, year)
• Service history entries (mechanic name, mileage, notes, cost, hours, parts)
• DTC scan history from your OBD-II adapter
• Live-data log samples during OBD polling
• Freeze frame data
• App preferences (unit preference, last-used adapter, dismissed tips, theme choice)
• Offline-saved repair guides
• Support chat conversation history (last 40 messages)

None of this leaves your device without your explicit action (share button, export CSV, or planned cloud sync).

Sent to third parties by the app

• NHTSA (nhtsa.dot.gov, vpic.nhtsa.dot.gov): VIN is sent to decode vehicle information; make/model/year is sent to check recalls and complaints. NHTSA is a US government agency with its own privacy notice.
• diyfixmycar.com backend: when you use the in-app AI support chat, your question, current vehicle context, and recent DTC codes are sent to our backend, which forwards to OpenAI. We log the question (first 200 characters), token counts, and cost — never any personal info like email or name. Rate-limited to prevent abuse.
• OpenAI (via our backend): support chat questions are processed by OpenAI's gpt-4o-mini model. OpenAI's API data usage policy applies. As of this writing, OpenAI does not use API inputs to train their models.
• Amazon (via affiliate links): when you tap a "Find on Amazon" button, your browser opens amazon.com with a search query and our affiliate tag. Amazon may set its own cookies per its privacy policy.
• Google (via fallback web searches): if you use the search feature to look up something specific, the search happens at google.com and their privacy policy applies once you leave the app.

What we do NOT collect

• No advertising IDs, no ad networks, no ad targeting
• No third-party analytics (no Google Analytics, no Firebase Analytics, no Mixpanel, no Amplitude)
• No location data beyond what Android requires for Bluetooth scanning (we mark our scan "neverForLocation")
• No microphone, camera, contacts, or messages access
• No third-party crash reporters

Bluetooth permission

The app requests Bluetooth permission to connect to your OBD-II adapter. On Android 12+, Bluetooth scanning requires location permission at the OS level — we mark our scan as neverForLocation so no location data is returned to us. We only use Bluetooth to talk to OBD adapters you explicitly select.

Account features (future)

When cloud sync launches (planned $1/month tier), it will require creating an account with an email address. That account and any synced data will be governed by an updated version of this policy, and the policy update will be surfaced in-app before any of your data syncs.

Children

The app is not directed at children under 13 and we do not knowingly collect information from them.

Your rights

• Delete: every screen where data is stored has a delete option. Uninstalling the app removes all locally stored data.
• Export: the live-data log has a "Copy as CSV" button. Service history and DTC scan export is planned.
• Request information: email [email protected] and we'll respond within 30 days.
• California residents (CCPA): you have the right to know what personal information we hold about you (answer: essentially none, per above), request deletion (uninstall the app), and not be discriminated against for exercising these rights. Contact [email protected].
• EU/UK residents (GDPR): same rights apply. We are the data controller. Legitimate basis for the (minimal) data processing above is Article 6(1)(b) — necessary for the service you asked for.

Changes

We'll update this policy when the app's data practices change. Material changes will be surfaced in-app.

Contact

Questions? [email protected]

---

See also: Terms of Service