Dealership Workflow Chrome extension — privacy

Last updated: September 25, 2026 · Bacano Systems LLC, doing business as Dealership Workflow

What the extension reads

  • The deal fields you choose. When you pick a deal, the extension loads that deal's form fields from Dealership Workflow (buyer and co-buyer names and address, vehicle, lienholder, dealer number) to fill the Missouri temp tag or lien form. It never fills — and the server never sends — a date of birth, driver license number, Social Security number or net price.
  • A VinSolutions customer page, only when you click "Start DW deal from this customer". It copies only: buyer and co-buyer first and last name, phone, email and address; the vehicle's VIN, stock number, year, make, model, trim, mileage and new/used; the lead type; and the sales rep's name. It never copies a Social Security number, date of birth or customer id, and it never writes anything into VinSolutions.
  • Page text, for two checks only. When you click "Save this page to the deal" on a Missouri portal page, the page's visible text is sent with the capture so Dealership Workflow can confirm the page shows the deal's VIN. For the toolbar badge, the extension looks on the CRM and portal pages for VINs and for stock numbers printed after a "Stock #" label — and sends only those strings.
  • A bill of sale you upload (free upload fill): the PDF is read in memory to fill the form; our AI provider reads that one page. It is not stored.
  • Your Dealership Workflow sign-in. The extension reuses the sign-in of your open Dealership Workflow tab (the short-lived access token only — never your password or refresh token), or an email code you enter.

What it sends, and where

Only to Dealership Workflow (dealershipworkflow.com), over HTTPS, with your sign-in:

  • deal searches (stock number, VIN or last name) and the deal you open;
  • the VINs and stock numbers found on a page, for the badge;
  • when you start a deal from VinSolutions, the vehicle's VIN and stock number and the buyer's name, phone and email, to check for an existing deal on that vehicle — compared, never stored;
  • screenshots of the portal page you choose to save, with its visible text for the VIN check;
  • a checklist item you mark done.

A VinSolutions customer goes straight into the Start New Deal form in your own Dealership Workflow tab — not through our server, and never in a web address. Apart from the existing-deal check above, nothing reaches our server until you click Create Deal.

The extension fills Missouri portal forms in your browser only. It never submits a form for you. It sends nothing to the Missouri Department of Revenue, VinSolutions or anyone else.

What it stores

  • In your browser: the email-code sign-in (if you use one), a fill in progress for at most 60 seconds while a portal page reloads, and the last fill's result (field names and counts only).
  • On our server, nothing new beyond: audit entries with counts and field names only (no customer values or page text), and the PDF of a portal page you choose to save, filed on that deal's temp tag or lien checklist item. Deals you create and checklist items you mark are stored as in Dealership Workflow itself.

Page text and screenshots are held in memory only; the page text sent for the VIN check is never stored or logged.

What it never does

  • No selling or sharing of data, no advertising, no tracking or analytics in the extension.
  • It runs only on the Missouri portals (sa.dor.mo.gov, dors.mo.gov), VinSolutions (vinsolutions.app.coxautoinc.com, apps.vinmanager.com) and dealershipworkflow.com.

Questions