Privacy Policy

Leadeye Pro Chrome Extension · Effective and last updated: June 7, 2026 (v8.9.1755)

This Privacy Policy is the privacy disclosure for the Leadeye Pro Chrome Extension (the "Extension"). It is published by Leadeye Pro LLC ("Leadeye Pro", "we", "us", or "our"). It explains, in compliance with the Chrome Web Store Developer Program Policies and the Chrome Web Store User Data Privacy program policy, every category of user data the Extension collects, how that data is handled and used, where it is stored, with whom it is shared, and how the Extension complies with the Chrome Web Store Limited Use requirement.

If you have any question, concern, or request regarding this Privacy Policy, contact us at support@leadeyepro.com.

1. Single purpose of the Extension

The Extension has one, and only one, user-facing purpose, declared on its Chrome Web Store listing: Leadeye Pro keeps a vehicle dealership's inventory in sync with the staff member's own Facebook Marketplace listings — auto-posting new inventory, reconciling price changes, and marking sold units. Every feature in the Extension's user interface serves that purpose, and every category of user data described in this policy is collected only to provide or improve that purpose. The Extension does not pursue any unrelated purpose.

2. Limited Use compliance

The Extension's use of user data received through the Extension complies with the Chrome Web Store User Data Privacy program policy's Limited Use requirement. The following four statements describe our Limited Use commitments:

Leadeye Pro only uses or transfers user data to provide or improve user-facing features that are prominent in the Leadeye Pro Chrome Extension's user interface.

Leadeye Pro does not sell or transfer user data to third parties for purposes that are unrelated to the Leadeye Pro Chrome Extension's single purpose.

Leadeye Pro does not use or transfer user data to determine creditworthiness or for any lending purposes.

Leadeye Pro does not allow humans to read user data, except: (a) with the user's affirmative consent; (b) for security purposes, such as investigating abuse; (c) to comply with applicable law; or (d) when the data is aggregated and anonymized for internal operations consistent with applicable privacy law.

In addition, Leadeye Pro does not use, copy, or transfer user data to train, fine-tune, or otherwise build generalized artificial-intelligence or machine-learning models of any kind. The Extension's optional "Generate listing description" feature sends only the active vehicle's specifications (year, make, model, mileage, declared features) on demand to a third-party LLM API through our backend; the prompt and the response are not retained for model training.

3. What user data we collect

The Extension collects only the three categories of user data declared on its Chrome Web Store Data Usage form. Each category is described below using the same name used by the Chrome Web Store Privacy Practices form so that this disclosure can be matched 1-for-1 against the form.

3.1 Authentication information

The Extension collects the following authentication information:

• Employee Username. A short login handle you choose at sign-up (for example, "jgarcia"). It is a pseudonymous login identifier used by your dealership management to attribute leaderboard activity and dealership metrics to the correct staff member. It is not your real name and is not tied to any real-world identifier such as email, phone, or postal address. You enter this value yourself in the Extension's account-creation UI; the Extension never reads it from any third-party website, cookie, or service.
• Account password. The password you choose for your Leadeye Pro account. The password is hashed using a one-way bcrypt algorithm before storage and is never stored, logged, or transmitted in plaintext after the moment you submit the sign-in form.
• License key. A short alphanumeric string issued to your dealership and used solely to verify that your dealership's subscription is active.
• Device identifier. A deterministic local hash computed from your browser's user-agent string, primary screen resolution, timezone offset, hardware-concurrency count, and language. The resulting value has the form DEV<hash> and is used only to enforce subscription seat counts on your license and to correlate code-integrity reports from the same workstation. It is not combined with cookies, advertising IDs, IP addresses, or any cross-site identifier. It is not used for advertising, profiling, or to track you across third-party websites.
• Dealership store name and optional display name. A short identifier for the dealership location you work at, and an optional display label. You enter these yourself.

3.2 Web history

The Extension reads the URL of the currently active browser tab to decide whether to inject its overlay. The overlay is injected only on the host patterns declared in the Extension's manifest.json:

• your dealer inventory website. Currently supported dealer domains: https://www.lamesarv.com/* (La Mesa RV Center) and https://www.westpalmbeachhyundai.com/* (West Palm Beach Hyundai, added in v8.9.1682). Additional dealer domains are added in two ways: (a) baked into a new versioned manifest.json release and disclosed here at the time of release, or (b) opted into by a signed-in user via a one-time chrome.permissions.request prompt that Chrome itself surfaces — no domain is read until that explicit user grant is recorded;
• https://www.facebook.com/marketplace/* — only the pages of the signed-in user's own Marketplace listings.

The active-tab URL is read transiently in memory. The Extension also keeps, in chrome.storage.local, a list of the dealer-inventory and Marketplace listing URLs it has already scanned so it can deduplicate work and reconcile state.

The Extension does not call the chrome.history API. The Extension does not read any browsing history, URL, page title, or visit time outside the host patterns above. The Extension does not see, read, log, or transmit any URL on any other website you visit. The Extension's optional_host_permissions declaration is used solely as the surface area that Chrome's own opt-in prompt can offer when you click "Add this dealer" inside the Extension popup — until that click and Chrome's grant, no other site is read.

3.3 Website content

On the host patterns where the Extension is permitted to run (your dealer inventory site plus facebook.com/marketplace/*), the Extension reads the following website content from the page DOM:

• From your dealer inventory site: vehicle title, stock number, price, year, make, model, mileage, and the URL of the vehicle's main photo.
• From facebook.com/marketplace/*: only the listings you yourself have posted — their title, price, listing URL, and post date. The Extension does not read other Facebook users' listings, posts, profile information, friend lists, messages, notifications, groups, or any Facebook surface outside the Marketplace pages used to manage your own listings.
• Operational diagnostic events fired by the Extension on these permitted sites. To keep the Extension working when Facebook or your dealer inventory site changes its DOM, and to help us reproduce bugs you report, the Extension transmits named operational events to leadeyepro.com. Each event records its operation name (for example, repair:price_drift_detected, autopost:fb_url_captured), a coarse timestamp, the Extension version, and a small structured payload that can include stock numbers, Facebook listing IDs, listing titles, listing prices, and counts of items processed. The Extension may also transmit sanitized DOM-structure snapshots of the Marketplace seller UI region when the parser cannot find an element it expects, an auto-post failure trace describing which form fields the Extension attempted to fill before failure, and an error / code-integrity report containing an error name and brief stack frame if the Extension's own code is corrupted at runtime. These transmissions are linked to your Employee Username and license key so we can match a support report to the user account that filed it. They never contain free-form messages, photos, financial information, passwords, or anything you typed into a non-Leadeye-Pro web page. They are not user-input tracking: the Extension does not capture mouse position, keystrokes, clicks, or scroll position.

3.4 Categories of user data the Extension does NOT collect

The Extension does not collect any of the following categories. The corresponding boxes on our Chrome Web Store Data Usage form are unchecked.

• Personally identifiable information. The Extension does not collect or process your real name, postal address, email address, phone number, age, date of birth, or government identification number. The Employee Username described in Section 3.1 is a pseudonymous login handle, not a real-world identifier.
• Health information. Not collected.
• Financial and payment information. Not collected. The Extension does not process payments. Subscription billing is handled outside the Extension.
• Personal communications. Not collected. The Extension does not read or transmit emails, SMS, chat messages, direct messages, or any other personal communications.
• Location. Not collected. No GPS, no precise location, no regional location, no IP-based geolocation. As with any web service, our HTTPS edge transiently logs the public IP your browser connected from for spam-and-abuse defence only (see Section 7.3); that IP is never resolved to a location, never joined to your account record, and is rotated out within 30 days.
• User activity. Not collected. The Extension does not perform network monitoring, click tracking, mouse-position tracking, scroll tracking, or keystroke logging. The operational diagnostic events described in Section 3.3 describe what the Extension itself did on permitted sites; they do not capture user input.

4. How we handle and use the data we collect

Each of the three categories enumerated in Section 3 is handled and used only as follows. We do not process user data for any purpose unrelated to the Extension's single purpose.

4.1 Use of Authentication information

• The hashed password is used to verify your identity at sign-in. It is never used for any other purpose.
• The license key is used to verify your dealership's subscription is active. It is never used for any other purpose.
• The Employee Username, dealership store name, and optional display name are used to identify your account, to attribute leaderboard activity and dealership metrics to the correct staff member, and to scope shared dealer-inventory data to your own dealership organization. They are not used for marketing email, push notifications, or any unrelated purpose.
• The device identifier is used only to enforce subscription seat counts on your license and to correlate code-integrity reports from the same workstation. It is not used for advertising, profiling, behavioural targeting, or cross-site tracking.

4.2 Use of Web history

The active-tab URL is used only to decide whether to inject the Extension's overlay on the two declared host patterns. The list of dealer-inventory and Marketplace listing URLs the Extension has scanned is held locally so the Extension can deduplicate and reconcile listings; when cloud sync is enabled, the same list is synchronized to the cloud for team continuity. This list is never sold, rented, transferred to advertisers, or used to build a browsing profile.

4.3 Use of Website content

• Vehicle data scraped from your dealer inventory site is used to auto-fill Facebook Marketplace listing forms when you click "Post to Facebook" on a row.
• Metadata about your own Facebook Marketplace listings is used to reconcile your inventory: detect price mismatches, surface sold listings, and match the correct dealer stock number to the correct Marketplace listing.
• Operational diagnostic events, DOM-structure snapshots, auto-post failure traces, and error / code-integrity reports are used only to (i) investigate support requests you submit, (ii) fix bugs in the categorizer, sync pipeline, and auto-poster, and (iii) monitor aggregate Extension quality (counters, success/failure rates, version distribution) so we can prioritise the next release.

Website content is not used for advertising, profiling, creditworthiness, behavioural targeting, training of generalized AI or machine-learning models, or any unrelated purpose. It is not sold, rented, or transferred to any third party.

5. With whom we share user data

We do not sell, rent, lease, trade, or transfer any of the user-data categories listed in Section 3 to third parties for advertising, marketing, profiling, creditworthiness, lending, AI-model training, or any purpose unrelated to the Extension's single purpose. User data is shared only in the following narrow circumstances:

• With authorized Leadeye Pro engineering and support personnel — strictly for the support, debugging, and abuse-investigation purposes described in Section 4.3. These personnel are bound by confidentiality obligations, may only access the minimum data necessary to investigate a specific issue, and may not use the data for any other purpose.
• With other authorized staff of your own dealership organization — when you opt into cloud sync, your dealership colleagues share an authoritative match map between dealer inventory and Marketplace listings. Data is never shared across separate dealership organizations.
• With infrastructure subprocessors strictly for hosting and delivery — we use MongoDB Atlas (managed database), Amazon Web Services (compute and object storage), and Cloudflare (HTTPS edge, DNS, and bot-and-DDoS defence). These subprocessors process data only on our behalf, are bound by data-protection agreements, and may not use the data for their own purposes.
• With Facebook / Meta — when you, as the logged-in Facebook user, post or update a Marketplace listing, the Extension submits listing content to Facebook through Facebook's own UI. Facebook's handling of that content is governed by Facebook's Privacy Policy, not by this one.
• With third-party LLM providers (Google Gemini and OpenAI) — only when you explicitly request AI-assisted description text for a listing, and only the active vehicle's specifications (year, make, model, mileage, declared features) are sent. No authentication information, no web history, no other website content, and no unrelated content is sent. The LLM providers are bound by their own enterprise data-protection terms and do not use these requests to train their public models.
• If required by law — if we are compelled by valid legal process, or if disclosure is necessary to protect the rights, safety, or integrity of Leadeye Pro or its users.
• In a business transfer — if Leadeye Pro is acquired or merges with another entity, user data may be transferred to the successor, which will remain bound by this Privacy Policy or by a successor that is no less protective.

6. AI-assisted features

The Extension includes an optional "Generate listing description" feature that produces marketing-copy text for a Facebook Marketplace listing. When you click that button, and only when you click that button, the active vehicle's specifications (year, make, model, mileage, declared features) are sent to a third-party LLM API (currently Google Gemini and OpenAI) through our backend at leadeyepro.com. No authentication information, no web history, no other website content, and no unrelated content is sent. The prompt and the generated description are not retained by Leadeye Pro for model training; they are forwarded in real time and discarded as soon as the response returns. The LLM providers do not use these enterprise-API requests to train their public models.

7. Where we store user data

7.1 Local storage in your browser

The following data is stored locally in your browser using the chrome.storage.local API and never leaves your device unless you explicitly transmit it to our servers (see Section 7.2):

• Cached dealer inventory data (Website content)
• The list of dealer-inventory and Marketplace URLs the Extension has scanned (Web history)
• Per-listing match associations between your inventory and your Marketplace listings (Website content)
• Button states for individual listings, such as "posted" or "needs price update" (Website content)
• Your saved Extension preferences and UI state

Local data is retained until you uninstall the Extension, clear the Extension's browser storage, or click "Clear cached data" in the Extension's Settings. Uninstalling the Extension automatically deletes all chrome.storage.local data with no manual cleanup required.

7.2 Cloud storage on Leadeye Pro servers

If — and only if — you have an active Leadeye Pro account and are signed in, the following subset of data is transmitted over HTTPS using TLS 1.2 or higher to our backend at leadeyepro.com:

• Your Employee Username, hashed password (one-way bcrypt), dealership store name, optional display name, license key, and device identifier (Authentication information) — transmitted to /api/auth/*, /api/ext/license-status, and /api/security/report.
• The list of dealer-inventory and Marketplace listing URLs the Extension has scanned (Web history) — transmitted to /api/cloud-sync/*.
• Confirmed match associations between dealer inventory items and your Facebook Marketplace listings, metadata about your own Facebook listings, and per-listing button states (Website content) — transmitted to /api/cloud-sync/* and /api/shared/inventory.
• Operational diagnostic events, DOM-structure snapshots, auto-post failure traces, and error / code-integrity reports (Website content, as described in Section 3.3) — transmitted to /api/debug-master-log, /api/debug-stream/batch, /api/debug-logs/auto-post-failure, /api/dom-fingerprints, and /api/security/report.
• Vehicle specifications for AI-assisted description generation (Website content), only when you click "Generate description" (see Section 6) — transmitted to the LLM provider's API through our backend, never directly from your browser.

Cloud data is stored in a managed MongoDB Atlas database operated by Leadeye Pro LLC. Data is encrypted in transit using HTTPS / TLS 1.2 or higher and encrypted at rest by the underlying database provider.

7.3 Server access logs

Like every web service, our HTTPS edge logs request metadata for each API call: the public IP address your browser connected from, the HTTP method and path, response code, request timestamp, and user-agent string. These logs are used solely for transient spam, abuse, and intrusion defence; they are rotated out automatically within 30 days, are not joined to your account record, and are not used to build a location profile, behavioural profile, or any kind of advertising profile.

7.4 Data retention

• Local browser data — retained until you uninstall the Extension, clear browser storage, or click "Clear cached data" in Settings.
• Cloud-synced account data — retained for the lifetime of your active account. You may request deletion at any time by emailing support@leadeyepro.com; we complete deletion within 30 days of the request. After account closure, account data is purged within 90 days unless a longer period is required by law.
• Operational diagnostic events, DOM snapshots, auto-post failure traces, code-integrity reports — retained up to 90 days, then automatically rotated out. They may be retained longer if attached to an open support ticket or active abuse investigation, in which case they are deleted within 30 days of ticket closure.
• Server access logs (HTTPS request metadata only) — retained up to 30 days, then automatically rotated out.
• AI-assisted description requests — not retained by Leadeye Pro at all. Forwarded to the LLM provider in real time and discarded as soon as the response returns.

7.5 Security

We implement appropriate organizational and technical security measures, including HTTPS / TLS 1.2 or higher for all data transmission, one-way bcrypt password hashing, scoped database access, role-based admin controls, and standard cloud-provider security baselines. No security control is perfect, but we minimise the data we retain and the time we retain it.

8. Your rights and choices

• Access. You can review the data the Extension stores about you through the Extension's Settings UI (locally cached data) or by emailing us (cloud-stored data).
• Correction. You can edit your Employee Username, dealership store, display name, and password from the Extension's Settings UI.
• Deletion. Local data is deleted when you uninstall the Extension or clear the Extension's browser storage. To delete cloud-stored data, email support@leadeyepro.com; we action requests within 30 days.
• Portability. Email us to request a machine-readable export of your cloud-stored account data.
• Withdraw consent. You can disable cloud sync, sign out of the Extension, or uninstall the Extension at any time.

9. Children's privacy

The Extension is intended for business use by automotive dealership staff and is not directed at, or knowingly used by, children under 13 (or 16 in jurisdictions where that is the applicable age). We do not knowingly collect data from children.

10. International users

Leadeye Pro is operated from the United States. If you access the Extension from outside the United States, you understand and agree that your data may be transferred to, stored in, and processed in the United States. We rely on standard contractual clauses or equivalent mechanisms with our subprocessors where required by law.

11. Changes to this policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. Material changes will be reflected in an updated "Effective and last updated" date above and, where appropriate, surfaced inside the Extension's UI on next launch.

12. Contact us

If you have any question, concern, or request regarding this Privacy Policy, please contact us:

Email: support@leadeyepro.com
Postal: Leadeye Pro LLC, c/o Privacy, United States.

© 2026 Leadeye Pro LLC. All rights reserved.