Load Watcher
← Back to site

Legal

Privacy Policy

Last updated September 24, 2026

This policy explains what Load Watcher collects, why, who else receives it, and what you can do about it. It covers the Load Watcher Chrome extension, this website (loadwatcher.io and its former address loadwatcher.app), and the company cabinet at api.loadwatcher.app.

What stays in your browser

Most of what the extension works with never reaches us. The loads you see on load boards, your matches, your call queue and the history of loads you contacted are kept in Chrome's storage on your computer.

What we collect and why

  • Account. Your email address and an identifier of your extension install. The key that proves an install is yours is stored only as a hash. We use these to sign you in and to tie your subscription to your install.
  • Install registration. When an install is registered or moved, our server logs record its IP address, the country derived from it, your browser platform and the extension version. We use this to prevent account takeover and abuse and to help support.
  • A copy of your settings and lanes. Your search criteria, email templates, and ignored and preferred brokers — so they can be restored after a reinstall and so support can troubleshoot. Loads, your call queue and your contact history are not part of this copy.
  • Usage counters. Daily counts of calls and emails placed through the service. Never the content of calls or messages.
  • Connected accounts. Access tokens for Gmail, GoTo Connect and RingCentral, encrypted at rest. We use them only to place the calls and send the emails you set up. With 3CX, calls are started from your own 3CX web client in your browser, and we receive no 3CX credentials.
  • Calls. When a call goes through our server, we pass the broker's number to your phone provider. Our logs keep only its last four digits.
  • Payments. Stripe processes payments; we never see or store your card number. We store your plan, subscription status and paid-through date, and, for company plans, the Stripe customer and subscription identifiers.
  • Company accounts. The owner's email, the emails of invited dispatchers, and which seat each one holds.
  • Support requests. Your email address and what you write to us.
  • Maps. To draw maps and routes, place names and coordinates are sent through our server to Mapbox. The extension reads trip distance from Google Maps inside your browser.
  • Server logs. Time, the address requested, the install identifier and the IP address, for security and debugging.

Gmail and other Google data

We ask Google only for permission to send email on your behalf and to know your email address. We do not read, scan or store your mailbox; the emails the extension sends appear in your own Sent folder.

Load Watcher's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, do not sell it, and do not let people read it except with your permission, for security, or when the law requires it.

Who else receives your data

We do not sell personal information, and we do not share it for advertising. We pass it only to the providers that run the service, each for its own part:

  • Stripe — payments
  • Railway — hosting and database
  • Cloudflare — website delivery, DNS and email routing
  • Resend — the emails we send you (sign-in codes, invitations)
  • Google — Gmail sending, and the fonts this website loads, which gives Google your IP address
  • GoTo and RingCentral — the calls you place through them
  • Mapbox — maps and routes

We may also disclose data when the law requires it.

Cookies and tracking

We use no analytics and no advertising trackers. This website remembers your language choice in your browser's local storage, and the company cabinet keeps its sign-in session there. We do not track you across other websites, so there is nothing for a browser's Do Not Track signal to switch off, and we do not respond to it differently.

How long we keep it

We keep your data while your account exists. Deleting your account removes your email address, your connected-account tokens and your subscription record from the live service right away. Some records stay behind, and here is exactly which:

  • Your install's registration is kept, so that a paid subscription cannot be claimed by someone else on the same install.
  • A company seat. If a company invited you, the seat it created, with the email address it invited, belongs to that company and stays until the company removes it. A removed seat stays in the company's usage history.
  • Everything else on request. If you ask us to delete your settings copy, usage counters and support requests too, we delete them together with your account. For 30 days these records, together with your account details, are held in an internal archive, only so that a mistaken deletion can be undone, and are then permanently erased at the archive's next clean-up.
  • Backups. Database backups that contain your data expire on their own schedule, within three months.
  • Payments. Stripe keeps its records of your payments under its own retention rules.

Your choices

  • Disconnect Gmail, GoTo Connect or RingCentral at any time in the extension's settings; you can also revoke Load Watcher's access in your Google account.
  • Ask us for a copy of your data, to correct it, or to delete it by writing to support.

Security

Data travels over HTTPS; access tokens are encrypted at rest; sign-in codes, sessions and install keys are stored only as hashes. No system is perfectly secure. If a breach affects your personal information, we will notify you as the law requires.

Children

Load Watcher is a business tool for freight dispatchers. It is not directed to children, and we do not knowingly collect information from anyone under 13.

Changes to this policy

When this policy changes, we update the date at the top. If a change is material, we will also tell you by email or in the extension before it takes effect.

Questions or requests? support@loadwatcher.io