Skip to main content

Privacy Policy

Effective Date: October 14, 2026
Last Updated: October 14, 2026 (consumer invite beta: recent-chat recall, photos, how to request access and deletion during the beta)
Company: DriveAI LLC
Product: DriveTrace
Website: https://drivetrace.ai

DriveAI LLC (“DriveAI,” “we,” “us,” or “our”) operates DriveTrace, an app in which you chat with an AI assistant (“Trace”) about your vehicle. We are also building services for auto repair shops, fleets and developers. Where this policy describes those services, it applies only when they are offered to you. During the current invite-only beta, DriveTrace is offered to individual vehicle owners only. This Privacy Policy describes how we collect, use, disclose, and retain personal information (“PI”), and explains the rights available to you under the California Consumer Privacy Act as amended by the California Privacy Rights Act (“CCPA/CPRA”) and, where applicable, the General Data Protection Regulation (“GDPR”).

This policy applies to all users of our services, including:

  • Auto repair shop operators and technicians who use DriveTrace for diagnostic analysis
  • Fleet managers who use DriveTrace for vehicle health monitoring
  • Vehicle owners whose data is processed through our platform, including via the Free Diagnosis Portal
  • Developers who access our diagnostic API

1. Categories of Personal Information We Collect

Under the CCPA/CPRA, “personal information” means information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular consumer or household. We collect the following categories of personal information:

CCPA Category Examples We Collect Collected
A. Identifiers Name, email address, phone number, username, account ID, Firebase UID, IP address, API key identifiers, organization ID Yes
B. Personal information under Cal. Civ. Code 1798.80(e) Name, telephone number, address Yes
C. Protected classification characteristics None intentionally collected No
D. Commercial information Subscription plan, billing history, service history (dates, costs, provider names, invoice numbers), API usage records Yes
E. Biometric information None intentionally collected. Audio recordings of vehicle engine sounds may incidentally capture voice characteristics or ambient sounds, but these recordings are collected solely for vehicle diagnostic purposes and are not used for biometric identification. No (see Section 6)
F. Internet or electronic network activity Log data, IP addresses, browser type, User-Agent headers, pages visited, API call history, interaction patterns Yes
G. Geolocation data Approximate location derived from IP address; geographic region associated with diagnostic sessions; precise geolocation data that may be present in CAN FD vehicle bus data (see Section 6) Yes
H. Sensory data Photos you send in chat (for example of your vehicle; they may show license plates, people or places). Yes
I. Professional or employment information Business name, organization name, role or title (for shop operator and technician accounts) Yes
J. Education information None No
K. Inferences drawn from PI Diagnostic predictions, confidence scores, vehicle health assessments, repair recommendations, severity and urgency levels generated by our AI and machine learning models Yes
L. Sensitive personal information Account credentials (password hashes — we never store plaintext passwords); precise geolocation that may be present in CAN FD data (see Section 6) Limited
Vehicle-Specific Data

We collect the following vehicle-related data, which may constitute PI when it can be linked to an identifiable individual:

  • Vehicle identifiers: Vehicle Identification Number (VIN), license plate number
  • Vehicle attributes: Make, model, year, engine type, fuel type, transmission, mileage, color, nickname, purchase date, warranty expiration, insurance policy number
  • Service history: Service dates, costs, service provider names, technician names, invoice numbers
  • OBD-II data: Diagnostic trouble codes (DTCs), live sensor data (RPM, coolant temperature, fuel trim, throttle position, O2 sensor readings), freeze frame data, fuel metrics
  • CAN FD data: Controller Area Network Flexible Data-rate raw bus frames, decoded signals, and DBC-decoded vehicle parameters
  • Audio recordings: Engine and driveline sound files you attach, where the app accepts them
  • Diagnostic results: AI-generated predictions, confidence scores, interpretations, recommended actions, severity levels
  • Photos and files you send: photos of your vehicle or its parts sent in chat.

VINs and license plate numbers can be linked to vehicle owners through public records and are treated as personal information throughout their lifecycle.

2. Sources of Personal Information

We collect personal information from the following sources:

  • Directly from you. When you create an account, submit a diagnostic request, enter vehicle information, send photos or other files, submit feedback on diagnostic results, or contact us.
  • From a sign-in provider you choose. If you sign in with an account from another company, such as Google, that company shares your name, email address and an account identifier with us, and may share your profile photo. We use them to set up your account and sign you in.
  • From your auto repair shop, dealership, or fleet operator, where we offer services to them. Business customers may submit vehicle data and diagnostic requests on behalf of vehicle owners.
  • From your vehicle. Through OBD-II scanners and CAN FD diagnostic hardware connected during diagnostic sessions.
  • From the Free Diagnosis Portal, when it is offered. You may upload a scan-tool report, which we read and do not store, with your vehicle’s make, model and year.
  • From our API. When developers submit diagnostic data through the DriveTrace API on behalf of their end users.
  • Automatically from your device. When you use our website or APIs, we automatically collect log data, IP addresses, and usage information.
  • From our payment processor. Stripe provides us with subscription status and billing event data. Stripe handles payment card information directly; DriveAI never receives or stores raw payment card numbers.
  • Generated by our systems. Our AI and machine learning models generate diagnostic predictions, confidence scores, and repair recommendations based on the data you and your service provider submit.
3. How We Use Personal Information

We collect and use personal information for the following business and commercial purposes:

Purpose Categories of PI Used
Continuing your conversation. When you start a new chat, Trace may include up to 30 messages from your three most recent chats (the same vehicle first) so it can pick up where you left off, instead of starting from zero. Chats you archive are not included. Chat history (the text of your messages and Trace’s replies).
Providing diagnostic services. Analyzing vehicle data (OBD-II codes, CAN FD data, sensor readings) and photos you send using AI and machine learning models to generate diagnostic reports and repair recommendations. A, D, G, H, K, vehicle data
Account management. Creating and maintaining your account, authenticating your identity, and managing your subscription and preferences. A, B, L
Billing and payments. Processing subscription payments and usage-based billing through Stripe, generating invoices, metering API usage, and maintaining financial records. A, D
AI and ML model improvement. Training and improving our diagnostic AI and machine learning models using anonymized and de-identified diagnostic data, audio recordings, and CAN FD data to increase diagnostic accuracy. H, K, vehicle data (anonymized)
Communication. Sending account-related notifications, diagnostic reports, service updates, and responding to your inquiries. A, B
API access and developer services. Providing programmatic access to diagnostic services for integration with shop management software and third-party applications. A, D, F
Security and fraud prevention. Detecting, investigating, and preventing unauthorized access, security incidents, and fraudulent activity. A, F, L
Analytics and service improvement. Understanding how users interact with our platform to improve functionality, user experience, and service reliability. F, G, K
Quality assurance. Reviewing diagnostic accuracy, monitoring model performance, collecting user and mechanic feedback, and resolving disputes about diagnostic results. D, K, vehicle data
Legal compliance. Complying with applicable laws, regulations, legal processes, and governmental requests, including tax and financial record-keeping obligations. A, B, D

We do not use personal information for purposes materially different from those described above without providing you with notice.

4. Sharing and Disclosure of Personal Information

We disclose personal information to the following categories of third parties, solely for the business purposes described in this policy:

Category of Third Party Purpose Data Disclosed
Cloud infrastructure provider (Google Cloud Platform) Hosting, computing, storage, database, and logging services. All DriveAI infrastructure runs on GCP in the us-west1 (Oregon) region. All categories of PI listed in Section 1 are stored and processed on GCP infrastructure.
Authentication provider (Google Firebase) User authentication, identity management, and session token issuance. Identifiers (email, name, phone number, UID), account credentials.
Payment processor (Stripe) Subscription billing, payment processing, invoice generation, and usage-based metering. Name, email address, subscription status, usage records. Stripe independently collects payment card details and billing address directly from users; DriveAI never receives raw card data.
AI and LLM providers (Google Gemini; secondary providers may include Anthropic and OpenAI) Natural language processing for diagnostic interpretation, chat-based diagnostic interaction, and report generation. Chat messages, photos you send in chat, and diagnostic data are sent to Google (Gemini) to generate answers. When you start a new chat, recent messages from your earlier chats are sent as context (see Section 3). We do not send your email address or account identifiers to the provider; your first name is included so Trace can address you.
Your auto repair shop, dealership, or fleet operator Delivering diagnostic results to the business that submitted the request on your behalf. Diagnostic reports, vehicle data, repair recommendations.

All third-party service providers are contractually bound to use personal information only for the purposes of providing services to DriveAI and are prohibited from selling, retaining, using, or disclosing it for their own purposes. We maintain Data Processing Agreements (DPAs) with our service providers.

We may also disclose personal information:

  • If required by law, regulation, subpoena, court order, or other legal process
  • To protect the rights, property, or safety of DriveAI, our users, or the public
  • In connection with a merger, acquisition, or sale of all or a portion of our assets, in which case you will be notified via email or prominent notice on our website of any change in ownership or uses of your personal information
5. Sale and Sharing of Personal Information

DriveAI does not sell personal information. We have not sold personal information in the preceding 12 months and have no plans to do so.

DriveAI does not share personal information for cross-context behavioral advertising. We do not disclose personal information to third parties for the purpose of targeted advertising.

Use of Data for AI and ML Model Training

We use anonymized and de-identified diagnostic data, audio recordings, and vehicle telemetry to train and improve our AI and machine learning diagnostic models. This data is stripped of all direct and indirect identifiers (including user IDs, VINs, and free-text personal information) before use in model training. This use of de-identified data does not constitute a “sale” or “sharing” under the CCPA/CPRA.

If you wish to opt out of having your diagnostic data used for model training — even in anonymized form — you may do so by:

  • Email: Send a request to privacy@driveaitech.com with the subject line “Opt-Out of Training Data Use”
  • Account settings: When available, use the privacy controls in your DriveTrace account dashboard

We will honor your opt-out request within 15 business days. Opting out will not affect the quality of diagnostic services you receive.

DriveTrace Individual Subscribers — Continuous Data and the “Hybrid” Learning Posture

If you use a DriveTrace Individual account (Free or Pro), you provide vehicle data on a continuing basis (for example, through a connected OBD-II dongle, uploaded CAN-bus log dumps, sensor/telematics readings, and your service log), and DriveAI LLC is the data controller for that data. For company-wide AI/ML improvement we apply a Hybrid consent posture:

  • De-identified, aggregate learning is ON by default (opt-out). Unless you opt out, we use a de-identified, aggregated version of your diagnostic data to improve our models. It is de-identified before use, and no single subscriber may make up more than 15% of any training aggregate. As above, de-identified use is not a “sale” or “share.” You may opt out anytime in account Privacy Settings or by emailing privacy@driveaitech.com, with no effect on your service.
  • EU/UK/CH residents: OFF by default. If you reside in the EU, the UK, or Switzerland, company-wide ML training on your data is off unless you explicitly turn it on (GDPR consent). This jurisdiction gate is enforced at the training pipeline, not just in the interface, and it fails closed: if we cannot corroborate your residency, we treat you as EU/UK/CH (training off) until it is established.
  • Identifiable use and third-party sharing are OFF unless you opt in. We will not use data that still identifies you, or share it with any third party, for anything beyond delivering the service you requested, unless you give a separate affirmative opt-in.

The specific consent instrument and signup controls for the Individual tier are described in DriveAI’s ML Training Data Consent (Variant A-2) and Portal Consent Language documents, and summarized in the Supplemental Notice for DriveTrace Individual Subscribers below.

Erasure timelines (how the deadlines fit together). The deletion windows in this policy are sequential stages of one process, not conflicting deadlines: we honor a training opt-out within 15 business days (above), purge training-stage data within 30 days (Section 7), and complete a full verified erasure within 45 days (Section 9, the outer response bound). The 15-business-day and 30-day steps fall inside the 45-day envelope, subject to the trained-model carve-out and the legal/financial retention exceptions in Section 7.

Marketplace Routing (DriveTrace Individual) — Treated as a “Sale”/“Share”

When DriveTrace Marketplace Routing is available and you opt in, we may share identifiable data (your contact details, vehicle information, approximate location, and pre-inspection summary) with a partner repair shop so it can provide you a quote or booking. Because a partner shop pays DriveAI a per-lead fee when we route you, we treat Marketplace Routing as a “sale” and “share” of personal information under the CCPA/CPRA. Accordingly, for this use:

  • We obtain your affirmative opt-in before any routing occurs, and you may opt out (withdraw) at any time; withdrawal stops all future routing.
  • We honor “Do Not Sell or Share My Personal Information” requests and Global Privacy Control (GPC) signals for this use.
  • Matching is merit-based (location, make/model expertise, skill-tier fit, availability); shops cannot pay for higher ranking, and any sponsored or promoted result is clearly labeled as an ad (FTC).
  • Marketplace Routing is not directed at, and is not offered to, individuals under 18.

Marketplace Routing may not yet be live in all areas; where it is not, no data is shared until it launches. When Marketplace Routing is active, the “Do Not Sell or Share My Personal Information” mechanism described in Section 8 applies to it.

Except for Marketplace Routing (above, and only when you opt in), we do not sell or share personal information as defined under the CCPA/CPRA. Until Marketplace Routing is live for your account, a general “Do Not Sell or Share My Personal Information” link is not otherwise required; if our practices change further, we will update this policy and provide the required opt-out mechanisms before any such sale or sharing occurs.

6. Sensitive Personal Information

Under the CCPA/CPRA, “sensitive personal information” includes certain categories of data that receive heightened protection. DriveAI collects the following categories that may qualify as sensitive personal information:

Account Credentials

We collect and store password hashes (using bcrypt with per-user salts) for account authentication. We never store plaintext passwords. Account credentials are used solely for the purpose of authenticating you to the DriveTrace platform.

Precise Geolocation

CAN FD vehicle bus data captured during diagnostic sessions may contain GPS coordinates or other precise geolocation signals embedded in the vehicle’s onboard systems. Additionally, geographic region data associated with diagnostic sessions (e.g., state or metropolitan area) is collected to support regional diagnostic pattern analysis.

  • Precise geolocation from CAN FD data is collected only during active diagnostic sessions and only when the diagnostic hardware captures it from the vehicle’s bus.
  • We do not use precise geolocation for tracking your movements, building location profiles, or any purpose unrelated to vehicle diagnostics.
  • Geographic data is generalized to state-level resolution before use in any anonymized training datasets.
Audio Recordings and Biometric-Adjacent Data

Audio recordings of engine and vehicle sounds may incidentally capture voice characteristics or ambient sounds. While we do not collect these recordings for the purpose of biometric identification, we recognize that certain jurisdictions (such as Illinois under BIPA) may treat voice recordings as biometric data. During the invite-only beta, the app does not accept audio uploads.

Your Right to Limit Use of Sensitive Personal Information

You have the right to limit our use of sensitive personal information to uses that are necessary to perform the services you have requested. To exercise this right, contact us at privacy@driveaitech.com. DriveAI does not use sensitive personal information for any purpose beyond what is necessary to provide and improve our diagnostic services.

7. Data Retention

We retain personal information only as long as reasonably necessary to fulfill the purposes for which it was collected, comply with legal obligations, resolve disputes, and enforce our agreements. Our specific retention periods are:

Data Category Retention Period Rationale
Account data (name, email, phone, username, Firebase UID, login history, preferences) Duration of active account + 30 days after account deletion request CCPA/CPRA right to erasure (1798.105); 30-day grace period aligns with the 45-day response window.
Vehicle data (VIN, license plate, make, model, year, service history) 2 years from last activity on the vehicle record Data minimization; supports longitudinal diagnostic accuracy. Deleted immediately on account deletion regardless of activity date.
Audio recordings (engine sound WAV files and associated metadata) 1 year from the date of recording Data minimization; limits biometric-adjacent data exposure while providing sufficient ML training data refresh cycles.
Diagnostic sessions and results (session metadata, AI predictions, confidence scores, OBD-II data, interpretations, recommended actions) 2 years from session creation date Business necessity for customer access to diagnostic history, warranty evidence, and product liability defense.
Chat history (LLM conversation messages between you and the diagnostic assistant) 1 year from message date Data minimization; chat messages have high PI density from free-text input. Chat history is also used for recent-chat recall (Section 3) while it is retained.
Photos and files you send in chat Deleted 180 days after upload, then permanently erased within 7 days, and deleted with your account Data minimisation; photos can show people, plates or places.
Usage and analytics data (API usage events, interaction patterns, UX metrics) 1 year from event date Data minimization; supports billing dispute resolution and capacity planning.
Firestore diagnostic interaction data (raw diagnostic data, user feedback, mechanic verdicts, geographic context) 2 years from document creation date ML training pipeline source data; aligned with MySQL diagnostic session retention.
CAN FD raw data (raw bus frames, decoded signals, vehicle telemetry) 1 year from collection date Data minimization; high-volume data with vehicle-specific signatures that constitute indirect PI.
Payment and billing records (Stripe customer mappings, subscription records, DPA acceptances) Duration of active subscription + 7 years after subscription end or account deletion IRS statute of limitations (26 U.S.C. 6501); California FTB requirements; CCPA exemption 1798.145(d) for financial record-keeping. Financial records are anonymized (not deleted) on account deletion and retained for 7 years.
Application logs (IP addresses, request URLs, User-Agent headers) 30 days Cloud Logging automatic expiry; per-user deletion not technically feasible in log infrastructure. Our cloud provider also keeps administrative audit records (Admin Activity, System Event and Access Transparency logs) for 400 days; this is fixed by the provider and cannot be shortened. These records log administrative and system actions (who changed what configuration, from which IP address), not users’ messages. When an administrative action is taken on a user’s account, the entry may identify that account. When we delete your account or data, we keep a record of the deletion, including any failed attempt, in our application logs for 30 days. The record does not include your name or email address. We keep a list of the files being deleted only until the deletion is confirmed complete (about 8 days), and then destroy it.
Password reset and verification tokens Consumed on use; expired tokens purged after 7 days Security hygiene.
ML training data provenance records (training dataset manifests, model lineage, anonymization status) Retained indefinitely Non-PI metadata required for audit trail integrity, AI regulatory compliance, and IP protection. Updated with tombstone entries when source PI is deleted.
Records of deletion requests 24 months after the request is completed To show that we honored your request. The record has no name or email address.

After the applicable retention period, personal information is permanently deleted or irreversibly de-identified so that it cannot be linked to an individual. De-identified data may be retained indefinitely for ML model training, aggregate analytics, and algorithm improvement.

When you request account deletion, all personal information is deleted within 30 days, except: (a) financial records, which are anonymized and retained for 7 years as required by law; and (b) ML training data provenance records, which are updated with a tombstone notation but do not themselves contain personal information.

Copies of your data may remain in our encrypted backups for up to 7 days after deletion, after which they are overwritten. Backups are not used to restore deleted accounts.

8. Your Rights Under the CCPA/CPRA

If you are a California resident, you have the following rights regarding your personal information:

Right to Know (Access)

You have the right to request that we disclose:

  • The categories of personal information we have collected about you
  • The categories of sources from which your personal information was collected
  • The business or commercial purposes for collecting your personal information
  • The categories of third parties with whom we have disclosed your personal information
  • The specific pieces of personal information we have collected about you

You may make a verifiable Right to Know request up to twice in a 12-month period.

Right to Delete

You have the right to request that we delete the personal information we have collected from you, subject to certain exceptions permitted by law. We may deny a deletion request if retaining the information is necessary to:

  • Complete a transaction or provide a service you requested
  • Detect security incidents or protect against malicious, deceptive, fraudulent, or illegal activity
  • Debug or repair functionality
  • Comply with a legal obligation, including tax and financial record-keeping requirements (see Section 7)
  • Use the information internally in ways reasonably aligned with your expectations based on your relationship with us
Right to Correct

You have the right to request that we correct inaccurate personal information that we maintain about you. We will use commercially reasonable efforts to correct the information as directed, taking into account the nature of the personal information and the purposes of the processing.

Right to Opt-Out of Sale or Sharing

You have the right to opt out of the sale or sharing of your personal information for cross-context behavioral advertising. As stated in Section 5, DriveAI does not currently sell or share personal information as those terms are defined under the CCPA/CPRA.

Right to Limit Use of Sensitive Personal Information

You have the right to limit our use and disclosure of sensitive personal information to uses that are necessary to perform the services or provide the goods you have requested, or as otherwise permitted by law. See Section 6 for details on the sensitive PI we collect and how we use it.

9. How to Submit a Privacy Request

During the invite-only beta, requests to access, export, correct or delete your data are handled by our team: email privacy@driveaitech.com. To delete your chats, delete your account or ask us to remove a specific chat. The app does not yet offer deleting a single chat, and the self-serve data export does not yet include your chat history; we include it when you ask us. We respond within the timelines below. To keep a chat out of what Trace sees, archive it. Archiving does not delete it. When you delete your account during the beta, you are signed out and can no longer sign in. We keep your data for three weeks so you can change your mind: email privacy@driveaitech.com within three weeks of your request and we will reopen your account with your chats and vehicles as they were. If you had Pro, it is not restarted; you can subscribe again. You will need to sign in again on each device. If you do not ask us to reopen it, we complete the deletion of your data within 30 days of your request and email you when it is done.

You may submit a privacy request through either of the following channels:

Verification

To protect your privacy, we must verify your identity before fulfilling a request to know, delete, or correct your personal information. Our verification process:

  1. We will ask you to confirm the email address associated with your account.
  2. We’ll email you to confirm we got your request, and we may ask you to reply from the email on your account so we know it’s you. We aim to get back to you quickly — and always within the time the law allows (45 days under the CCPA).
  3. For requests to access specific pieces of PI or to delete PI, we may require additional verification steps.

If we cannot reasonably verify your identity, we may be unable to fulfill your request. We will explain the reason for any denial.

Authorized Agents

You may designate an authorized agent to submit a request on your behalf. If you use an authorized agent, we require:

  • Written authorization signed by you, or a power of attorney
  • Verification of the agent’s identity
  • We may still verify your identity directly, unless the agent provides a valid power of attorney
Response Timeline

We will acknowledge receipt of your request within 10 business days. We will respond to verified requests within 45 calendar days. If we need additional time (up to an additional 45 calendar days), we will notify you of the extension and the reason for it.

Requests Through Your Auto Repair Shop

If your data was submitted by a partner auto repair shop, dealership, or fleet operator, you may also submit your privacy request through that business. They are contractually obligated to forward such requests to us for processing.

Appeal Process

If we deny your privacy request in whole or in part, you may appeal the decision by emailing privacy@driveaitech.com with the subject line “Privacy Request Appeal.” We will respond to appeals within 60 calendar days.

10. Non-Discrimination

DriveAI will not discriminate against you for exercising any of your privacy rights under the CCPA/CPRA or any other applicable privacy law. We will not:

  • Deny you services
  • Charge you different prices or rates
  • Provide you a different level or quality of service
  • Suggest that you will receive a different price, rate, or quality of service

for exercising your rights.

11. Financial Incentive Programs

DriveAI does not currently offer any financial incentive programs (such as loyalty programs, discounts, or other benefits) that are related to the collection, retention, sale, or sharing of personal information.

If we introduce any such programs in the future, we will update this policy to describe the material terms of the program, including how you can opt in and how you can opt out, and the method we use to calculate the value of the personal information involved.

12. Cookies and Tracking Technologies
Cookies We Use

When you visit drivetrace.ai, we may use the following types of cookies and similar technologies:

Type Purpose Duration
Strictly necessary cookies Authentication session management (Firebase Auth tokens), security (CSRF protection), load balancing Session or short-lived
Functional cookies None in the invite-only beta. A few interface settings, such as whether a side panel is collapsed, are kept in your browser’s local storage instead, and you can clear them in your browser. Not applicable
Analytics cookies None in the invite-only beta Not applicable
What We Do Not Use
  • We do not use third-party advertising or retargeting cookies.
  • We do not participate in cross-site behavioral tracking networks.
  • We do not use tracking pixels for advertising purposes.
  • We do not use fingerprinting techniques to identify users across sites.
Managing Cookies

You can control cookies through your browser settings. Most browsers allow you to refuse or delete cookies. Disabling strictly necessary cookies may impair the functionality of the platform (for example, authentication may not work).

Do Not Track

Some browsers transmit “Do Not Track” (DNT) signals. There is no industry standard for how companies should respond to DNT signals. DriveAI does not alter its data collection or use practices in response to DNT signals because we do not engage in cross-site tracking of our users.

13. Information for International Users (GDPR)

If you are located in the European Economic Area (EEA), the United Kingdom (UK), or Switzerland, this section provides additional information about how we process your personal data under the General Data Protection Regulation (“GDPR”) or the UK General Data Protection Regulation (“UK GDPR”).

Data Controller

For direct users of the DriveTrace platform, DriveAI LLC is the data controller. Where diagnostic data is submitted by an auto repair shop, dealership, or fleet operator on behalf of a vehicle owner, that business is typically the data controller and DriveAI acts as a data processor. In such cases, the relationship is governed by our Data Processing Agreement.

Legal Bases for Processing

We process personal data based on the following legal grounds under Article 6 of the GDPR:

Legal Basis Processing Activities
Performance of a contract (Art. 6(1)(b)) Providing diagnostic services, managing your account, processing payments, delivering diagnostic reports
Legitimate interests (Art. 6(1)(f)) Improving our AI/ML diagnostic models (using anonymized data), ensuring platform security, preventing fraud, internal analytics. Our legitimate interests do not override your fundamental rights and freedoms.
Legal obligation (Art. 6(1)(c)) Complying with tax and financial record-keeping requirements, responding to lawful governmental requests
Consent (Art. 6(1)(a)) Where required, such as for analytics cookies if we introduce them in the future, or for marketing communications beyond service-related notifications. You may withdraw consent at any time without affecting the lawfulness of processing prior to withdrawal.
Your Rights as a Data Subject

Under the GDPR, you have the following rights:

  • Right of access (Article 15) — Request confirmation of whether we process your personal data and obtain a copy of it.
  • Right to rectification (Article 16) — Request correction of inaccurate personal data.
  • Right to erasure (Article 17) — Request deletion of your personal data where certain grounds apply (also known as the “right to be forgotten”).
  • Right to restriction of processing (Article 18) — Request that we restrict the processing of your personal data in certain circumstances.
  • Right to data portability (Article 20) — Receive your personal data in a structured, commonly used, machine-readable format (JSON or CSV).
  • Right to object (Article 21) — Object to processing of your personal data based on legitimate interests or for direct marketing purposes.
  • Rights related to automated decision-making (Article 22) — Our AI/ML diagnostic models produce automated outputs (diagnostic predictions, severity assessments, repair recommendations). These outputs are informational tools intended to assist qualified technicians; they are not used to make decisions that produce legal or similarly significant effects on individuals without human involvement. You have the right to request human review of any automated output that materially affects you.

To exercise any of these rights, contact us at privacy@driveaitech.com or submit a request through https://drivetrace.ai/privacy-request.

Cross-Border Data Transfers

DriveAI processes and stores all personal data in the United States, specifically in Google Cloud Platform’s us-west1 (Oregon) region.

You send your personal data directly to us in the United States. Where the GDPR or UK GDPR applies to us, we protect that data as described in this policy, and our service providers that process it (Section 4) do so under contracts that include the European Commission’s Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) or the UK International Data Transfer Addendum, or under their own participation in the EU-U.S. Data Privacy Framework.

If you would like a copy of the applicable transfer mechanism, please contact us at privacy@driveaitech.com.

GDPR privacy contact

For questions or concerns about our processing of personal data under the GDPR, contact us at:

Supervisory Authority

If you are located in the EEA or UK, you have the right to lodge a complaint with your local data protection supervisory authority if you believe our processing of your personal data violates the GDPR.

14. Data Security

We implement technical and organizational security measures designed to protect personal information from unauthorized access, destruction, use, modification, or disclosure. These measures include:

  • Encryption in transit: All data is encrypted in transit using TLS
  • Encryption at rest: Google-managed encryption (AES-256 equivalent) for all databases (Cloud SQL, Firestore) and storage systems (GCS)
  • Access controls: Firebase Authentication for user access; HMAC-SHA-256 hashed API keys for programmatic access; internal services accept requests only from inside our network with Google-issued service identity tokens; backend services additionally verify a shared secret
  • Password security: Passwords are hashed using bcrypt with per-user salts. Plaintext passwords are never stored or logged. Legacy SHA-256 hashes are transparently upgraded to bcrypt on login.
  • Infrastructure security: All services run on Google Cloud Run (serverless, ephemeral containers) with VPC-native networking. Our databases are reachable only on a private network, and every connection is encrypted with certificate-verified TLS. Our customer-facing ingress sits behind Google Cloud Armor edge filtering.
  • Credential management: All secrets, API keys, and database credentials are stored in Google Cloud Secret Manager, never in source code or configuration files
  • Data segregation: User-scoped database queries enforce tenant isolation, preventing cross-user or cross-organization data access
  • Photo metadata: When you upload a photo that we keep, such as a photo in a chat, we rebuild it from its image alone, so the photo we store carries no file information such as camera details or location (GPS). If a photo can’t be processed this way, we don’t keep it. Photos you send only to read a VIN or a receipt are read in memory and never stored.
  • Incident response: We maintain incident response procedures and will notify affected users of a data breach as required by applicable law

No method of transmission over the internet or electronic storage is completely secure. While we use commercially reasonable means to protect your personal information, we cannot guarantee absolute security.

15. Children’s Privacy

DriveTrace is designed for adult vehicle owners (and, where offered, businesses). You must be at least 18 to create an account. Our services are not directed at children under the age of 16, and we do not knowingly collect personal information from children under 16, nor from any child under 13 (COPPA).

If we learn that we have inadvertently collected personal information from a child under 16, we will take prompt steps to delete that information. If you believe that a child under 16 has provided personal information to us, please contact us at privacy@driveaitech.com.

We do not sell or share the personal information of consumers under 16 years of age, nor do we have actual knowledge of doing so.

16. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. When we make changes:

  • We will update the “Last Updated” date at the top of this policy.
  • We will post the revised policy on our website at https://drivetrace.ai/privacy.
  • For material changes that affect how we handle personal information, we will notify registered users via email at least 30 days before the changes take effect.

Your continued use of our services after the effective date of a revised policy constitutes acceptance of the changes. If you do not agree with the revised policy, you may delete your account.

Supplemental Notice for DriveTrace Individual (Consumer) Subscribers

This supplemental notice applies specifically to individuals who hold a DriveTrace Individual account (Free or Pro) for personal, non-commercial use. It supplements — and where it addresses the same topic, controls over — the general policy above for those subscribers. Where diagnostic data is instead submitted by a shop, dealership, or fleet on your behalf, that business is typically the controller and our Data Processing Agreement governs.

1. We are your data controller. For your DriveTrace Individual account, DriveAI LLC is the data controller. Your relationship is directly with us — there is no shop or business intermediary.

2. What we collect on a continuing basis. Beyond account and billing data, your account may continuously collect: OBD-II diagnostic codes and live sensor readings; CAN-bus / CAN FD log dumps you upload; telematics and vehicle-health signals; your service and maintenance log; and the diagnostic sessions and pre-inspection summaries you generate. Categories, sources, sensitive-data handling, and security are as described in Sections 1, 2, 6, and 14 above.

3. How your data is used — the Hybrid posture. See Section 5 (“DriveTrace Individual Subscribers”). In short: your data is always used to deliver your own diagnostics; a de-identified, aggregate version is used to improve DriveTrace for everyone on by default (opt-out), except OFF by default for EU/UK/CH residents; and identifiable use or third-party sharing (including Marketplace Routing) is off unless you opt in.

4. Marketplace Routing. If and when you opt in, sharing your identifiable details with a partner shop is treated as a “sale”/“share” under the CCPA/CPRA (a per-lead fee is involved). You may opt out anytime; we honor GPC signals; matching is merit-based; ads are labeled. See Section 5 (“Marketplace Routing”).

5. Retention. Your continuous vehicle data follows the retention periods in Section 7 (e.g., diagnostic sessions 2 years, CAN FD and audio 1 year, account data through account life + 30 days). De-identified training data follows the Data Retention Schedule.

6. Your choices, in one place. During the invite-only beta, some of these controls are handled by our team on request (see Section 9). From your account Privacy Settings you can, at any time and without affecting your service or subscription: opt out of company-wide learning; grant or withdraw identifiable-data use; grant or withdraw Marketplace Routing; and exercise your rights to access, correct, delete, export (portability), and limit sensitive-PI use. EU/UK/CH residents additionally have the GDPR rights in Section 13, and DriveAI’s processing of your data relies on the lawful bases set out in the ML Training Data Consent (Variant A-2) instrument.

7. Age. DriveTrace Individual is for adults. You must be at least 18 to create an account (see the Terms of Service). See Section 15.

8. Governing consent instruments. The precise consent text you are shown at signup, and the values recorded, are defined in DriveAI’s ML Training Data Consent (Variant A-2) and Portal Consent Language (Sections 7-8) documents. Those instruments and this notice are designed to be read together.

9. Memory (not yet on). We are building a memory feature that keeps short notes of the kinds of vehicle work you’ve discussed (for example, “suspension work”), not your words, so Trace can pick up where you left off. It is not active on your account. Before it applies to you, we will tell you in the app what it keeps and for how long.

17. Contact Us

If you have questions about this Privacy Policy, our data practices, or wish to submit a privacy request, you can reach us at:

DriveAI LLC


To exercise your privacy rights, please visit our Privacy Request Form or email privacy@driveaitech.com.