Data Collection & Use Policy

1. Data minimization

Mobile Mechanic AI is designed to collect and process information reasonably needed to run repair-business workflows. Shops should avoid entering personal or confidential information that is unrelated to servicing a vehicle, communicating with a customer, operating the business, or using a requested integration.

2. Shop account data

Business name, owner/staff names, contact information, roles, plan, pricing defaults, branding, service area, and shop settings are used to create the tenant workspace, identify authorized users, personalize documents, apply permissions, support billing, and operate the account.

3. Customer and vehicle data

Customer names, phone numbers, email addresses, service locations, VINs, license plates, mileage, vehicle details, complaints, availability, and service history are used to create customer/vehicle records, route intake to the correct shop, prepare jobs, communicate with customers, document work, and maintain the vehicle timeline.

4. Job, diagnostic, and repair data

Complaints, technician findings, diagnostic codes, test results, measurements, repair recommendations, labor information, parts information, estimates, approvals, invoices, declined work, warranty/comeback records, and completion details are used to manage each repair workflow and produce shop/customer records.

5. Photos, files, voice, and scan data

When a user chooses to upload or capture media, the platform may process photos, receipts, documents, scan-tool reports, and other files. Voice input may be converted into text for complaints or technician findings. These items are attached only to the relevant shop/job context unless the user intentionally exports or shares them.

6. Location data

Location may be entered manually or obtained from the device after permission is granted. It is used for service addresses, travel planning, maps, scheduling, service-area checks, and nearby parts or service resources. The platform should not request precise location when the active feature does not need it.

7. AI processing

AI features may use the complaint, vehicle details, codes, findings, and other selected job context to generate pre-workups, checklists, explanations, estimate assistance, or second opinions. Only context reasonably related to the requested AI task should be sent. AI output is not a verified diagnosis and remains subject to technician review.

8. VIN, plate, service-history, and parts lookups

When a shop deliberately performs a lookup, the VIN, plate/state, vehicle identity, or parts request may be sent to the selected provider. Paid lookups may also record the shop, lookup type, cost, balance impact, and result metadata. CARFAX or similar service-history data may be transmitted only through an authorized connection when that integration is available.

9. Payments, subscriptions, and accounting

Platform subscription data and customer-payment workflow data are kept logically separate. Connected payment or accounting providers may receive the minimum information needed for an authorized transaction, invoice, customer sync, reconciliation, or bookkeeping action. Mobile Mechanic AI does not treat connecting an account as permission to perform unrelated transfers or exports.

10. Connected services and automation

A shop may choose to connect calendars, email, SMS, file storage, accounting, payments, maps, automation services, parts systems, or other providers. Data is sent to a connected service only when required for the feature the shop enables or an action the user requests. Connection tokens and provider identifiers are used only to maintain those authorized connections.

11. Staff access and tenant isolation

Records are tied to a shop identifier and are intended to be available only to authorized users for that shop, subject to role permissions. A technician should not receive owner-only financial or administrative information merely because the technician can work on a job.

12. Analytics, errors, and security events

Feature usage, error information, device/browser details, timestamps, and security events may be recorded to troubleshoot failures, improve reliability, enforce limits, detect abuse, and support the shop. These records should not be used to build advertising profiles from customer repair information.

13. Sharing and exports

Data can be shared with the shop's authorized staff, the customer receiving an estimate or record, a provider the shop connects, or a destination the shop deliberately chooses for export. Mobile Mechanic AI does not sell customer repair records for money or use them for cross-context behavioral advertising.

14. Shop responsibilities

Each shop is responsible for entering accurate information, limiting access to appropriate staff, obtaining customer permissions required by law, honoring customer privacy requests it is responsible for, securing its own credentials, and retaining records required for repair, tax, warranty, or regulatory purposes.

15. Retention and deletion

Data is retained as reasonably necessary for the active account, requested features, security, legal obligations, dispute resolution, backups, and required business records. Deleting or closing an account does not necessarily remove information immediately from backups or records that must be retained by law.

16. Changes

Material changes to the categories of data collected, the purposes of use, or sharing practices may require renewed acceptance. The current version is displayed at the top of this page.

17. Contact

Questions about data collection or use can be sent to support@mobile-mechanic.app.