LaneScout

Privacy Policy

Last updated: August 28, 2026

LaneScout (“the extension,” “we,” “us”), a product of M8 LLC, is a Chrome extension that displays public, FMCSA-derived broker-risk signals on the DAT One load board. This policy explains exactly what the extension does and does not do with data. It is written to be accurate to the code, not aspirational. See also our Terms of Service.

The short version

What the extension reads

When you are on one.dat.com, LaneScout reads the load rows already rendered in your browser to find, per posting, the broker’s company name and one contact (phone or email), and — only when you expand a load — the MC number. This happens locally in your browser. The extension reads no other site, with one exception you control: if you turn on the optional Gmail protection (below), it also reads opened messages on mail.google.com — and Chrome asks for that permission separately when you enable it.

What is sent off your device, and to whom

  1. Risk lookups. To place a badge, the extension sends the broker identifier (company name / phone / email / MC number) to the LaneScout lookup service (a Cloudflare Worker). The service returns risk signals derived from a mirror of public FMCSA data. We do not send the rate, lane, commodity, or any other load detail.
    When you open a load’s dossier, this also includes any contact identifiers — email addresses or phone numbers — written into that posting’s comments, so they can be checked against the list of contacts reported for impersonation. Only the identifiers themselves are sent; the comment text is parsed in your browser and never leaves your device.
  2. Account sign-in (optional). If you sign in, your email address and authentication tokens are handled by Supabase (our authentication provider) to create and maintain your session. Google sign-in is offered via Google’s standard OAuth; we receive only your email and basic profile.
  3. Community reports (optional, signed-in only). If you report a contact you believe impersonates a real broker, we send that contact identifier and your user ID so the report can be moderated before it ever affects anyone’s badge.
  4. Outcome reports (optional, signed-in only). If you record how a booking went, we send the broker identifier and your outcome selection.
  5. Automatic impersonation detections. When a broker identifier you look up closely resembles a different registered broker’s FMCSA-listed email domain, our service records that observation so a human reviewer can decide whether that contact belongs on our reported-contact list. This adds nothing to what your browser sends — the comparison already runs to produce the badge, and we now keep the result instead of discarding it. We record the domain, which registered broker’s domain it resembles, and how many times it has been seen. We do not record who saw it: no user ID, no IP address, no install identifier is attached to a detection, so there is no record connecting one to you. Nothing is shown to anyone — not on a badge, not to the broker, not to our business customers — unless a LaneScout reviewer approves it, and most are never approved.
  6. AI summaries (optional, paid feature). If you open the AI briefing for a broker, the already-computed risk signals for that broker (not any DAT load data) are sent to our AI provider (Anthropic) to generate a plain-language summary. The load’s posted comments are parsed in your browser; only the resulting signals — never the comment text — are included.

We do not send your browsing history, keystrokes, location, or the contents of the load board beyond the broker identifier described above.

Gmail phishing protection (optional — off by default)

LaneScout can flag emails that reference FMCSA/DOT but come from non-government addresses, and “portal”/“sign-in” links that lead somewhere other than an official .gov site. This feature is off by default: it does nothing until you switch it on in the extension popup, at which point Chrome asks you to grant access to mail.google.com. You can turn it off at any time from the same toggle, which also releases the permission.

What is stored on your device

The extension caches broker lookup results in Chrome’s local storage for up to 24 hours (so the same brokers aren’t re-queried), plus your sign-in session if you have an account. You can clear this at any time by removing the extension or clearing the site’s storage.

Data we store on our servers

We do not store the load postings you view or any DAT proprietary data.

Payments

Paid plans are processed by Stripe, our payment processor. When you subscribe, you provide your payment details directly to Stripe — we never see or store your full card number. We store only your Stripe customer/subscription identifiers and your plan status so we can grant access and let you manage your subscription. Stripe’s handling of your payment data is governed by Stripe’s Privacy Policy.

What we do not do

Website analytics (lanescout.io only)

Since 7 August 2026 most pages of this website load Google Analytics 4 so we can see how many people find the site and which pages they read. This is ordinary website measurement and it is separate from the extension.

The nature of the signals

LaneScout shows informational signals derived from public data; they are decision aids, not a determination or accusation about any company or person. FMCSA data is mirrored periodically, so the detail panel shows the date the data was pulled. Always verify independently before making a booking decision. LaneScout is not affiliated with DAT Solutions or FMCSA.

Data retention and deletion

Cached lookups expire within 24 hours on your device. To delete your account and the reports/outcomes associated with it, contact us at the address below and we will remove them.

Children

LaneScout is a business tool and is not directed to children under 13.

Changes

We may update this policy; the “Last updated” date above will change. Material changes will be noted in the extension’s changelog.

Contact

LaneScout, a product of M8 LLC — privacy@lanescout.io