Privacy Policy — SweetDriver

Last updated: August 9, 2026

SweetDriver ("the extension") is an internal tool built by ETF Auto for its own service writers and managers. It is not offered to the general public and is distributed unlisted to ETF Auto staff. It runs only on two sites ETF Auto already uses: its shop management system (tekmetric.com) and the fleet claims system it files warranty and fleet claims into (claimdriver.com).

What the extension does

Filing a fleet claim means re-typing the same repair order into a second system by hand. SweetDriver reads the repair order the user already has open in Tekmetric and fills the matching claim form in ClaimDriver, either one claim at a time or in a batch of up to ten.

What data it handles

Only the contents of the repair order being claimed, as it already exists in the user's Tekmetric account:

• Repair order number, dates, store, and totals
• Vehicle details — VIN, year, make, model, mileage
• Job lines, parts, labor and their amounts
• The fleet account the repair was performed for
• The repair order's invoice document

What is transmitted, and where

Repair order details are entered into ClaimDriver, the fleet claims system operated by MKEY / ClaimDriver — because filing that claim is the purpose of the extension and the destination the user chose. The data travels from the user's Tekmetric session to the user's own ClaimDriver session, both of which they are already signed in to.

No data is sent anywhere else. The extension has no server of its own, contacts no ETF Auto systems, uses no analytics, and transmits nothing to any other destination.

What is stored

• On the device: the user's own settings (such as which store they are filing for and whether dry-run mode is on) and the working state of a batch in progress, so a batch survives a page reload. Held in the browser's extension storage on that machine only.
• Invoice files: when the user attaches an invoice to a claim, the document is saved into their own Downloads folder. It goes nowhere else.
• On any ETF Auto server: nothing. The extension does not have one.

Why each permission is needed

• storage — the user's settings and in-progress batch state, on their machine.
• tabs and scripting — a claim spans two tabs (Tekmetric and ClaimDriver); the extension needs to find the claim tab and act in it. Both are limited to those two sites.
• alarms — paces a batch so ClaimDriver is not hit too quickly.
• downloads — saves the repair order's invoice so it can be attached to the claim.

What the extension does not do

• It does not sell or transfer data to third parties, beyond filing the claim into ClaimDriver as the user directed.
• It does not use data for any purpose unrelated to filing that claim.
• It does not use data to determine creditworthiness or for lending purposes.
• It does not track browsing, clicks, keystrokes or location, and it is inactive on every website other than Tekmetric and ClaimDriver.
• It does not collect user credentials. It uses the sessions the user is already signed in to, and those session tokens are never transmitted anywhere except back to the site they belong to.
• It does not submit a single claim on its own — it fills the form and stops, so a person reviews and submits. Batch submission happens only when a user deliberately turns off dry-run mode, and only for claims that pass every consistency check.

Who can access the data

Only the ETF Auto employee using the extension, within the two accounts they are already signed in to. Data handled by ClaimDriver after a claim is filed is governed by ClaimDriver's own privacy policy.

Changes

If this policy changes, the updated version will be posted at this address with a new "last updated" date.

Questions about this policy or the data it describes: claude@etfauto.com — ETF Auto.