1. Who we are and what this policy covers
Control Tower is a web application for trucking carriers and freight brokerages, offered by Dropright Corp ("Dropright", "we"), 943 Flynn Road, Camarillo, CA 93012. This policy explains what information the Control Tower application handles, why, and what choices exist. It covers the application only; the Dropright marketing website has its own policy.
2. Whose data it is
Control Tower is sold to businesses. Each customer organization (a carrier or a brokerage) decides what it enters into the application, who in its team may see it, and which outside systems it connects. The organization is responsible for that information and for telling its own employees, drivers and business partners how it uses their information. Dropright handles the information as the organization's service provider: we store it, show it to the organization's authorized users, and carry out the organization's instructions, and we do not use it for any other purpose. If you are a driver, an employee or a contact of an organization that uses Control Tower and you have a question about your information, please ask that organization first; we will help it answer.
3. What information the application holds
- Account information of the people who sign in: name, work email address, a hashed password, two-factor authentication settings, sessions, and a record of sign-in attempts with the time, the internet address and the browser.
- Business records the organization enters or imports: customers, loads, trips and stops, rates, invoices and payments received, permits, escorts, expenses, equipment, and the notes and approvals that go with them.
- Information about the organization's drivers and staff: names and work details; contact details and an emergency contact; date of birth; driver license number, state and class; pay, deductions and settlement statements; absences; and internal notes the organization writes.
- Documents the organization uploads: rate confirmations, bills of lading, proofs of delivery, permits, receipts, and, if the organization chooses to keep them here, driver qualification documents such as licenses and medical certificates, and drug and alcohol program records. Access to these depends on each user's role; reads of the restricted classes are logged.
- An audit trail: who changed what and when, with the internet address of the request.
- Connection credentials: when an organization connects an outside system, the tokens or keys for that connection. These are stored encrypted.
We do not use advertising cookies or third-party analytics in the application. The application sets the cookies it needs to keep you signed in and to recognize a device you have used before.
4. How the information is used
We use the information only to provide the application to the organization: to show it to the organization's authorized users, to produce the documents, emails and exports the organization asks for, to carry out the connections the organization turns on, to keep the service secure, and to fix problems. We do not sell it. We do not share one organization's information with another organization. We do not use it for advertising. We do not use customer information to train artificial intelligence models.
5. The QuickBooks Online connection
Connecting QuickBooks Online is optional. A connection is made only when an administrator of the organization chooses to connect a QuickBooks company and approves the access on Intuit's own screen.
What we read. While a company is connected, Control Tower regularly reads these records from it and keeps a copy inside the organization's Control Tower account: customers, vendors, products and services (items), invoices, payments, bills and bill payments. The copy is used to show the organization which of its loads have been invoiced and paid, to compare an invoice in the books with the load it belongs to, and to prepare invoices for posting.
What we write. By default a connection is read-only and Control Tower writes nothing to QuickBooks. If an administrator switches a connection to allow posting, Control Tower can create an invoice in QuickBooks for an invoice the organization issued in Control Tower, create the customer for that invoice if the books do not have it yet, and attach the load's proof of delivery and bill of lading to it. Every such posting needs an approval by an authorized person in the organization before anything is sent. Control Tower does not edit or delete existing QuickBooks records and does not post payments.
What Intuit tells us. Intuit notifies Control Tower when a record in a connected company changes. The notification names the record only; Control Tower then reads the record itself.
How the access is protected. The access tokens Intuit issues are stored encrypted, are never shown to users, and are used only by the Control Tower servers.
Who sees QuickBooks information. Only the organization that connected the company, through users whose role allows it. We do not give QuickBooks information to any other customer or to any third party, and we do not use it for anything except the features described here. It is not sent to the AI document-reading feature.
Disconnecting. An administrator can disconnect at any time on the Integrations page. Disconnecting deletes the stored tokens and stops all reading and posting for that company. Today, to withdraw the authorization at Intuit as well, please also disconnect Control Tower inside QuickBooks (Apps, then Disconnect). The copy of QuickBooks records made while the company was connected is deleted on the organization's request. Invoices the organization created in Control Tower, and the record that an invoice was posted, are the organization's own Control Tower records and stay.
Control Tower is not an Intuit product. Intuit's handling of information inside QuickBooks is governed by Intuit's own terms and privacy statement.
6. Other services we use
We use a small number of outside services to run the application. They receive only what they need for their task.
DigitalOcean (hosting), United States.
What it does: runs the servers and stores the database, the uploaded documents and the backups.
What it receives: everything the application holds.
Status: in use.
SendGrid (email delivery).
What it does: delivers the emails the application sends: invitations, password resets, and messages and documents an organization chooses to send.
What it receives: the recipient's address and the content of each email.
Status: in use.
Intuit (QuickBooks Online).
What it does: the accounting connection described in section 5.
What it receives: what an organization posts to its own QuickBooks company.
Status: optional; only for organizations that connect it.
Anthropic (AI document reading).
What it does: reads a load document, such as a rate confirmation, that a user chooses to have read, and returns the fields found in it for a person to check.
What it receives: that one document. Only documents filed as load paperwork can be sent; the application refuses driver files and every other document class before anything is sent.
Status: optional; off unless both our platform operator and the organization's administrator switch it on. Anthropic's commercial terms state that it may not train models on customer content it receives through its services.
Dropbox Sign or Adobe Acrobat Sign (e-signature).
What it does: sends an agreement for signature when an organization has connected its own e-signature account.
What it receives: the signers' names and email addresses and the contents of the agreement.
Status: optional; only for organizations that connect it.
Federal Motor Carrier Safety Administration (public carrier lookup).
What it does: returns the public registration record of a carrier.
What it receives: the carrier's USDOT number.
Status: optional.
U.S. Energy Information Administration (public diesel price).
What it does: returns the weekly national diesel price.
What it receives: nothing about any customer.
Status: optional.
We will update this list before we start using a new service that receives customer information.
7. Where the information is stored
The application, its database, the uploaded documents and the backups are stored on servers in the United States, with our hosting provider. Optional services in section 6 may process information in other locations under their own terms.
8. How long we keep it, and deletion
We keep an organization's information for as long as the organization uses Control Tower. The organization can correct its records in the application at any time and can ask us to delete specific information; we act on a written request from an administrator of the organization within 30 days, unless the law requires the organization or us to keep the record. When an organization stops using Control Tower, it can ask for an export of its records within 30 days; we then delete its information from the live system within 90 days, and it disappears from our backups as they expire. Backups of the database are encrypted, are kept on our production server with our hosting provider, and are kept for 30 days. Some records must be kept by carriers and brokers for periods set by transportation and tax rules; the organization decides how long its records stay, and we follow its instructions.
9. How we protect it
We use measures appropriate for a business application of this kind, including: encrypted connections (HTTPS) for all access; passwords stored only as salted hashes; optional two-factor authentication for every user, required for our own operators; automatic lockout after repeated failed sign-ins; separation of each organization's information from every other organization's inside the database; role-based permissions inside each organization, with tighter access for drivers' personal details; encryption of connection tokens and keys; encrypted backups; a log of changes; and a short list of Dropright staff with access to the production systems. No system is perfectly secure, and we cannot guarantee that an incident will never happen.
10. Who at Dropright can see customer information
Access to the production servers is limited to the small number of Dropright technical staff who operate the service, and they access customer information only when needed to operate the service, to fix a problem, or to help an organization at its request.
11. If something goes wrong
If we learn of a security incident that affects an organization's information, we will tell that organization's administrators without undue delay, with what we know about what happened, what information was involved and what we are doing about it, so the organization can meet its own duties.
12. Requests from individuals
Because the organization decides how its information is used, requests from individuals to see, correct or delete information about them should go to the organization. If a request reaches us directly, we pass it to the organization and help it respond.
13. Children
Control Tower is a business application and is not meant for anyone under 18.
14. Changes to this policy
We will post any change on this page with a new effective date, and we will tell organization administrators by email before a change that materially affects how we handle their information takes effect.
15. Contact
Privacy questions, deletion requests, support and security reports: support@dropright.com. Mail: Dropright Corp, 943 Flynn Road, Camarillo, CA 93012.
The terms that govern use of Control Tower are in the Control Tower End-User License Agreement and Terms of Use.