Review our
Terms of Service
and
Privacy Policy,
then confirm below. Optional choices are yours — change them anytime in Privacy Settings.
Optional — you choose
What this meansHelp improve DriveTrace for everyone. We use an anonymized, aggregated version of your vehicle data (with your name, VIN, and location removed, and capped so no aggregate can be traced to you) to make our diagnostics smarter for all drivers. This is not a sale of your data. Turn it off anytime — your diagnostics and subscription are unaffected.
What this meansLet DriveTrace use data that still identifies me for features beyond my own diagnostics (off by default).
PreviewShop terms are being finalized — shown here for preview.
Optional — you choose
What this means## Plain-Language Summary (non-binding overview)
For convenience only; the operative terms below control.
- **Optional and off by default.** Nothing here happens unless you deliberately turn it on. Your DriveTrace service works exactly the same whether you opt in or not.
- **What you'd be allowing.** If you opt in, DriveAI can use **de-identified and aggregated** data from your shop's use of DriveTrace to build **benchmarks** — for example, "how your average diagnostic turnaround, common fault patterns, or comeback rate compare to similar shops in your region or segment."
- **What is removed first.** Before your data is used for benchmarking, we remove direct identifiers — your customers' names, emails, phone numbers, VINs, and license plates, and your shop's identifying details. Benchmarks are reported only in aggregate across many shops; they never expose an individual customer, vehicle, or an identifiable competing shop.
- **Not selling, not advertising, not model training.** We do not sell your data, we do not use it for advertising, and this opt-in does **not** authorize training our AI models on your data (that is a separate choice).
- **You can turn it off anytime.** Turning it off stops future use immediately. Aggregate benchmarks already produced can't be "un-computed," but they contain no identifiable data about you.
- **You confirm you're allowed to do this.** By opting in you confirm you have the authority and any necessary basis to authorize this use of the data you put into DriveTrace.
---
## Operative Terms — Benchmarking Data Use Authorization
This authorization ("**Authorization**") supplements the DriveTrace Shop Data Processing Agreement (`docs/legal/shop-dpa.md`, the "**DPA**") and the Business Terms of Service (`docs/legal/shop-business-tos.md`). Capitalized terms not defined here have the meaning given in the DPA. In the event of a conflict, the DPA controls with respect to the Processing of Personal Information.
**B-1. Purpose.** This Authorization permits DriveAI to Process certain de-identified and aggregated data derived from Shop's use of the Services for the purpose of producing cross-shop benchmarking, comparative performance analytics, and aggregate industry insights (the "**Benchmarking Purpose**"). The Benchmarking Purpose is separate from, and in addition to, the Business Purposes in Section 3.1 of the DPA, and separate from the ML Training Purpose (`docs/legal/ml-training-consent.md`, Variant B).
**B-2. Optional, unbundled, and off by default.** This Authorization is entirely optional. It is presented as a **separate control**, unbundled from acceptance of the Business Terms, the DPA, and any ML Training authorization. The control **defaults to off**. Declining (or later revoking) this Authorization does not affect the availability, scope, price, or quality of the Services.
**B-3. Scope of data.** Subject to the de-identification requirements in B-4, the following categories may be used for the Benchmarking Purpose if Shop opts in:
| Data category | Used for benchmarking (if opted in) | Notes |
|---|---|---|
| Diagnostic operational metrics (e.g., session counts, diagnostic categories, DTC frequencies, turnaround/cycle times, comeback indicators) | Yes | De-identified and aggregated |
| Vehicle metadata (make, model, year, engine/fuel type, mileage band) | Yes | Retained at a non-identifying granularity |
| Aggregate parts/labor/service patterns | Yes | Aggregated; no individual invoice exposed |
| Consumer names, emails, phone numbers, addresses | **No** | Never used for benchmarking |
| VINs and license plate numbers | **No** | Removed before any benchmarking use |
| Shop-identifying details in benchmark *outputs* | **No** | Outputs are aggregate; no identifiable competing shop is exposed |
| Billing / payment data | **No** | Never used for benchmarking |
| Raw audio recordings | **No** | Not used for benchmarking |
**B-4. De-identification and aggregation requirements.** Before using any data under this Authorization, DriveAI shall:
- (a) remove all direct identifiers (consumer name, email, phone, address, account ID, VIN, license plate; and Shop's direct identifiers);
- (b) replace shop, user, session, and vehicle identifiers with non-reversible pseudonymous tokens and not retain a re-identification mapping after de-identification;
- (c) apply automated scrubbing to any free-text metrics to remove embedded Personal Information before inclusion;
- (d) report benchmarking outputs only in **aggregate** form, subject to a minimum-cohort threshold so that no output can reasonably be attributed to an individual Consumer, vehicle, or identifiable Shop; and
- (e) maintain technical and organizational safeguards that prohibit re-identification, consistent with CCPA/CPRA § 1798.140(m) (definition of "deidentified"), and make no attempt to re-identify.
**B-5. No Sale, Sharing, advertising, or model training.** The Benchmarking Purpose does not constitute a "Sale" or "Sharing" of Personal Information under CCPA/CPRA. DriveAI does not sell benchmarking data, does not use it for advertising, and does not transfer identifiable data to third parties. This Authorization does **not** authorize use of Shop data to train, fine-tune, or improve DriveAI's machine-learning models — that use requires the separate ML Training Data Use Authorization.
**B-6. Shop representations.** Shop represents and warrants that it has the authority to authorize the Benchmarking Purpose for the data it submits, that doing so does not infringe any third party's rights, and that, to the extent required by Applicable Data Protection Law, it has provided any necessary notice to, or has a lawful basis with respect to, the Consumers whose data underlies the de-identified inputs.
**B-7. Revocation.** Shop may revoke this Authorization at any time through its DriveTrace administration portal or by written notice to legal@driveaitech.com. Revocation takes effect for data processed after the revocation date and applies prospectively. Aggregate benchmarking outputs already produced from de-identified data prior to revocation are not subject to recall but contain no data that can reasonably be linked to Shop, its Consumers, or their vehicles. Revocation must be as easy to exercise as granting the Authorization.
**B-8. GDPR applicability.** Where GDPR or UK GDPR applies, Shop, as Controller, is responsible for establishing and documenting the lawful basis for the de-identification and aggregation underlying the Benchmarking Purpose (e.g., Article 6(1)(f) legitimate interests following a balancing test). Truly anonymized aggregate outputs fall outside the scope of the GDPR; the de-identification process itself is Processing subject to the DPA.
**B-9. Audit and term.** Shop may audit DriveAI's compliance with this Authorization on the same terms as Section 11 of the DPA. This Authorization is effective when Shop enables the control and remains in effect until revoked or until the DPA terminates. B-4, B-5, and B-9 survive termination with respect to any retained de-identified data.
---
## Consent-Control Specification (for the backend + frontend)
This section specifies how the opt-in control and its records are implemented. It mirrors the append-only consent-record model already used for ML-training consent (`docs/legal/ml-training-consent.md`, § 4.3).
**UI requirements**
- Presented in the Shop administration portal under "Data & Privacy," as a **separate toggle**, visually and functionally distinct from the DPA/Business-Terms acceptance and from any ML-training toggle. It must **not** be bundled into a single "accept all" control.
- **Default: OFF.** No pre-checking/pre-enabling.
- Toggling on shows a confirmation: *"By enabling this, you confirm you have the authority to authorize de-identified benchmarking use of your shop's data. This does not train AI models on your data and can be turned off anytime."*
- Revocation (toggle off) is available at any time without contacting support.
- A "View full terms" link opens the operative text above.
**Consent-record schema (append-only, immutable)**
```json
{
"consent_id": "<uuid>",
"entity_type": "shop",
"entity_id": "<shop_id>",
"consent_type": "benchmarking",
"consent_version": "shop-benchmarking-optin@1.0",
"action": "grant" | "revoke",
"timestamp": "<ISO 8601>",
"granted_by": "<admin user_id who toggled>",
"ip_address": "<IP>",
"user_agent": "<browser user-agent>"
}
```
- Records are **append-only**; a revocation adds a new record, it does not delete the prior grant. Current state = most recent record for `(entity_id, consent_type)`.
- The `consent_version` references the terms-registry composite key (`{registry_id}@{version}`) so each record proves the exact document version the Shop agreed to.
- The backend MUST persist the grant record **before** any Shop data is flagged eligible for the Benchmarking Purpose; if the record fails to persist, the data is not used.
- Retention: consent records retained **7 years** (audit/regulatory alignment; consistent with the ML-training consent records).
- On a material (MAJOR) version bump of this document, Shops holding consent under an earlier version are re-prompted before benchmarking continues under the new scope (per the Terms Versioning Scheme).
## Cross-References
| Document | Relationship |
|---|---|
| `docs/legal/shop-dpa.md` | This Authorization supplements the DPA; the DPA's de-identification exception (Section 9.3) and no-Sale/Share posture (Section 4.1) frame this use. |
| `docs/legal/ml-training-consent.md` (Variant B) | Separate, independent opt-in for ML *model training*. Benchmarking ≠ training; a Shop may grant either, both, or neither. |
| `docs/legal/shop-business-tos.md` | Section 6.4 references this opt-in as off-by-default and unbundled. |
| `docs/legal/terms-versioning-scheme.md` | Governs versioning, bump triggers, and re-prompt obligations for this document. |
| `docs/legal/privacy-policy.md` | The Privacy Policy's description of de-identified/aggregated use and benchmarking reports should reconcile with this Authorization at counsel review. |
One more step before you continue — choose your account
type and review how your car's data is used.
I'm signing up as
Data & AI-Learning Consent
Review our
Terms of Service
and
Privacy Policy,
then confirm below. Optional choices are yours — change them anytime in Privacy Settings.
Optional — you choose
What this meansHelp improve DriveTrace for everyone. We use an anonymized, aggregated version of your vehicle data (with your name, VIN, and location removed, and capped so no aggregate can be traced to you) to make our diagnostics smarter for all drivers. This is not a sale of your data. Turn it off anytime — your diagnostics and subscription are unaffected.
What this meansLet DriveTrace use data that still identifies me for features beyond my own diagnostics (off by default).
PreviewShop terms are being finalized — shown here for preview.
Optional — you choose
What this means## Plain-Language Summary (non-binding overview)
For convenience only; the operative terms below control.
- **Optional and off by default.** Nothing here happens unless you deliberately turn it on. Your DriveTrace service works exactly the same whether you opt in or not.
- **What you'd be allowing.** If you opt in, DriveAI can use **de-identified and aggregated** data from your shop's use of DriveTrace to build **benchmarks** — for example, "how your average diagnostic turnaround, common fault patterns, or comeback rate compare to similar shops in your region or segment."
- **What is removed first.** Before your data is used for benchmarking, we remove direct identifiers — your customers' names, emails, phone numbers, VINs, and license plates, and your shop's identifying details. Benchmarks are reported only in aggregate across many shops; they never expose an individual customer, vehicle, or an identifiable competing shop.
- **Not selling, not advertising, not model training.** We do not sell your data, we do not use it for advertising, and this opt-in does **not** authorize training our AI models on your data (that is a separate choice).
- **You can turn it off anytime.** Turning it off stops future use immediately. Aggregate benchmarks already produced can't be "un-computed," but they contain no identifiable data about you.
- **You confirm you're allowed to do this.** By opting in you confirm you have the authority and any necessary basis to authorize this use of the data you put into DriveTrace.
---
## Operative Terms — Benchmarking Data Use Authorization
This authorization ("**Authorization**") supplements the DriveTrace Shop Data Processing Agreement (`docs/legal/shop-dpa.md`, the "**DPA**") and the Business Terms of Service (`docs/legal/shop-business-tos.md`). Capitalized terms not defined here have the meaning given in the DPA. In the event of a conflict, the DPA controls with respect to the Processing of Personal Information.
**B-1. Purpose.** This Authorization permits DriveAI to Process certain de-identified and aggregated data derived from Shop's use of the Services for the purpose of producing cross-shop benchmarking, comparative performance analytics, and aggregate industry insights (the "**Benchmarking Purpose**"). The Benchmarking Purpose is separate from, and in addition to, the Business Purposes in Section 3.1 of the DPA, and separate from the ML Training Purpose (`docs/legal/ml-training-consent.md`, Variant B).
**B-2. Optional, unbundled, and off by default.** This Authorization is entirely optional. It is presented as a **separate control**, unbundled from acceptance of the Business Terms, the DPA, and any ML Training authorization. The control **defaults to off**. Declining (or later revoking) this Authorization does not affect the availability, scope, price, or quality of the Services.
**B-3. Scope of data.** Subject to the de-identification requirements in B-4, the following categories may be used for the Benchmarking Purpose if Shop opts in:
| Data category | Used for benchmarking (if opted in) | Notes |
|---|---|---|
| Diagnostic operational metrics (e.g., session counts, diagnostic categories, DTC frequencies, turnaround/cycle times, comeback indicators) | Yes | De-identified and aggregated |
| Vehicle metadata (make, model, year, engine/fuel type, mileage band) | Yes | Retained at a non-identifying granularity |
| Aggregate parts/labor/service patterns | Yes | Aggregated; no individual invoice exposed |
| Consumer names, emails, phone numbers, addresses | **No** | Never used for benchmarking |
| VINs and license plate numbers | **No** | Removed before any benchmarking use |
| Shop-identifying details in benchmark *outputs* | **No** | Outputs are aggregate; no identifiable competing shop is exposed |
| Billing / payment data | **No** | Never used for benchmarking |
| Raw audio recordings | **No** | Not used for benchmarking |
**B-4. De-identification and aggregation requirements.** Before using any data under this Authorization, DriveAI shall:
- (a) remove all direct identifiers (consumer name, email, phone, address, account ID, VIN, license plate; and Shop's direct identifiers);
- (b) replace shop, user, session, and vehicle identifiers with non-reversible pseudonymous tokens and not retain a re-identification mapping after de-identification;
- (c) apply automated scrubbing to any free-text metrics to remove embedded Personal Information before inclusion;
- (d) report benchmarking outputs only in **aggregate** form, subject to a minimum-cohort threshold so that no output can reasonably be attributed to an individual Consumer, vehicle, or identifiable Shop; and
- (e) maintain technical and organizational safeguards that prohibit re-identification, consistent with CCPA/CPRA § 1798.140(m) (definition of "deidentified"), and make no attempt to re-identify.
**B-5. No Sale, Sharing, advertising, or model training.** The Benchmarking Purpose does not constitute a "Sale" or "Sharing" of Personal Information under CCPA/CPRA. DriveAI does not sell benchmarking data, does not use it for advertising, and does not transfer identifiable data to third parties. This Authorization does **not** authorize use of Shop data to train, fine-tune, or improve DriveAI's machine-learning models — that use requires the separate ML Training Data Use Authorization.
**B-6. Shop representations.** Shop represents and warrants that it has the authority to authorize the Benchmarking Purpose for the data it submits, that doing so does not infringe any third party's rights, and that, to the extent required by Applicable Data Protection Law, it has provided any necessary notice to, or has a lawful basis with respect to, the Consumers whose data underlies the de-identified inputs.
**B-7. Revocation.** Shop may revoke this Authorization at any time through its DriveTrace administration portal or by written notice to legal@driveaitech.com. Revocation takes effect for data processed after the revocation date and applies prospectively. Aggregate benchmarking outputs already produced from de-identified data prior to revocation are not subject to recall but contain no data that can reasonably be linked to Shop, its Consumers, or their vehicles. Revocation must be as easy to exercise as granting the Authorization.
**B-8. GDPR applicability.** Where GDPR or UK GDPR applies, Shop, as Controller, is responsible for establishing and documenting the lawful basis for the de-identification and aggregation underlying the Benchmarking Purpose (e.g., Article 6(1)(f) legitimate interests following a balancing test). Truly anonymized aggregate outputs fall outside the scope of the GDPR; the de-identification process itself is Processing subject to the DPA.
**B-9. Audit and term.** Shop may audit DriveAI's compliance with this Authorization on the same terms as Section 11 of the DPA. This Authorization is effective when Shop enables the control and remains in effect until revoked or until the DPA terminates. B-4, B-5, and B-9 survive termination with respect to any retained de-identified data.
---
## Consent-Control Specification (for the backend + frontend)
This section specifies how the opt-in control and its records are implemented. It mirrors the append-only consent-record model already used for ML-training consent (`docs/legal/ml-training-consent.md`, § 4.3).
**UI requirements**
- Presented in the Shop administration portal under "Data & Privacy," as a **separate toggle**, visually and functionally distinct from the DPA/Business-Terms acceptance and from any ML-training toggle. It must **not** be bundled into a single "accept all" control.
- **Default: OFF.** No pre-checking/pre-enabling.
- Toggling on shows a confirmation: *"By enabling this, you confirm you have the authority to authorize de-identified benchmarking use of your shop's data. This does not train AI models on your data and can be turned off anytime."*
- Revocation (toggle off) is available at any time without contacting support.
- A "View full terms" link opens the operative text above.
**Consent-record schema (append-only, immutable)**
```json
{
"consent_id": "<uuid>",
"entity_type": "shop",
"entity_id": "<shop_id>",
"consent_type": "benchmarking",
"consent_version": "shop-benchmarking-optin@1.0",
"action": "grant" | "revoke",
"timestamp": "<ISO 8601>",
"granted_by": "<admin user_id who toggled>",
"ip_address": "<IP>",
"user_agent": "<browser user-agent>"
}
```
- Records are **append-only**; a revocation adds a new record, it does not delete the prior grant. Current state = most recent record for `(entity_id, consent_type)`.
- The `consent_version` references the terms-registry composite key (`{registry_id}@{version}`) so each record proves the exact document version the Shop agreed to.
- The backend MUST persist the grant record **before** any Shop data is flagged eligible for the Benchmarking Purpose; if the record fails to persist, the data is not used.
- Retention: consent records retained **7 years** (audit/regulatory alignment; consistent with the ML-training consent records).
- On a material (MAJOR) version bump of this document, Shops holding consent under an earlier version are re-prompted before benchmarking continues under the new scope (per the Terms Versioning Scheme).
## Cross-References
| Document | Relationship |
|---|---|
| `docs/legal/shop-dpa.md` | This Authorization supplements the DPA; the DPA's de-identification exception (Section 9.3) and no-Sale/Share posture (Section 4.1) frame this use. |
| `docs/legal/ml-training-consent.md` (Variant B) | Separate, independent opt-in for ML *model training*. Benchmarking ≠ training; a Shop may grant either, both, or neither. |
| `docs/legal/shop-business-tos.md` | Section 6.4 references this opt-in as off-by-default and unbundled. |
| `docs/legal/terms-versioning-scheme.md` | Governs versioning, bump triggers, and re-prompt obligations for this document. |
| `docs/legal/privacy-policy.md` | The Privacy Policy's description of de-identified/aggregated use and benchmarking reports should reconcile with this Authorization at counsel review. |
If we can reach the email on your account, a link to
turn off two-factor authentication is on its way.
It expires in 30 minutes. You'll sign in with your
password afterwards.
Notice at Collection: We collect your name, email address, information about your vehicle, and the messages and photos you send in chat, to provide the service.
If you sign in with Google, Google shares your name, email address and an account identifier with us, and may share your profile photo.
Under the California Consumer Privacy Act (CCPA), you have the following rights:
Right to Know: You may request the categories and specific pieces of personal information we have collected about you.
Right to Delete: You may request that we delete the personal information we have collected from you.
Right to Opt Out: You may opt out of the sale or sharing of your personal information.
See our Privacy Policy
for full details on use, retention, and how to exercise your rights.