Privacy Policy

Auto AI Services · Estimate Auditor for CCC ONE and Mitchell · Effective 31 October 2026

This explains exactly what the Estimate Auditor reads, what it keeps, and what it never keeps. It is written to be checked against the product rather than to cover us — where a sentence below says we do not collect something, the software does not have the code to do it.

What the product does

The Estimate Auditor is a Chrome extension and a hosted service. On a repair estimate you have open in CCC ONE or in Mitchell, it reads the written estimate, checks it against repair-procedure rules and the vehicle's own federal equipment record, and proposes lines that appear to be missing. Nothing is added to an estimate unless you tick it and confirm. It does nothing on any other website.

What we collect

From your estimate

When you press Audit this estimate, the extension reads the estimate that is open and sends the following to our service so the audit can run. Nothing is read until you press it.

The shop number or organisation key is how an audit is filed under the shop whose estimate it is, so that everyone at a shop signs in as themselves and audits on the one account, and how a free trial is counted once per shop rather than once per email address.

We do not read, request, or receive the vehicle owner's name, address, telephone number, email address, insurance claim number, or policy number. The extension does not look at those fields. They are not part of an estimate audit, so they are not part of what crosses the wire.

We also never receive payment card details — see Payments.

The VIN, specifically

The VIN is sent to our service and used once, to ask the U.S. National Highway Traffic Safety Administration's public vPIC database which equipment the manufacturer built into that vehicle — which is how the audit knows whether a car has, for example, a camera that requires calibration after a windshield replacement.

The VIN is not stored. What we cache is the build pattern: VIN positions 1–8 and 10–11. That is the segment describing the make, model, body, engine and model year, and it deliberately excludes position 9 and positions 12–17 — the check digit and the serial number, which are the parts unique to one individual vehicle. Thousands of vehicles share a build pattern, and it cannot be resolved back to a car, an owner, or an address. It is cached so the same build is not looked up twice.

Against each completed audit we record a plain description such as “2022 GMC Sierra”, never the VIN.

About your shop

WhatWhy
Each person's email address and name, and the shop's name Your account, how we reach you about it, and so the shop's owners can see who has joined it
Estimator names you add So each audit is credited to whoever ran it. First names are enough, and this is optional — audits run and are counted without it
Browser and operating system of each connected computer Shown on your Settings page so you can recognise a computer and disconnect one
Audits run, findings produced, and what you accepted — with which estimating system each was in and, for Mitchell, which insurer's rules applied Your dashboards, and the count your subscription is billed on
Feedback you choose to send from the panel: a thumbs up or down, what went wrong, which of the audit's lines it is about and what you write, with the audit it was about, your browser and the extension's version To fix what went wrong, decide what to build next, and answer you. Anything that looks like a phone number, an email address or a VIN is removed before it is stored
How you found us and how setup went: the campaign or site that sent you to our homepage (its tags, and whether you came from an ad, never the ad's click id), the kind of device and browser you signed up on, your time zone, which setup steps you finished, and your answers to our optional setup questions To see where setup gets stuck and fix it, and to send setup emails at a sensible time of your day
Whether you pressed a button in one of our emails So we stop sending what does not help

We never store your part-code price list. It is used to derive a map of which of your codes each rule should write to, and we keep that map and a fingerprint of the list — not the list. Your labour rates and margins are yours.

How we use it

To run audits, show you your own results, count usage against your subscription, and improve the rules. Rule improvement uses aggregate patterns across shops — for example, that a particular operation has no matching code in many catalogues. It does not involve reading one shop's estimates to inform another's.

AI-assisted analysis

After the rule-based audit identifies potentially missing operations, we may send the operation descriptions and line-item text from your estimate to a third-party artificial intelligence service (currently Anthropic's Claude API) to check whether a flagged operation is actually already present on the estimate under different wording. This reduces false positives — for example, catching that "R&I Frt Bmpr Fascia" and "Remove & Install Front Bumper Cover" are the same operation.

Only operation descriptions are sent — not the VIN, not the vehicle owner's information, not your price list, and not your rates. The AI service processes the text in real time and does not retain it after the request completes. We do not permit it to use your data for model training.

We do not sell your data, share it with insurers or carriers, or use it for advertising. We do not use it to train third-party or general-purpose AI models.

Emails we send

While you are on a free trial we send a few short emails to help you finish setting up and get the most from your trial: never more than one a day. Each one has an unsubscribe link, which stops them at once and does not touch your account. Sign-in codes still arrive.

Our homepage

Our public homepage uses the Meta Pixel to tell Meta that the page was visited, so we can measure our advertising. It runs on that page only. Nothing from your estimates, your dashboard or the extension is sent to Meta.

Who else processes it

We use a small number of service providers, each for one job:

ProviderForWhere
Google Cloud RunRunning the serviceUnited States (us-east1). The rules for a Mitchell estimate run in Canada (northamerica-northeast1) and keep nothing
NeonThe databaseUnited States (us-east-1)
ClerkSign-in and accountsUnited States
StripeSubscriptions and paymentUnited States
NHTSA vPICThe federal equipment lookupUnited States (a public government database)
AnthropicAI-assisted false-positive filtering (operation descriptions only)United States
ResendSending our emails to youUnited States
MetaMeasuring our advertising, from our public homepage onlyUnited States

Payments

Subscriptions are handled by Stripe. Card details are entered on Stripe's own hosted checkout and never reach our servers. We store only Stripe's customer and subscription identifiers, and the number of audits you have run.

Retention and deletion

Audit history is kept while your account is open, because it is the record your dashboards are built from and shops refer back to past jobs. You can ask us to delete your account and everything associated with it at any time, and we will do so within 30 days.

Removing an estimator deactivates them rather than deleting them, so audits they already ran keep their attribution. Say so if you want a person's name removed entirely and we will remove it.

Disconnecting a computer revokes its access immediately.

What you write in feedback is deleted after a year. The rating and the reason are kept while your account is open, because they are how we tell which rules shops find wrong.

Your choices

Security

Everything travels over TLS. Each connected browser holds a revocable token rather than your password, and only a hash of that token is stored — a copy of our database does not yield a working credential. Access to production data is limited to Auto AI Services personnel who need it.

Limited use of Chrome Web Store data

Our use of information received from Google APIs, and of data obtained through the Chrome extension, adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Specifically: the extension collects estimate data solely to provide the audit feature; it is not sold, not transferred except to the service providers listed above, not used for advertising, and not read by humans except with your permission, to resolve a problem you have reported, or where required by law.

Children

This is a tool for collision repair businesses. It is not directed to anyone under 18 and we do not knowingly collect data from children.

Changes

If we change this policy we will update the date at the top, and we will tell account holders by email before any change that materially affects what we collect or how we use it.

Contact

Auto AI Services is operated by 1001731309 Ontario Inc., which is responsible for the information described here.

Questions, a copy of your data, or a deletion request: support@estimateaudits.com.