Multi-Entity Ledger Bridge · Last updated: August 22, 2026

1. Who this policy covers

Multi-Entity Ledger Bridge (“the Application”) is private software operated by Austin Velocity Volleyball Club, LLC (“the Operator”) for the Operator’s own internal accounting use. It is not distributed publicly, not offered as a service, and has no end users other than the Operator and people the Operator authorizes within their own organization.

2. What the Application accesses

When the Operator explicitly authorizes it against a QuickBooks Online company, the Application can read that company’s accounting data through Intuit’s official API, using the accounting scope. This includes financial reports (profit and loss, balance sheet, cash flow, trial balance), accounts receivable and payable aging, and records such as accounts, customers, vendors, and transactions.

Authorization is granted per company. The Application can access only those companies the Operator has individually and explicitly connected, and only for as long as that authorization remains valid.

3. What the Application does with that data

Data retrieved from QuickBooks is used solely to produce reports and analysis for the Operator, on the Operator’s own computer, at the Operator’s request.

The Application does not:

• transmit accounting data to the developer of the Application;
• transmit accounting data to any third party;
• sell, rent, license, or share data with anyone;
• use the data for advertising, profiling, or training any model;
• operate any server, hosted service, or shared database;
• create, modify, or delete anything in QuickBooks — access is read-only.

4. Where data is stored

The Application stores OAuth tokens locally on the Operator’s computer, in a directory readable only by the Operator’s own account. Accounting data is not persisted by default; reports are retrieved from Intuit’s API when requested. If the Operator chooses to save a report, that file resides on their own computer and is under their control.

No data is stored on any server operated by the developer, because no such server exists.

5. Network connections

The Application communicates only with Intuit’s official endpoints over HTTPS. It makes no other outbound network connections and contains no analytics, telemetry, or tracking of any kind.

6. Data retention and deletion

Stored tokens persist until the Operator deletes them or revokes the Application’s access. The Operator may revoke access at any time by disconnecting the Application from within QuickBooks Online, or by deleting the local token file. Revoking access immediately and permanently ends the Application’s ability to read that company’s data.

7. Third parties

The Application uses no third-party processors, sub-processors, analytics providers, or hosting providers. The only external party involved is Intuit, whose handling of QuickBooks data is governed by Intuit’s own privacy policy.

8. Security

Credentials and tokens are written with owner-only file permissions. All communication with Intuit uses HTTPS. Because the Application stores credentials on the Operator’s computer, the security of those credentials depends on the security of that computer, which is the Operator’s responsibility.

9. Children’s privacy

The Application is business accounting software. It is not directed at children and is not used by them.

10. Changes to this policy

If the Application’s behavior changes in a way that affects this policy, this page will be updated and the date above revised.

11. Contact

Questions about this policy may be directed to dave@austinvelocity.com.