Privacy Policy
Last updated: October 21, 2026
LaneScout (“we,” “us”) is a product of M8 LLC. It includes the LaneScout Chrome extension, which shows broker-risk signals on the DAT One load board; the optional Gmail protection and mailbox bot; and LaneScout Mail Guard, an email-protection service for companies. This policy explains what data we handle, why, who else receives it and how long we keep it. See also our Terms of Service.
- We do not collect your browsing history.
- We do not store, resell, or redistribute DAT’s load data (rates, lanes, postings).
- The only data that leaves your browser for a lookup is the broker identifier on a posting — company name, phone, email, and/or MC number.
- The optional Gmail protection is off by default. If you turn it on, only a few technical details of a message, such as domains and link hostnames, are checked with us — never your email content and never anyone’s email address.
- We do not sell your data or use it for advertising.
- Creating an account is optional. If you do, we store your email to authenticate you.
What the extension reads
When you are on one.dat.com, LaneScout reads the load rows already shown 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
- Risk lookups. To place a badge, the extension sends the broker identifier (company name, phone, email or MC number) to the LaneScout service, which returns risk signals based on public FMCSA data. We do not send the rate, lane, commodity, or any other load detail. When you expand a load or open its details, the lookup may also include email domains, email addresses or phone numbers written into that posting’s comments, so they can be checked too. Only those identifiers are sent; the comment text is read in your browser and never leaves your device.
- A broken board. If the extension cannot find any loads on a DAT page (usually because DAT changed its page), it tells us which board it was and the extension’s version, at most once a day, so we can fix it. Nothing from the page, and nothing about you or your account.
- Account sign-in (optional). If you sign in, your email address and sign-in tokens are handled by our authentication provider to create and keep your session. Google sign-in uses Google’s standard sign-in; we receive only your email and basic profile. Signing out ends the session on our side too.
- Community reports (optional, signed-in only). If you report a contact you believe impersonates a real broker, we receive that contact and your user ID so the report can be reviewed before it affects anyone’s badge.
- Outcome reports (optional, signed-in only). If you record how a booking went, we receive the broker identifier and your answer.
- Possible impersonations. When a contact you look up appears to imitate a different, registered broker, our service records that contact, the broker it appears to imitate and how often it has been seen, so a person can review it. This adds nothing to what your browser sends, and the record is not linked to you: no user ID, IP address or install identifier is kept with it. Nothing is shown to anyone unless a LaneScout reviewer approves it.
- AI summaries (optional, paid feature). If you open the AI briefing for a broker, the risk signals already found for that broker (never DAT load data or comment text) are sent to our AI provider to write a plain-language summary.
We do not send your browsing history, keystrokes, location, or the contents of the load board beyond what is described above.
Gmail phishing protection (optional — off by default)
LaneScout can flag emails that look like fraud aimed at freight companies, such as fake FMCSA notices or
look-alike broker addresses. 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 with the same switch, which also releases the
permission.
- The message is read in your browser. The sender, subject, text, links, attachment names and the message’s technical headers are examined locally.
- What leaves your browser: only the sender’s email domain (for example
example.com, never the address), the domains of links in the message and of the reply-to address, any MC numbers the sender cites, and the address of the mail server that delivered the message (a server’s, not a person’s). - Never sent: the subject, the text, the headers themselves, sender or recipient addresses, attachments or their names, or anything else about your mailbox.
- What we keep: no record of which user, message or mailbox a check came from. We keep results about public records (such as a domain’s registration date) keyed only by that domain or server, so the same lookup isn’t repeated.
- Your sender history stays on your device. To tell a look-alike from someone you really deal with, the extension remembers who has written to you (company domains, or the full address for a free-mail sender, with counts and dates, never subjects or text). It stays in Chrome’s storage on your computer, is never sent to us, and the popup shows its size and clears it.
- One exception, about the domain, not about you: if the sender’s domain appears to imitate a registered broker, we record that domain for review, as described under “Possible impersonations” above — never the address, the message, or anything identifying you or your mailbox.
The LaneScout mailbox bot (optional — installed by you)
The mailbox bot is a script you install into your own Google account. It runs the same checks as the Gmail protection on new inbox messages and labels conversations that raise signals (LaneScout/…). It works with the Gmail permissions you grant it in your account and never sends, moves, archives or deletes mail. It sends LaneScout the same short list as the Gmail protection above, and only if you give it an API key; without one, nothing leaves your Google account. Its sender history is kept in the script’s private storage in your account, and uninstalling it deletes that history.
LaneScout Mail Guard (for companies)
Mail Guard is a service a company turns on for its own Google Workspace or Microsoft 365 email. The company’s administrator authorizes it in the company’s Google or Microsoft admin settings, chooses which mailboxes it protects, and can withdraw that authorization at any time. Mail Guard acts on the company’s instructions, and the company decides who in it can see the results. Where this section says Gmail, read Outlook for a Microsoft 365 company.
- What it reads: each new email that reaches a protected mailbox (its headers, text, links and attachments) in order to check it, and once, the headers of the mailbox’s past mail, to learn who the company corresponds with. Email text and attachments are checked and then discarded; they are not stored.
- What it writes to the mailbox: a LaneScout label on an email that raises signals and, if the company keeps notes on, a short note in that mailbox explaining what was found and how to check it. The note is never sent, and nobody outside the mailbox receives it. In dashboard-only mode Mail Guard writes nothing. It never sends, deletes, moves, archives or edits email.
- The AI analyst: unless the company switches it off, Mail Guard has an AI model read the emails that need a closer look. For those emails it sends our AI provider the email (sender, recipients, subject, date, text, link destinations, attachment names and some attachments) and what Mail Guard knows that helps judge it, such as its findings, the company’s past dealings with that sender, the last four digits of bank accounts that sender used before, and whether the team marked earlier emails from them genuine. The provider processes this only as our service provider, to produce the reading; its terms do not allow it to train its models on this data and limit how long it may keep it. Mail Guard keeps the analyst’s reading with the finding.
- Bank details: when an email gives bank details, Mail Guard keeps a one-way fingerprint of the account and its last four digits — never the full numbers — so a change of account can be noticed.
- The team’s answers and questions: when someone marks a finding genuine or not genuine, Mail Guard keeps who, when, and their note. Questions someone asks the analyst are sent to our AI provider with the finding and the email; Mail Guard keeps only who asked, when, and about which finding.
- Emails forwarded for a check: if someone at the company forwards an email to Mail Guard to have it checked, Mail Guard reads it once and emails the answer back to that person. It keeps only a record that a check was asked for and its result. Only addresses at a protected company are answered.
- Learning from answers: when a finding is settled, Mail Guard keeps an anonymous record of it (which checks fired, the type of sender and the outcome), without the email’s text, subject, addresses or domains. These records are kept for two years, deleted with the company’s other data, and used to improve Mail Guard.
- The company directory: Mail Guard uses read-only directory access to confirm that the person turning it on is an administrator and to list the company’s people when an administrator chooses mailboxes. It keeps only the addresses of the chosen mailboxes and of that administrator.
- What it keeps: a summary of who the company corresponds with (a company’s domain, or the full address of a free-mail sender, with message counts and similar details; phone numbers only as one-way fingerprints). For an email that raised signals: the sender’s address and the findings (kept 365 days) and the subject line (kept 90 days). Emails that raise nothing leave only a “checked” marker (30 days) and a daily count.
- What leaves the service: the same technical details as the Gmail protection above, checked against LaneScout’s own data and public records; the emails the analyst reads, sent to our AI provider as described above; and, to check a single link, phone number or domain, just that item — never the email — sent to a provider that looks it up.
- Alerts: if a company turns on alerts, Mail Guard emails the people the company chooses about emails to verify, and sends security alerts (for example, if Mail Guard loses its access) to the company’s backup contact by email and, if a mobile number is given, by text message. These are delivered by our email and text-message providers. LaneScout’s own copy of a security alert says only what kind of alert it was and for which company.
- Who sees findings: the company’s Mail Guard administrators see the company’s; each protected mailbox’s owner can see their own. LaneScout staff can see a company’s settings and findings to run and support the service.
- Deletion: removing a mailbox deletes its findings; when a company leaves, everything Mail Guard stored for it is deleted. A trial or subscription that ends pauses protection and deletes nothing, so the company can resume; a company can ask for deletion at any time.
- Billing: Mail Guard subscriptions are paid through our payment processor, as described under Payments below.
What is stored on your device
The extension keeps recent lookup results in Chrome’s storage so the same brokers aren’t looked up again: up to 2 hours for a Caution or High Risk result and up to 24 hours for a Clear one. Results from a single load’s comments are never kept. If you have an account, your sign-in session is kept too. If you use the Gmail protection, the sender history described above is kept as well. You can clear all of this by removing the extension or clearing its storage; the sender history also has its own Clear button.
Data we store on our servers
- Account: your email address, account identifiers and plan.
- Reports and outcomes you submit: the broker or contact, your user ID, and your submission.
- Usage records: if you have an account, minimal records needed to run the product, for example how many broker details you opened (for plan limits) and which flagged brokers you reviewed. These never include DAT load data.
- Uninstall feedback, if you give it: when you remove the extension, a page asks one question. If you answer, we store your answer and the extension version — not your name, email, account, IP address or any identifier that could connect the answer to you. Closing the page stores nothing.
- Possible impersonations: a contact, the broker it appears to imitate, and how often it has been seen. Not linked to any user.
- Public FMCSA data: broker records we refresh from public FMCSA data. This is public data about businesses, not about you.
We do not store the load postings you view or any DAT proprietary data.
Payments
Paid plans are handled by our payment processor. You enter your payment details on the processor’s own secure page; we never see or store your card number. We store only the processor’s customer and subscription references and your plan, so we can give you access and let you manage your subscription.
Who else receives data
- We do not sell or rent your data.
- We share data only with service providers that run parts of LaneScout for us and may use it only to do so: hosting and data storage, sign-in, payments, AI processing, email and text-message delivery, and website analytics. Mail Guard customers can ask for the current list of these providers at the address below.
- We may disclose data if the law requires it.
- We do not use the data for advertising, and we do not turn on Google’s advertising or ad-personalisation features in our website analytics.
- The extension itself contains no analytics or tracking. The analytics described below run on the lanescout.io website only.
- We do not keep a record of which postings, brokers or messages you looked at to build our list of reported contacts. Business customers can receive reviewer-approved flagged contacts; that list carries the contact and the company it imitated, and nothing about any LaneScout user.
Website analytics (lanescout.io only)
Most pages of this website use Google Analytics so we can see how many people find the site and which pages they read. This is separate from the extension.
- What it collects: pages viewed, approximate location, device and browser type, and
the site or search that referred you. It sets a cookie (
_ga) so repeat visits are not counted as new people. - Pages without it: the flag dispute form, the uninstall feedback page, and pages where you are signed in as a customer.
- Never joined to: your LaneScout account, your lookups, or anything the extension does.
- Opting out: a content blocker or your browser’s tracking protection stops it, as does Google’s Analytics opt-out add-on. Nothing on this site needs analytics to work.
The nature of the signals
LaneScout shows informational signals based on public data; they are decision aids, not a determination or accusation about any company or person. Always verify independently before making a booking decision. LaneScout is not affiliated with DAT Solutions or FMCSA.
Security, retention and deletion
Data is encrypted in transit and access is limited to the people who run the service. We keep encrypted backups so the service can be restored after a failure; each backup is deleted after 90 days, so anything removed from the service is gone from backups within 90 days as well.
Lookup results on your device expire within 24 hours. To delete your account and the reports and outcomes linked to 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