Privacy policy

What BYDFixer collects, what it never collects, and what you can delete. It covers the whole product — the app and this website — and is written from an audit of both 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)

The website — account creation and card payment

This policy covers the whole product, and the website collects what the app does not.

DataWhy
Name, phone number, passwordCreating an account on the website. The phone number is the identity; the password is stored hashed (scrypt), never as text
A browser identifierA random value the site generates and keeps in localStorage on your device, sent with sign-in and registration
Tap's charge id, the amount, currency, payment status and a referenceProof that a subscription was paid for

About the browser identifier: its only purpose is to bind a subscription to one browser so accounts are not shared. It is not linked to browsing behaviour, is never given to a third party, is released by an administrator on request, and is deleted with the account. It does not occupy a device slot, so registering on a laptop does not lock your handset.

About payment: your card details never reach us. Payment happens on Tap's own hosted page; there is no card field on our site, and we store no card number or any part of one.

Account-level subscription: an activation window with a start and end date on your account, opened by a payment or by an administrator. It is not tied to any particular vehicle.

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.
  • Tap Payments — card payment on the website. Your card details go to Tap's own page; we never see them. It is not used in the app.
  • Nobody else. No Firebase Analytics, no Crashlytics, no advertising.

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).