Privacy policy

What BYDFixer collects, what it never collects, and what you can delete. Written from an audit of the app as built, not from intent.

What we collect

DataWhyWhere
Name and phone numberAccount and sign-inour server
EmailOptional, contact onlyour server
An app-generated device identifierBinds an account to one handsetdevice and our server
Fault codes and the selected vehicleTo fetch the matching repair stepssent with each request
Assistant conversationsTo show your past conversationsour server, 90 days, then deleted
Crash reportsTo fix what crashesSentry (United States)

What we do not collect

  • Photographs are never uploaded. VIN reading from the camera runs on the device via ML Kit; the image never leaves the phone and is not stored.
  • No location, no contacts, no photo-library access.
  • No advertising identifier, no tracking, no ads, no usage analytics.

Crash reports — what is stripped before sending

A crash report normally carries whatever was in the request. That is cut before it leaves: HTTP breadcrumbs are dropped entirely, the request and user objects are nulled, and no screenshots or view hierarchy are attached. What remains passes a scrubber that removes phone numbers, bearer tokens and 17-character VINs. A fault code is not scrubbed — it is what makes the report useful, and seven characters identify nobody.

Third parties

  • Google ML Kit — camera text recognition. Recognition is on-device, but the library sends its own usage and diagnostic data to Google.
  • Sentry — crash reports, after the scrubbing above.
  • Nobody else. No Firebase Analytics, no Crashlytics.

Your rights

In the app: Settings → Account → Delete account. It deletes the account and its conversations. You can also clear only the copy held on your phone, which deletes nothing on the server. Contact us on WhatsApp: +963 958 330 862.

Transport

All traffic is HTTPS. The app refuses cleartext (usesCleartextTraffic is off) and does not participate in automatic backup (allowBackup=false).