DealFlo
HomePrivacyTermsComplianceSubprocessors

DealFlo Chrome Extension — Privacy and Data Disclosure

Effective date: November 14, 2026 · Applies to the DealFlo browser extension only. The DealFlo platform is covered by our Privacy Policy.

The DealFlo extension shows a salesperson the DealFlo text conversation for the customer they are viewing in their dealership CRM, puts an SMS button beside the customer phone numbers the CRM shows, and lets them text, call and take notes without leaving it. If the salesperson allows it, it also fills their Facebook Marketplace vehicle listings from the dealership’s DealFlo inventory and helps them add the buyers who message about those cars. To do that it reads a small amount of information from the page on screen. This page describes exactly what that means, in the order the questions usually get asked.

Where it runs

The extension is installed with permission to read pages on these sites only:

  • VinSolutions: *.vinsolutions.com, *.vinmanager.com and vinsolutions.app.coxautoinc.com
  • Elead: *.eleadcrm.com, *.elead-crm.com, *.forddirectcrm.com, and crm.connectcdk.com, elead.connectcdk.com and prod-crm.connectcdk.com, where Elead runs when a salesperson signs in through CDK Unify
  • DealFlo’s own sample CRM page, www.dealflo.tech/extension-demo, which contains invented customers and exists so a salesperson can try the SMS buttons before using them on a real CRM. No other DealFlo page is read.

It does not run on any other website unless the salesperson turns it on for that one site, at which point Chrome shows its own permission prompt naming the site. That is also how it runs on Facebook (www.facebook.com): only after the salesperson taps “Allow DealFlo on Facebook” and approves Chrome’s prompt, to post their inventory to Marketplace (see Facebook Marketplace below). It never requests access to all websites. It has no access to browsing history, bookmarks or downloads, and it does not record which pages are visited.

On the sites above it reads a page only while that page is on screen. A CRM page open in a background tab is read when the salesperson switches to it, not before.

What it reads from a customer screen

When a salesperson opens a customer record in a supported CRM, the extension reads the following from that page and nothing else:

  • The customer’s phone number.
  • The customer’s name.
  • The customer’s email address, if the page shows one.
  • A vehicle of interest and VIN, if the page shows them.
  • A customer or opportunity identifier, when the CRM puts one in the page.

Reading happens entirely inside the browser. The page’s HTML is never transmitted. The fields above go to the DealFlo panel beside the CRM, which sends only the phone number and the CRM’s identifiers to DealFlo to find the matching customer in your DealFlo account. The name, email and vehicle stay in the browser, where they are shown to the salesperson, and reach DealFlo only if the salesperson chooses to add a customer who is not in DealFlo yet. Salespeople can turn this automatic reading off in the extension’s settings.

The SMS and Email buttons

On a supported CRM page, including list screens such as a desk log, the extension finds the customer phone numbers and email addresses the page shows and draws a small DealFlo SMS button beside each number and an Email button beside each address, so a customer who only gave an email can be reached the same way. It is designed to leave out numbers and addresses in page headers, navigation and footers, numbers and addresses inside notes and other text, fax numbers, automated no-reply addresses, and anything the salesperson is typing into.

  • While the salesperson is signed in, the extension sends those phone numbers and email addresses, and nothing else from the page, to DealFlo so each button can show whether that customer is already in your DealFlo account and whether they have replied or opted out. DealFlo checks them against your own store’s records and does not store them. Signed out, nothing is sent.
  • When the salesperson taps a button, the extension reads that number or email address again, along with the customer name shown on the same row, and hands them to the DealFlo panel. The number or address is used to find the customer. The name is only used to pre-fill a form the salesperson reviews if the customer is not in DealFlo yet.
  • Salespeople can turn the buttons off in the extension’s settings, and DealFlo can switch them off for every store at once without an update.

What it refuses to read

The extension does not read credit applications, financing or payment pages, or any screen showing a Social Security, driver’s licence, bank or card number, and draws no SMS buttons on them.

Before reading anything, it checks the page address for a credit, finance, payment or deal page, and checks what is on screen for a field or label for a Social Security number, a driver’s licence number, bank routing or account details, a card number, or a password. If any are present, or the page is too large to check in full, the extension reads nothing, and the panel tells the salesperson that it did not read that screen. The check runs again whenever the page changes, so a tab or window that opens with any of those details on it takes the SMS buttons down for as long as it is showing.

An ordinary customer record is not refused because it shows a birthday or because its notes mention a credit application. On those screens the extension reads only what is listed above, never anything else on the page.

Facebook Marketplace

Only on www.facebook.com, and only after the salesperson allows it. The extension never sees, stores or sends the salesperson’s Facebook password or cookies: it works inside the Facebook tab they are already signed in to.

Posting a car

  • When the salesperson chooses a car in the DealFlo panel and taps Post, the extension opens Facebook’s “Vehicle for sale” form in a new tab and types in the listing DealFlo prepared from the dealership’s inventory: vehicle details, price, mileage, colors, description and photos (downloaded from DealFlo). The salesperson can see and change every field.
  • It does not click Next or Publish (unless the salesperson turned on auto-post, described below). The salesperson reviews the listing and publishes it themselves. The extension then tells DealFlo the car is posted, with the listing’s Facebook address, so DealFlo can show it as live and remind the salesperson when it sells.
  • The salesperson can choose several cars at once. The extension then fills them one after another in the same Facebook tab, opening the next car once they publish the one on screen, and still does not click Next or Publish itself. A batch stops at the dealership’s daily posting pace.
  • It tells DealFlo how the fill went, field by field (filled, skipped or needs a hand), and whether the post was published or abandoned. If Facebook shows a login, says Marketplace isn’t available on that profile, or is set to another language, the extension reads Facebook’s own on-screen text in that tab to say so; only a reason (for example “needs a login”) reaches DealFlo.

Auto-post

Off unless three things are true: DealFlo has switched it on for the dealership, a manager at the dealership has turned it on, and the salesperson has turned it on themselves in the DealFlo panel, in that browser. They can turn it off at any time.

  • While it is on and Chrome is open, the extension asks DealFlo every few minutes which of the dealership’s cars to post. For each one it opens Facebook’s “Vehicle for sale” form in a background tab, types in the listing exactly as it does for a car the salesperson posts by hand, and then clicks Next and Publish itself, so the listing is published from the salesperson’s own Facebook profile without them pressing anything. It closes the tab when Facebook confirms. It posts one car at a time, a few minutes apart, and stops at the dealership’s daily posting pace.
  • It tells DealFlo that it is running (the time and the extension’s version), which cars it posted, which car it could not post and why (for example a field Facebook asked for), and why it stopped if it did (for example “needs a login”). The dealership’s managers can see that in DealFlo. Nothing else about the salesperson’s Facebook account is read or sent.
  • On the device it keeps whether auto-post is on, for which dealership, what it is doing, and a random identifier for that browser profile, made by the extension and not derived from the device, so that one login never posts from two browsers at once.
  • Facebook’s terms expect a person to publish each listing. A salesperson who turns auto-post on is told so first.

Marketplace chats

The extension reads the open Marketplace chat on the salesperson’s device to identify the car and prefill the buyer’s contact information. It sends only what the salesperson chooses to add.

  • It looks for a Marketplace chat (one linked to a listing). Personal chats get nothing: no card, and nothing about them is sent anywhere.
  • Before the salesperson taps Add, the only things sent to DealFlo are the listing’s title and link (the Facebook address of the listing the chat is about), to check whether it is one of the dealership’s cars. No buyer name, contact details, message or link to the chat itself is sent.
  • When the salesperson taps Add, DealFlo receives exactly what they confirmed on the card: the buyer’s name, the phone number or email address, the chat’s Facebook identifier and the listing’s address. That creates an ordinary DealFlo lead, or finds the existing one so nobody is duplicated.
  • Message text is never sent or stored. A phone number or email the buyer typed is only used to fill in the card, which the salesperson can edit or clear.
  • DealFlo’s assistant texts a Marketplace buyer only if the salesperson confirms the buyer asked to be texted. Otherwise the buyer is added for the salesperson to contact personally.

Salespeople can turn Facebook access off in the extension’s settings or in Chrome, and DealFlo can switch the Marketplace features off for every store at once without an update.

The side panel

The side panel shows DealFlo’s own web application, loaded from www.dealflo.tech each time the panel opens, the same as opening DealFlo in a browser tab. It signs in with the extension’s own DealFlo session rather than the salesperson’s website login. Everything the salesperson does there, such as sending a text, logging a note or starting a call, is an ordinary DealFlo action governed by our main Privacy Policy.

The extension also downloads a small settings file from DealFlo, including while signed out, which says whether the SMS buttons are switched on and how they are labelled. It contains no information about anyone, and nothing about the salesperson or the page is sent to fetch it.

What is stored, and for how long

  • On the salesperson’s computer: their DealFlo sign-in session (kept until they sign out), the settings file above, and the panel’s working state: the customer read off the current screen, the conversation that is open, and any message they have started typing, and the progress of a Facebook listing being filled. The working state is cleared when the browser closes. While a batch of cars is being posted, the list of those cars (each car’s title and listing description from the dealership’s inventory, and whether it was posted) is kept on their computer so the batch survives the panel closing, until they clear it. If they use the Marketplace chat card, a list of the chats they added (the chat’s Facebook identifier and the buyer’s name, the most recent 500) is kept on their computer so the card can say “In DealFlo”. Their extension preferences (automatic reading, SMS buttons, notifications, which store they are working in) are saved in Chrome’s sync storage, so they follow the salesperson to another computer if Chrome sync is on.
  • On DealFlo’s servers: nothing new. Information read from a CRM page is used to look up an existing DealFlo record and is not stored as a copy. If the salesperson chooses to add a customer who is not yet in DealFlo, that is an explicit action they confirm, and it creates an ordinary DealFlo lead governed by our main Privacy Policy. For Facebook Marketplace, DealFlo keeps the listings the salesperson posts (which car, its Facebook address, whether it is live, how the fill went) and, for each buyer they add, the link between that lead, the car and the Facebook chat.
  • Diagnostics: DealFlo records whether each read succeeded, which CRM it was, and which version of the extension ran, so we can tell when a CRM changes its pages and breaks compatibility. These records contain no customer name, phone number, email address, record identifier, or page address.

What the extension never does

  • It does not sell, rent, or share any information with anyone.
  • It does not use any information for advertising, profiling, or credit decisions.
  • It does not transmit page content, screenshots, or keystrokes.
  • It never clicks Send on Facebook and never sends a Facebook message. It clicks Next and Publish only for a salesperson who turned on auto-post; otherwise every post is published by the salesperson.
  • It does not contain analytics, advertising, or tracking software of any kind. The code that reads CRM and Facebook pages, draws the SMS buttons and fills listings is contained in the extension package Chrome installs.

The use of information received through the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements: it is used only to provide the extension’s single purpose, letting the salesperson work their DealFlo conversations and inventory from their CRM and from Facebook Marketplace.

Who controls it

A dealership must be switched on for the extension by DealFlo before any of its salespeople can use it; until then the extension refuses every request for that store. Salespeople see only the customers their DealFlo role already lets them see. Individual salespeople can turn off automatic reading and the SMS buttons, and remove Facebook access, in the extension’s settings. Posting to Facebook is limited to the salespeople their store allows. Signing out, or removing the extension, ends its access immediately.

Questions

A dealership’s IT or compliance team can reach us at joshuas@dealfloai.com. If you need a written answer for a vendor review, say so and we will provide one.

DealFlo
Privacy PolicyTerms of ServiceSMS ComplianceSubprocessorsContact
© 2026 DealFlo Inc. All rights reserved.