Privacy & Messaging Policy
FreightScout, Inc. ("FreightScout," "we," "us") builds execution intelligence for freight brokerages. This policy covers the FreightScout platform, which is our only product, and explains what data we collect, how we use it, and the specific ways we handle your connected email and calendar, the SMS/text messages we send, and the location a driver shares through our driver app, FreightScout Driver. It is written to be read plainly by the people who use our software.
Who We Are
FreightScout, Inc. is a Delaware corporation headquartered in Wilmington, DE. Our platform helps freight brokerages coordinate loads and carriers, hand a shift over, and find and keep customer freight. SalesScout was an earlier name for part of this platform. It is retired as a public brand: gosalesscout.ai redirects to freightscout.ai and there is no separate SalesScout product to buy. You can reach us any time at privacy@freightscout.ai.
What Data We Collect
Account information. When your brokerage onboards, we store your name, work email address, brokerage affiliation, role, and, where you provide it, a work phone number. This is typically supplied by your brokerage administrator during setup.
Operational & CRM data. To power the product we store load records, carrier and contact records, lane and rate data, pipeline status, and outreach history. This is the working data of your brokerage and is scoped to your organization.
Connected email & calendar content. If you connect a Google or Microsoft account via OAuth, we store encrypted authentication tokens. The scope of what we access is deliberately narrow and is described in detail below.
Call & SMS logs. When our platform places operational voice calls or sends text messages as part of brokerage operations, we log metadata (phone numbers involved, timestamps, delivery status) and message content for the purpose of coordinating loads, recordkeeping, and support. Consent and opt-out handling for SMS are described in the Messaging section below.
Usage data. We log interactions with the platform (queries, brief requests, sends) to improve service quality and to provide activity reporting to brokerage managers.
Website visit data. When you browse our public website, analytics and advertising tags may record pages viewed, referring page, approximate location derived from IP address, and general device and browser information. This is separate from the product data above and applies to anyone visiting the site, whether or not they are a customer. It is described in full in the next section.
How We Use Data
We use product data solely to operate and improve the product for your brokerage: to run the agents and workflows you enable, to send outreach and operational communications you or your brokerage approve, to provide reporting to your managers, and to support and secure the service. We do not sell, rent, or trade that product data, and we do not use it for third-party advertising. Website visit data is separate and is described next.
Your freight data is not training data. Your load, lane, rate, carrier, margin and contact data is used to run the product for your own brokerage and for nothing else. We do not use it to train generalized AI or machine-learning models. It is not shown, sold, licensed or made available to any other customer of ours, and it is not pooled with any other customer's data to build a shared model, index, benchmark or rate product. What the product learns from your data stays scoped to your brokerage.
Website Visitors, Cookies, Analytics and Advertising
This section covers our public website only. It does not apply to data inside the product, which is governed by the sections above.
What we use. Our public website uses GoHighLevel for site analytics, plus advertising pixels from Meta (Meta Pixel), Google (Google tag for Google Ads and GA4), and LinkedIn (LinkedIn Insight Tag). Each of these sets cookies or similar identifiers in your browser.
Forms on this website. The contact form and the scorecard form post to Formspree, which receives and forwards the details you type into them. Formspree processes that submission on our behalf; it is not used for anything inside the product.
Those tags record the pages you view, the page that referred you, an approximate location derived from your IP address, and general device and browser information. They do not receive your brokerage's operational or CRM data, and they are not an SMS tool.
Why. GoHighLevel helps us see which pages and topics are useful, measure whether our marketing reaches the right people, and, where you have given us your details through a form or a booking link, connect your inquiry to the pages you read before it.
The Meta, Google, and LinkedIn tags are used for advertising measurement, attribution, and audience building on those platforms, in addition to site analytics. We do not sell or rent website visit data.
Your choices. This tracking is not required to browse the site and nothing on the site is withheld if you block it. You can refuse or delete these cookies in your browser settings, or use a browser or extension that blocks analytics and advertising scripts, without losing access to any page. If you would like us to delete website visit data already associated with you, or to stop processing it, email privacy@freightscout.ai and we will do so.
Consent. When your browser's timezone indicates you are in the United Kingdom, the European Union or the wider European Economic Area, we ask before anything loads. None of these vendor scripts are requested until you choose Accept, and choosing Decline is remembered on that browser and respected on every later visit. Elsewhere the scripts load by default.
We use the timezone your browser reports because it needs no location lookup and no third party. It is a signal rather than a location, so we made it deliberately over-inclusive: anything we cannot positively read as non-European, including an empty, UTC or generic timezone of the kind privacy-hardened browsers report, is treated as European and is asked. The case it still misses is a European resident whose device reports a non-European zone, through a VPN or a changed clock.
The basis for loading them elsewhere, and the remedy if we got you wrong. Outside the UK, EU and EEA we load analytics and advertising cookies on the basis of notice and opt-out: this policy is the notice and the control below is the opt-out, which works before and after the scripts have loaded. Three things hold no matter what the timezone said. A Global Privacy Control signal from your browser is a refusal everywhere, honoured without asking. The control below is open to every visitor in every country, takes effect at once, and clears identifiers already stored here. And a refusal is remembered on that browser and respected on every later visit, so you are never asked twice.
Turn analytics and advertising cookies off. This applies to any visitor in any country, takes effect immediately, is remembered on this browser, and also clears analytics cookies already stored here that the browser will let a script reach.
Global Privacy Control. If your browser sends a Global Privacy Control signal, we treat it as a refusal everywhere, regardless of region and without asking. None of these vendor scripts are requested.
Hosting analytics. Some pages also load Vercel Analytics, provided by our hosting platform, which records aggregate page-view counts and sets no advertising cookies.
Email & Calendar Integration (Google & Microsoft OAuth)
When you connect your work email or calendar, we request only the permissions required for the specific feature you are using:
Google Gmail: gmail.send, and, where your organization's Google Workspace administrator has authorized FreightScout, gmail.readonly. Send is used only to send emails that you compose or approve within the product, from your own address. Read access is requested only from people whose address is on an email domain your administrator has confirmed, and each person grants it for their own mailbox. Nobody can connect another person's mailbox, and we never read a mailbox nobody connected.
Google Calendar: calendar.events. Microsoft Calendar: Calendars.ReadWrite. We read the times, titles and attendees of the meetings on your primary calendar for three purposes: to show your calendar alongside your FreightScout meetings in the product, to offer only the times you are free on your booking page, and, if you enable the meeting-prep / notetaker assistant, to identify which meetings it should prepare for or join. We create an event on your calendar in one case only: when someone books a time you offered them on your booking page. That event carries the booker's email address and any note they left, and no invitation is sent from your calendar when it is created. We do not change or delete any event on your calendar. If you connected your calendar before we began asking for permission to create events, your connection stays read-only until you reconnect it.
Microsoft Outlook: Mail.Send (send on your behalf), Mail.Read (read your mailbox), offline_access (maintain the connection without repeated sign-ins), and User.Read (identify your account).
What the Outlook read scope actually does. When you connect an Outlook mailbox, FreightScout keeps a working copy of that mailbox inside the product, so you can search, read and reply to your freight email without leaving it and so the product can tell when someone has replied to a message you sent. A background job refreshes that copy about every two minutes and works backwards through the mailbox until it reaches the beginning. That is a copy of the mailbox, not reply detection alone, and we would rather write it down than let a reader infer something narrower from the scope name.
What is copied. Sender and recipients, subject, message body, the time a message was sent or received, read state, importance, folder and conversation identifiers, and the file names of attachments. Attachment contents are not copied by this job. Where your brokerage runs our email classification agent, messages in the copy are also classified by an AI model to mark which are freight relevant and to match them to a load, a carrier or a customer. That classification uses the model provider named in Who Processes Your Data below, under terms that do not permit the provider to train on your content.
Where it goes, and how long it stays. The copy is stored against your brokerage's organization only, under the same row-level security as the rest of your data, and no other customer can reach it. Delete a message in Outlook and our copy of it is deleted too, the next time the job runs. Disconnect the mailbox, or have your administrator deactivate you, and the tokens are deleted immediately and the copy stops being refreshed. Ask us and we delete the copy itself. The full retention position is in the table under Data Retention.
What Gmail read access is used for. Two things. Reply detection: we check a connected mailbox for replies to emails that were sent from FreightScout, so follow-ups stop once someone has replied and you can see who responded. We store the text of those replies with the email they answer, and, where your brokerage has turned on thread sync, a short record of each email thread with a snippet of its latest message. Document capture: your administrator can connect a shared mailbox, such as the one your proof-of-delivery paperwork arrives at, by signing in as that mailbox. We read the attachments that arrive there into your brokerage's document queue, and we never send from it. Unlike an Outlook connection, we do not keep a copy of your whole Gmail mailbox.
AI processing. Some features use an AI model to work with email content: judging whether a reply is interested, suggesting a response, and answering questions you ask Scout about your email. That content is sent to the model provider named in Who Processes Your Data only to produce that result for you, under terms that do not allow the provider to train on it. Google Workspace APIs are not used to develop, improve, or train non-personalized AI and/or ML models.
Who at FreightScout can see Gmail content. Nobody, in the normal course of our work. Gmail content is hidden from FreightScout staff even when they open your workspace to help you. We read it only with your consent for specific messages, when it is necessary for security purposes such as investigating abuse, or to comply with applicable law.
Limited Use disclosure. FreightScout's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not transfer or use Google user data to serve advertisements, and we do not allow humans to read this data unless we have your affirmative consent for specific messages, it is necessary for security purposes (such as investigating abuse), to comply with applicable law, or the data has been aggregated and anonymized. We do not use Google user data to train generalized AI/ML models.
SMS & Messaging (A2P 10DLC)
FreightScout sends operational text messages as part of freight brokerage operations managed through our platform. This section is our SMS/messaging disclosure and applies to every messaging program we register.
What the messages are
Messages are transactional, freight/logistics operational communications tied to active shipments and business relationships. For example: load check-calls and status requests, driver and carrier coordination, appointment and pickup/delivery scheduling, and shipment status notifications. Messages are not marketing and are not sent to consumers for promotional purposes.
Consent. We send SMS messages only to individuals who have a direct business relationship with FreightScout or its customer brokerages (such as carriers, drivers, and dispatch contacts) and who have provided their mobile number and agreed to receive operational text messages. Consent is collected in these ways:
1. On our website. Our contact form includes an optional, unchecked SMS consent checkbox alongside the field for your mobile number. It is separate from the checkbox that accepts our Terms & Conditions: accepting the Terms does not grant SMS consent, and SMS consent is never required to submit the form. Checking the SMS box is what grants consent. It reads: "I agree to receive text messages from FreightScout, Inc. at the number provided about my inquiry, scheduling, and the loads and shipments we coordinate, including pickup and delivery updates, appointment reminders, location and ETA requests, and document requests. Message frequency may vary. Msg & data rates may apply. Reply STOP to opt out or HELP for help. Consent is not a condition of purchase or service." We record the fact of consent, the time it was given, and the version of that wording.
2. During carrier onboarding and load coordination. When a carrier, driver, or dispatch contact provides a mobile number for shipment coordination and agrees to receive operational text messages about the loads they are moving. This consent is taken by the brokerage that books the load, usually verbally by a dispatcher at booking, not by FreightScout.
Who holds the record, and what we can show you. The brokerage is responsible for obtaining that consent and for holding the record of it: who agreed, when, through which channel, and against which load or carrier. Our contract with every brokerage requires it. What FreightScout itself holds, and can show you on request for your own number, is the mobile number, every message sent to or from it with its time and delivery status, the load it was sent about where one is recorded, and every opt-out we have received from it. We do not hold a recording or a signature for a consent given verbally to a dispatcher, so if you ask us to prove your consent we will tell you which brokerage took it and put you in touch with them, and we will stop texting you the moment you ask, whatever the record says. Email privacy@freightscout.ai for either.
Providing a phone number alone is never consent. Consent must be granted affirmatively, and it is never a condition of any purchase or of using FreightScout. Consent is never purchased, rented, or shared with third parties, and mobile opt-in data is never shared with third parties for their own marketing.
Message frequency. Message frequency varies based on load and shipment activity. You may receive messages only when there is an active shipment or coordination need.
Cost. Message and data rates may apply, per your mobile carrier plan.
Opt-out. You can opt out of receiving text messages at any time by replying STOP (or END, QUIT, CANCEL or UNSUBSCRIBE) to any message. You may also email support@freightscout.ai or call (904) 467-2114 to request removal. After you opt out we will send one confirmation message and then send no further texts to that number unless you re-subscribe by replying START. Messages already queued may still arrive briefly.
Help. For help, reply HELP or INFO to any message, contact us at support@freightscout.ai, or call (904) 467-2114. Carriers are not liable for delayed or undelivered messages.
Mobile information and opt-in consent are never sold or shared with third parties or affiliates for their marketing or promotional purposes. Information may be shared only with the messaging service providers (such as our SMS aggregator and telecom carriers) strictly to deliver the messages you have agreed to receive.
Executive assistant messaging
Separately from the freight operational messaging described above, FreightScout operates an executive assistant line that sends and receives text messages to coordinate meetings on behalf of company leadership. This is a distinct messaging program with its own consent: opting in to one does not opt you in to the other.
Consent. Mobile numbers used for this purpose are provided directly by the recipient in the course of an existing business relationship, such as booking a meeting through our scheduling page, an email exchange, or an established partner or vendor relationship. Numbers are never purchased, rented, or obtained from third-party lists. Consent is never a condition of purchase, of a meeting, or of any business relationship with FreightScout, and you may withdraw it at any time.
Message types. Messages are conversational and two-way, and cover scheduling, rescheduling, meeting confirmations, and relaying messages. They are never marketing or promotional, and are never used for cold outreach.
Message frequency. Message frequency varies with meeting activity and is typically fewer than one message per recipient per day.
Cost. Message and data rates may apply, per your mobile carrier plan.
Opt-out. Reply STOP to opt out at any time. You may also email support@freightscout.ai or call (904) 467-2114.
Help. Reply HELP for assistance, email support@freightscout.ai, or call (904) 467-2114. Carriers are not liable for delayed or undelivered messages.
No third-party sharing. Mobile information, including phone numbers and messaging consent, is never sold, rented, or shared with third parties or affiliates for marketing or promotional purposes. It is shared only with messaging service providers strictly to deliver the messages the recipient has agreed to receive.
What we collect for SMS, and how long we keep it
When you opt in to receive text messages we collect and use your name, mobile number, email address, the details of your enquiry, your consent status and the time it was recorded, and our records of message delivery and opt-out. This is used only to respond to you, coordinate scheduling and shipments, provide service updates, maintain consent records, honour opt-out requests, and meet legal and regulatory obligations.
How long each of those is kept, why, and whether it survives a deletion request, is set out in one place: the table under Data Retention below. Nothing in this section overrides it.
Your SMS privacy rights
You may withdraw consent at any time without penalty, ask us for your SMS consent records, correct your mobile number, request deletion of your SMS data (subject to the retention obligations above), or raise a complaint about our messaging practices. To do any of these, email privacy@freightscout.ai or call (904) 467-2114.
Brand registration
FreightScout's brand and campaign registration under A2P 10DLC is approved and live with the carrier networks and our messaging aggregators, and it is maintained for as long as we send, so our messages are identifiable and traceable to us.
FreightScout Driver: the driver app
FreightScout Driver is a free phone app for truck drivers hauling a load booked by a freight brokerage that uses FreightScout. The brokerage texts the driver a link for one load. The app opens that load and, if the driver agrees, shares where the truck is with that brokerage until the load is delivered. There is no sign-up, no account and no password. This section covers what the app collects. The brokerage that booked the load decides how it uses the load's record, under its own contract with us.
Consent, one load at a time. The app never asks for location when it opens. On a load, it first explains in plain words what sharing means, and the driver chooses "Allow while on a load" or "Not now". A yes covers that one load only. The driver can stop sharing at any time from the Me tab, and the brokerage is told that tracking stopped. Sharing also ends by itself when the load is delivered or the proof of delivery is sent. We record each yes and each stop, with its time, against the load.
What the app sends us
Location while a load is shared. The phone's position (latitude and longitude), the time it was taken, and, where the phone reports them, its accuracy, speed and heading. Positions are taken more often near a stop and less often on the highway or when parked. On a shared load this continues with the screen off, which is why the phone asks for "Always" location; on Android a standing notice names the load and the brokerage while it runs. Nothing is recorded on a load the driver has not said yes to, or after sharing stops.
The driver's mobile number. It comes from the broker's texted link, not from the phone. It ties the positions to the right driver on the right load.
Stop updates. When the driver slides to mark arriving at or leaving a stop, the time of that tap. The app can also mark arrival and departure from the truck's position near the stop.
Photos the driver chooses to send. Paperwork such as a bill of lading, a proof of delivery, a lumper receipt or a scale ticket, and photos attached to a problem report. The app only sends a photo the driver takes or picks for that purpose. It does not read the rest of the photo library.
A random install id. The app makes its own random id when it is installed, to tell one phone's session from another. It is not the phone's hardware id or advertising id, and erasing the app's data deletes it.
What it does not collect
The driver's name, typed during the first opening, stays on the phone and is never sent to us. The app has no advertising or third-party analytics code, does not track the driver across other companies' apps or websites, and does not read contacts, messages or other apps. Location is never sold, and it is never used for advertising.
Who sees it
Positions, stop times and photos for a load go to the brokerage that booked it, inside its FreightScout workspace, under the same row-level security as the rest of its data. No other brokerage can see them. Where the brokerage has connected its own transportation management system, the load's stop times and positions are written back to it. The brokerage's customer for that load, usually the shipper, can get a tracking link that shows the truck's position between pickup and delivery only, never before pickup or after delivery. We do not share driver location with anyone else, except as required by law.
The map. The next-stop map loads its map images from OpenFreeMap, a free map tile service. As with any online map, a tile request shows that service roughly which area is on screen, along with the phone's IP address. The app sends OpenFreeMap no position, phone number or id.
Erasing the app's data
Because there is no account, there is no account to delete. In the app, Me, then "Sign out and erase this phone's data", stops tracking for the load, tells the brokerage, and erases everything the app keeps on the phone, the random install id included. Uninstalling the app also stops it. What has already been sent for a load is part of that load's record, and the Data Retention table says how long it stays and why. To ask about or request deletion of your records, email privacy@freightscout.ai; help with the app is at freightscout.ai/driver-app.
How We Protect Your Data
Encryption. All OAuth tokens (Google and Microsoft) are encrypted at rest using AES-256-GCM. Tokens are decrypted only in-memory at runtime by our backend service; raw tokens are never written to disk, included in logs, or exposed in any user-facing interface.
Key separation. Encryption keys are held as server environment variables, separate from the database, so a compromise of the database alone does not expose token data.
Access control. Database access is restricted to our backend service via a private service key, with row-level security enforced so each organization sees only its own data.
Automatic cleanup. When a user is deactivated by their brokerage administrator, associated OAuth tokens and email-connection data are automatically and permanently deleted.
Data Retention
You can ask us to delete your personal data at any time, and for most of what we hold we simply do it. A few categories survive a deletion request, and each one survives for a reason we can name. Rather than leave that spread across the document, here is the whole position in one table.
| What we hold | How long | Why we keep it | Does it survive a deletion request? |
|---|---|---|---|
| Account information: name, work email, role, brokerage, work phone | While your brokerage subscribes | To run your account | No. Deleted within 30 days of cancellation, or sooner on request. |
| Operational and customer-record data: loads, carriers, contacts, lanes, rates, pipeline, outreach history | While your brokerage subscribes | To run the product for your brokerage | No. Deleted within 30 days of cancellation, or sooner at your administrator's request. |
| The working copy of a connected Outlook mailbox | While the mailbox is connected. A message deleted in Outlook leaves the copy within minutes. | So you can work your freight email inside the product | No. Disconnecting the mailbox stops it, and asking us deletes it, within 30 days. |
| Content from a connected Gmail mailbox: reply text, thread records and snippets, and the text of alerts that quote them | While the mailbox is connected. If we lose access, 30 more days | Reply detection and the features described under Email & Calendar Integration | No. Disconnecting the mailbox deletes it automatically. If FreightScout loses access, for example because Google access was revoked or the password changed, we pause and tell you; if access is not restored within 30 days, it is deleted automatically. Documents captured into your document queue are business records and follow the operational-data row above. |
| OAuth tokens for a connected mailbox or calendar | Until you disconnect, or an administrator deactivates you | To hold the connection open | Deleted automatically on either event. No request needed. |
| SMS and voice logs: numbers, timestamps, delivery status, message content, call recordings and transcripts | Up to 3 years | Carrier and regulatory recordkeeping, and disputes about what was actually said to a driver or a carrier | Yes, for the remainder of the 3 years. A regulator, a carrier or a court can require us to show that a message was sent, to whom, and what it said. A log deleted on request is a log we cannot produce. |
| SMS consent records: the fact of consent, its time, and the exact wording agreed to | Duration of the consent plus 4 years | The record of consent is the defence to a claim that a message was unconsented | Yes, for that period. The federal limitation period for those claims is four years, so a shorter retention would delete the evidence before the claim can expire. |
| Opt-out records: the fact that a number replied STOP | Kept indefinitely | It is the only thing that keeps us from texting that number again | Yes, permanently. Deleting an opt-out record would undo the opt-out. The record holds the number and the opt-out, nothing else. |
| Driver app records for a load: positions, stop times, consent and stop records, and the driver's mobile number | As part of that load's record, for as long as the load's record is kept | They are the record of when a truck arrived, waited and left. Detention, late delivery and lost freight claims turn on exactly those times, and they are often raised months or years later. | Yes. A brokerage, a carrier or a shipper can need us to show where the truck was and when, and the record is kept so that it cannot be changed after the fact. A position deleted on request is one nobody can produce in that dispute. The driver can stop new positions being recorded at any time, and nothing is recorded on a load the driver did not say yes to. |
| Photos sent from the driver app: bills of lading, proofs of delivery, receipts, problem photos | While the brokerage subscribes | They are the load's paperwork, used for billing and claims | Follows the operational-data row above: they are the brokerage's business records. |
| Driver app data on the phone: the driver's name, the load link, the random install id, unsent positions | Until the driver erases it in the app or uninstalls | So the app can run the load | Not held by us. "Sign out and erase this phone's data" deletes it at once. |
| Security and audit logs: sign-ins, privilege changes, administrative actions | Up to 3 years | Security investigation and compliance. The record is append-only so that it is tamper-evident. | Yes, for the 3 years. A log an account holder can edit is not evidence of anything, which is the point of keeping it. |
| Billing and tax records | The period tax and corporate law requires | Legal obligation | Yes, for that period. |
| Website visit data held by our analytics and advertising vendors | Each vendor's own retention, set out in their policies | Site analytics and advertising measurement | No. Ask us and we stop it and have it deleted, and you can switch the cookies off yourself at any time with the control above. |
What this means in practice. "Delete at any time" is true of everything in the table whose last column says No, which is all of your account and operational data. Where a row says Yes, we are not refusing the request: we keep one narrow record for the stated period and delete the rest. If we ever hold something back, we will tell you which records, on which row of this table, and when they will go.
Who Processes Your Data
We do not sell, rent, or share your product data with third parties for their own purposes. We do use other companies to run the product and the website, and each of them sees a defined slice of data in order to do one job. Here is the whole list, what each one does, and what it sees. A customer under contract can ask us for the current version of this list at any time, and we give notice before a new provider starts handling customer data.
| Provider | What it does for us | What it sees |
|---|---|---|
| Supabase | Database and authentication hosting | Product data |
| Vercel | Application and website hosting, plus aggregate page-view counts | Product data in transit, website visit data |
| Anthropic | The AI models behind Scout, the agents, and email classification | The content sent for a given task, under terms that do not permit training on it |
| Microsoft and Google | The mailbox and calendar you choose to connect | As described in the OAuth section above |
| Twilio and Telnyx | SMS and voice delivery, including the text that carries a driver's load link | Phone numbers, message content, call audio |
| ElevenLabs | The synthesized voice used on agent calls | Call audio and the words spoken |
| Deepgram and AssemblyAI | Call and meeting transcription | Call and meeting audio |
| Recall.ai | Joining and recording the meetings the notetaker assistant is asked to cover | Meeting audio and participants |
| OpenFreeMap | Map images for the driver app's next-stop map | A phone's IP address and the map area on screen. No position, phone number or id. |
| Resend | Transactional and notification email sent from FreightScout's own address | Recipient address and message |
| Formspree | Receives and forwards the contact form and the scorecard form on this website | What you type into those forms. No product data. |
| GoHighLevel | Website analytics, and connecting an enquiry you send us to the pages you read first | Website visit data and what you submitted. No product data. |
| Meta, Google and LinkedIn | Advertising measurement and audiences, only where cookies are allowed | Website visit data. No product data. |
The last three rows are website vendors. They never receive your brokerage's operational or customer-record data, they are not used to send SMS, and they load only under the consent rules in the Website Visitors section above. Every provider in the table acts under its own terms for the part it performs, in addition to the processing we do to provide the service to you.
Your Rights
You may request access to, correction of, or deletion of your personal data at any time, and you may ask for a copy of it in a usable format. Brokerage administrators may deactivate users, which triggers automatic deletion of the associated authentication tokens. Where a deletion request runs into one of the exceptions in the Data Retention table, we will tell you which records we are keeping, which row of that table they sit on, and the date they will be deleted. We answer within 30 days. To exercise any of this, email privacy@freightscout.ai.
Changes to This Policy
We may update this policy as our products evolve. Material changes will be communicated to active brokerage administrators. The "last updated" date above reflects the most recent revision.
Contact
For privacy questions or data requests: privacy@freightscout.ai. For SMS/messaging help: support@freightscout.ai or (904) 467-2114. For help with the FreightScout Driver driver app: freightscout.ai/driver-app.
FreightScout, Inc. · Wilmington, DE, USA.