1. Who We Are
BrokerWise TMS is a cloud-based transportation management system for freight brokers, operated by Bison Wise AI LLC, an Arizona limited liability company (“BrokerWise,” “we,” “our,” or “us”). The QuickBooks integration allows BrokerWise to send accounts-receivable records you create in BrokerWise into your own QuickBooks Online company.
BrokerWise is an independent application. It is not affiliated with, endorsed by, or operated by Intuit Inc. Your use of QuickBooks Online remains governed by your own agreement with Intuit.
2. Connecting Your QuickBooks Company
You connect QuickBooks to BrokerWise through Intuit’s OAuth 2.0 authorization flow. You sign in to Intuit directly, and Intuit asks you to authorize BrokerWise to access the QuickBooks company you select. BrokerWise never sees or stores your Intuit username or password.
When the connection is established, BrokerWise reads your QuickBooks company’s display name to verify that the correct company was authorized. It is not stored.
Each BrokerWise customer account may hold one QuickBooks connection. You may disconnect at any time, as described in Section 6.
3. QuickBooks Data We Access
Intuit Platform Disclosure
BrokerWise accesses QuickBooks Online data solely to provide the invoicing integration you have authorized. Data is used only for the purposes described in this policy. We do not sell QuickBooks data, do not share it with third parties for their own purposes, and do not use it for advertising, profiling, or model training. QuickBooks data is never aggregated or combined across BrokerWise customers.
The Direction of Data Flow
The BrokerWise integration is primarily a push integration. BrokerWise creates records in your QuickBooks company based on the load and invoice data you enter in BrokerWise. BrokerWise does not import your QuickBooks records into BrokerWise for reporting, reconciliation, analytics, or any other purpose.
The only data BrokerWise reads from QuickBooks is what is necessary to do that job correctly: your company name for confirmation, whether a matching customer or invoice already exists so we do not create duplicates, and company preferences that affect how records must be created.
Records BrokerWise Works With
Depending on which integration features are enabled for your account, BrokerWise may access the following QuickBooks entities:
| QuickBooks Record | What BrokerWise Does | Why |
|---|---|---|
| Company Information | Reads company name | So you can confirm the correct company was connected. Not stored. |
| Customers | Reads to find a match; creates when none exists | To file your invoice against the correct customer. A person in your organization always confirms the match — BrokerWise never matches customers automatically. |
| Invoices | Reads to check for an existing invoice number; creates and updates | To create your invoice in QuickBooks and update it if you issue a revision. |
| Attachments | Reads to avoid duplicates; creates | To attach the proof-of-delivery document to the invoice. |
| Payments | Creates | To record a customer payment against an invoice you pushed (when this feature is enabled). |
| Company Preferences | Reads | To respect settings such as whether QuickBooks assigns its own invoice numbers. |
Records BrokerWise Will Never Access
BrokerWise does not read or write Bills, Vendors, or any accounts-payable records. The integration is limited to accounts receivable. This is a permanent design commitment, not a current limitation.
4. What We Store
BrokerWise stores references to your QuickBooks records, not copies of them. Specifically, BrokerWise may store:
- Your QuickBooks company identifier (Intuit’s “realm ID”), which is an opaque number used to route requests to the correct company.
- Encrypted OAuth access and refresh tokens, their expiration, the permission scope you granted, and the connection status.
- The QuickBooks customer identifier associated with each of your shipper records.
- The QuickBooks invoice identifier associated with each invoice BrokerWise sends, along with sync status and timestamps.
BrokerWise does not store copies of your QuickBooks customer records, invoice contents, balances, contact details, or company name. The invoice data BrokerWise sends to QuickBooks originates in BrokerWise; we do not read QuickBooks invoice content back into our system.
5. How We Protect Your QuickBooks Credentials and Data
Token Security
OAuth tokens are encrypted using AES-256-GCM at the application layer before they are written to our database. The database stores only ciphertext and never holds a plaintext token. The encryption key is held outside the database and outside our source code. Tokens are decrypted in memory only at the moment an API call is made, are never stored in decrypted form, and are never written to logs.
Customer Isolation
QuickBooks credentials and QuickBooks-derived identifiers are isolated per customer at the database level. Every table holding QuickBooks data is protected by row-level security enforced by the database engine itself, keyed to your authenticated identity. One customer’s QuickBooks data cannot be accessed by, combined with, or affected by another customer’s. This isolation is structural, enforced by the database, not dependent on application code.
Transport
All communication with Intuit’s APIs occurs over encrypted HTTPS connections.
6. Disconnecting QuickBooks
You may disconnect your QuickBooks company from BrokerWise at any time by revoking BrokerWise’s access in your Intuit account settings.
When you disconnect:
- Your OAuth tokens are destroyed and the connection is marked inactive. BrokerWise retains no credential capable of accessing your QuickBooks company after disconnection.
- Reference identifiers are retained. BrokerWise keeps the record of which QuickBooks invoice and customer identifiers correspond to which BrokerWise records. These are BrokerWise’s own records about documents BrokerWise sent, and they are retained to preserve your audit trail and to prevent duplicate invoices if you later reconnect. They contain no QuickBooks record content — only opaque identifiers.
Disconnecting from BrokerWise does not delete any records already created in your QuickBooks company. Those records belong to you and remain in QuickBooks.
7. Sharing and Third Parties
We do not sell your QuickBooks data. We do not share it with third parties for their own marketing, advertising, or independent purposes. QuickBooks data is processed only by BrokerWise and by the infrastructure providers that host and operate the BrokerWise platform, who are contractually bound to use it solely to provide services to us. A current list of our infrastructure providers is available on request.
We may disclose data if required by law, court order, or governmental authority, or to protect the rights, property, or safety of BrokerWise, our users, or others.
8. Retention
Encrypted OAuth tokens are retained only while your QuickBooks connection is active and are destroyed on disconnection. Reference identifiers are retained for the life of your BrokerWise account and are deleted with your account data in accordance with our general Privacy Policy. BrokerWise does not retain QuickBooks record content because it does not store it.
9. Your Rights
You may disconnect QuickBooks at any time (Section 6), request a description of the QuickBooks-related identifiers we hold for your account, or request deletion of your account data. Requests are handled as described in our general Privacy Policy. If you are a California resident, the rights described there under the CCPA/CPRA apply to your QuickBooks-related data as well.
10. Intuit’s Terms
BrokerWise’s use of Intuit’s APIs is subject to the Intuit Developer Terms and Intuit’s platform requirements. Your use of QuickBooks Online is subject to your own agreement with Intuit and Intuit’s privacy policy, which govern Intuit’s handling of data within QuickBooks. This policy governs only BrokerWise’s handling of data that passes through the integration.
11. Governing Law and Changes
This policy is governed by the laws of the State of Arizona, without regard to its conflict of law principles. We may update this policy as the integration evolves. Material changes will be reflected in the effective date above and, where appropriate, communicated to connected users.
12. Contact Us
For questions about this policy or about how BrokerWise handles your QuickBooks data, contact us at:
Bison Wise AI LLC
Operating as: BrokerWise TMS
Email: [email protected]
Website: brokerwisetms.com
Governing Law: State of Arizona, United States