Privacy Policy
This Privacy Policy explains what data the Simple Dispatcher service (also written "SimpleDispatcher"; the "Service", "we", "us") collects, why, how it is stored and protected, who receives it, how long it is kept and how you can have it deleted. The Service is available at https://simpledispatcher.com.
If you do not agree with this Policy, please do not use the Service.
1. Who we are and how to contact us
The data controller is the operator of the Simple Dispatcher service.
2. What the Service does
Simple Dispatcher is a work tool for truck dispatchers. You describe your trucks (location, size, rates, filters). The Service receives freight loads from the load boards you use, finds the loads that fit your trucks, shows them to you in real time and sends your bid to the broker by e-mail from your own mailbox. Loads from Sylectus and LoadOne arrive as e-mails in your Gmail mailbox, which is why the Service asks for access to Gmail. Loads from other boards (DAT, C.H. Robinson, Millhouse, Landstar, NTG, UTS) are sent to the Service by the Simple Dispatcher browser extension that you install yourself.
3. Data we collect
3.1. Data you give us
- Account: name, e-mail address, password (stored only as a hash), role (dispatcher or manager) and interface language.
- Work data: trucks (name, city and state, dimensions, weight, equipment, search radius, dates, rates, filters, stop words), board settings, sender name and address, your bid e-mail templates and the images you upload for them, favourite brokers, work hours set by a manager.
- Team links: which dispatchers belong to which manager, and the invitations a manager sends (the invited e-mail address). Loads that a manager collects with the browser extension are passed to the manager's dispatchers who have chosen to receive them.
- Messages to us: the name, e-mail address and text you send through the contact form.
3.2. Data we receive from other services
- Google (Gmail): see section 4.
- Stripe (payments): the payment identifier, product, plan, amount, date and the e-mail address used for the payment. We never receive or store your card number; card data is entered on Stripe's pages.
- Telegram: if you link the Simple Dispatcher bot, the identifier of your Telegram chat, the linking code and the commands you send to the bot, and whether notifications are on. The bot sends you service notifications (for example, that matching loads are waiting for you); these notifications do not contain the content of your e-mails.
- Browser extension: the loads it reads on the load-board pages you have open (order number, pickup and delivery places and dates, weight, equipment, broker contact, rate) and an access token that identifies your account.
3.3. Data collected automatically
- IP address, browser type (user agent), date and time of requests, the pages and actions requested, session identifiers.
- Technical logs of errors and of background jobs. Passwords, tokens, keys and cookies are masked before anything is written to a log.
- Activity data the product needs: when a match was viewed, when a bid was sent, daily counters per truck.
We do not use advertising trackers or third-party analytics.
4. Google user data (Gmail)
This section describes exactly how the Service accesses, uses, stores and shares data received through Google APIs. It applies to every Google account you connect in the Service. You can connect one mailbox for load e-mails and bids (Sylectus, LoadOne) and, if you wish, a second mailbox that is used only to send your bids for DAT loads.
4.1. What permission we ask for and why
Connecting Gmail is your choice: you press "Connect Gmail" in the settings and approve the request on Google's own consent screen. The Service asks only for these Google OAuth scopes:
| Scope |
When it is requested |
Why the Service needs it |
https://www.googleapis.com/auth/gmail.modify |
Every time you connect or reconnect a mailbox |
To list your Gmail labels so that you can choose the label that holds your load e-mails; to read the new e-mails under that label and extract the load from them; to send your bid to the broker from your mailbox (as a reply in the same thread or as a new e-mail); and to add the "sent" label you chose to the e-mail you have bid on. This one scope covers reading, sending and labelling, so no further scopes are requested. |
https://mail.google.com/ |
Only if you decide to use the optional paid "Cleanup" tool and press its connect button |
To permanently delete old load e-mails under a label you choose, at your explicit request. Gmail permits permanent deletion only with this scope. It is never requested during a normal connection. |
The Service also reads the e-mail address of the connected Google account (Gmail profile) to show you which mailbox is connected.
4.2. What Gmail data the Service accesses
- Labels: the names and identifiers of your own labels.
- Load e-mails under your label: for each Gmail load board you switched on, the most recent e-mails (received within the last 24 hours) under the label you selected for that board. The Service reads the headers (sender, reply-to, subject, date, message identifiers) and the body of those e-mails to extract the load: order number, pickup and delivery places and dates, weight, pieces, dimensions, vehicle type, the broker's name, e-mail address and phone, and the broker's notes.
- One e-mail you point to: on the "Diagnose" page you can enter the identifier of a single e-mail to find out why it did not match a truck. The Service then looks up that one e-mail in your mailbox by its identifier and reads it. This happens only when you ask for it.
- Sending: the Service creates and sends e-mails from your mailbox: your bid to the broker, and a test e-mail to your own address when you press "Send Test Mail".
- Labelling: the Service adds the "sent" label you chose to an e-mail you have bid on.
- Cleanup tool (optional): the identifiers of the e-mails under the label you chose that are older than 90 days, in order to delete them.
The Service does not go through the rest of your mailbox, does not read your contacts, calendar, Drive or any other Google product, and does not change or delete e-mails except as described above.
4.3. How the Service uses Gmail data
Only to provide the features you see in the Service:
- to show you the loads that fit your trucks, with the distance and the price calculated for you;
- to send your bids. A bid is sent when you press "Send". If you turned on automatic sending for a truck, the Service sends the bid for a matching Sylectus load automatically, using the template and the prices you set; you can turn this off at any time;
- to mark the e-mails you have bid on with your label;
- to keep the history of your bids and your statistics;
- to prevent two dispatchers of the same manager's team from bidding on the same load twice;
- to explain, at your request, why an e-mail did not match a truck;
- if you use the cleanup tool, to delete the e-mails you asked the Service to delete.
We do not use Gmail data for advertising, including retargeted, personalised or interest-based advertising. We do not sell Gmail data. We do not use Gmail data to develop, improve or train generalised or non-personalised artificial intelligence or machine learning models. We do not transfer Gmail data to data brokers or information resellers.
4.4. Who can see Gmail data
The processing is automatic. Our staff do not read your e-mails or the data extracted from them, unless:
- you gave us your explicit consent to look at specific messages (for example, when you ask support to investigate a problem);
- it is necessary for security purposes (for example, investigating abuse or a fault that affects the protection of the data);
- it is necessary to comply with applicable law;
- the data has been aggregated and anonymised and is used for internal operations in line with applicable privacy law.
Inside the Service the loads and bids are shown to you. If your account is linked to a manager's account, the Service uses the fact that a load has already been bid on to stop a teammate from bidding on it again, and the manager sees your statistics: the daily number of matches and bids per truck and load board, without the content of the loads. The administrators of the Service see, in the list of users, the address of your connected mailbox and the number of your bids per load board.
4.5. Limited Use
SimpleDispatcher'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.
4.6. Storage and protection
- Access tokens. The access token, the refresh token, their expiry time and the granted scopes are stored in our database encrypted (AES-256). They are never shown in the interface, never sent to your browser and masked in logs.
- Mailbox address. The e-mail address of the connected mailbox is stored as your sender address. It is shown to you in the settings and is visible to the administrators of the Service in the list of users.
- E-mail content. The Service does not keep an archive of your e-mails. A load e-mail that was just read is held in a short-lived technical cache on our servers (it expires after about two minutes) so that the same e-mail is not downloaded twice.
- Load data. When a load fits at least one of your trucks, the Service stores the extracted load fields listed in 4.2, including the subject of the e-mail and the broker's notes from its text, together with Gmail's message and thread identifiers. An e-mail that fits no truck leaves no load record.
- Bids. The subject and the text of a bid prepared or sent for you are stored with the match.
- Transport. All connections between your browser, the Service and Google use HTTPS (TLS).
- Access control. The data is stored on the servers of our hosting provider; access is limited to the people who operate the Service. The loads and the text of the bids are shown only to the user they belong to.
4.7. Sharing of Gmail data
We do not share Gmail data with third parties, with these necessary exceptions:
- Brokers you bid to. Your bid is an e-mail from your own mailbox to the broker's address taken from the load e-mail; it is sent through Gmail.
- Distance calculation. The city and state of the pickup and delivery places are sent to the Google Maps Platform (Distance Matrix API) to calculate distances. No personal names, e-mail addresses or message text are sent.
- Hosting. The data is stored on the servers of our hosting provider (Amazon Web Services), which processes it only on our behalf.
- Legal obligations. If a law or a lawful request of a public authority requires it.
4.8. Retention of Gmail data
- Loads that fit a truck but were not bid on are deleted automatically, together with their matches, 24 hours after they arrive.
- Loads you have bid on, and loads whose bid is still being sent or whose sending result is unclear, are kept with the text of the bid as your bid history for as long as your account exists.
- Daily statistics are kept for 14 days.
- Technical records of a bid that failed to send may contain the text of that bid; they are kept for troubleshooting until they are purged.
- Access tokens are kept until you disconnect the mailbox or your account is deleted. They are also kept if your subscription has ended; the Service does not read your mailbox while you have no valid subscription.
4.9. How to revoke access and delete your Google data
You can stop the access at any time, in any of these ways:
- In the Service: Settings → "Disconnect Gmail". The Service revokes its token at Google and deletes the stored tokens immediately.
- In your Google Account: open https://myaccount.google.com/permissions (Google Account → Security → Your connections to third-party apps and services), choose Simple Dispatcher and remove its access. Reading, sending and labelling through the Gmail API stop at once.
- By request: write to info@simpledispatcher.com from the e-mail address of your account and ask us to delete your Gmail data or your whole account (see section 9). We delete the stored tokens, loads, matches and bid history within 30 days and confirm it by e-mail.
Please disconnect Gmail in the settings before you ask for your account to be deleted: this also revokes the Service's access at Google. If a mailbox is still connected when an account is deleted, its tokens are erased from our database and can no longer be used by us, and we recommend that you also remove the access in your Google Account as described above.
5. Why we process data (purposes and legal bases)
- To provide the Service (performance of our contract with you): accounts, trucks, matching, bids, history, statistics, notifications, the extension, support.
- With your consent: connecting Gmail, linking Telegram. You can withdraw consent at any time by disconnecting.
- Payments and accounting (contract and legal obligation): subscription status, payment records.
- Security and reliability (our legitimate interest): logs, rate limits, protection against abuse and fraud, error analysis.
- Legal compliance: answering lawful requests and keeping the records the law requires.
We do not make decisions about you that have legal effects solely by automated means.
6. Cookies and browser storage
The Service uses only cookies that are necessary for it to work:
- a session cookie that keeps you signed in, and a "remember me" cookie if you choose it;
- a security cookie that protects forms against forged requests (CSRF);
- a cookie that remembers the language you chose.
Your browser's local storage keeps the light or dark theme you chose and a few interface preferences. The contact form is protected by Google reCAPTCHA, which is loaded when you use the form and is subject to Google's Privacy Policy and Terms of Service. We use no advertising cookies.
7. Who receives data
We do not sell personal data. Data is passed only to the providers that are necessary to run the Service, and only as much as each of them needs:
| Provider |
What for |
What it receives |
| Amazon Web Services |
Hosting of the application, the database and backups |
All data of the Service, processed on our behalf |
| Google (Gmail API) |
Reading load e-mails and sending bids at your request |
The requests described in section 4 |
| Google Maps Platform |
Distances and route maps |
City and state of trucks, pickups and deliveries |
| OpenStreetMap Nominatim |
Coordinates of a truck's city |
City and state |
| Stripe |
Payments |
Your account identifier, the plan and what you enter on Stripe's page |
| Telegram |
Bot notifications if you link the bot; technical error alerts for the operator of the Service |
Your chat identifier and the text of the notifications; the alerts carry a short technical error description with credentials masked |
| Google reCAPTCHA |
Protection of the contact form |
Technical data of the browser that sends the form |
| E-mail delivery provider |
Service e-mails (verification, password reset, invitations) |
Your e-mail address and the text of the message |
We may also disclose data when the law requires it, or to protect our rights, our users or the public in a dispute or a security incident.
8. How long we keep data
- Account, trucks, settings, templates: while your account exists.
- Loads without a bid: 24 hours. Loads with a bid (history): while your account exists.
- Statistics: 14 days.
- Extension access tokens: until they expire or you change your password; expired tokens are removed daily.
- Telegram linking codes: a code is valid for 15 minutes; a used code is kept only as a hash while your account exists.
- Payment records: while your account exists, and longer where accounting and tax law requires it.
- Sessions, technical caches and logs: for the limited time needed for operation, security and troubleshooting.
- Backups: deleted data disappears from backups as the backups are rotated.
9. Deleting your account and your data
There is no self-service delete button yet. To delete your account write to info@simpledispatcher.com from the e-mail address of the account, or use the contact form. If you have a paid period that is still running, we end it as part of the deletion; payments already made are not refunded unless the law requires it. Deleting an account removes your profile, trucks, settings, templates, connected mailboxes and their tokens, loads, matches, bid history, statistics, payment records and Telegram link. Extension tokens stop working at once and their records are removed when they expire. We complete the deletion within 30 days. Records that we are legally obliged to keep may be kept for the period the law requires.
10. Security
We protect data with encrypted connections (TLS), encryption of Google tokens at rest, hashed passwords, role-based access, rate limits and masked logs. No method of transmission or storage is perfectly secure; if we learn of a breach that affects your data we will notify you and the competent authorities as the law requires.
11. Your rights
Depending on the law that applies to you, you have the right to know what data we hold about you, to receive a copy, to correct it, to have it deleted, to restrict or object to its processing, to data portability and to withdraw consent. You can change your name, e-mail address, password and language yourself on the Account page. For anything else write to info@simpledispatcher.com; we answer within 30 days. You also have the right to complain to the data protection authority of your country.
12. International transfers
The Service runs on the servers of the providers listed in section 7, which may be located outside your country. If you use the Service from another country, your data is transferred to and processed in the countries where those providers operate.
13. Children
The Service is a business tool and is not intended for anyone under 18. We do not knowingly collect data of children.
14. Changes to this Policy
We may update this Policy. The current version and the date of the last update are always on this page. If a change affects how we use Google user data, we will tell you in the Service and ask for your consent before using the data in the new way.
This Policy is published in several languages. If the versions differ, the English version prevails.
15. Contact
Questions about this Policy or about your data: info@simpledispatcher.com.
See also the Terms of Service.