Privacy Policy

Effective date: 2026-05-18. Application: QBuddy (Windows desktop application). Operator: bright i-deas, tech, LLC.

This Privacy Policy explains what information the QBuddy desktop application ("QBuddy") accesses, where that information is stored, and with whom it is shared. QBuddy is used by professional bookkeepers and accounting firms to post bank-statement transactions to QuickBooks Desktop and QuickBooks Online companies they are authorized to access on behalf of their clients.

1. The short version

QBuddy runs entirely on the bookkeeper's local Windows workstation. It does not send Customer Data to bright i-deas servers.
QBuddy connects directly to Intuit's QuickBooks Online APIs to read and post accounting data, and to Intuit's QBFC SDK locally to do the same against a QuickBooks Desktop company file.
The only data leaving the workstation is (a) requests and responses between QBuddy and Intuit when you connect or post, and (b) files sent to the file-transfer endpoints you configure for your firm's own bookkeeping workflow.
QBuddy does not sell, share, or repurpose Customer Data.

2. Information QBuddy accesses

Category	What it includes	Where it lives
Bank statement files	PDF statements you drop into QBuddy for parsing.	Local workstation only.
Parsed transactions	Date, description, and amount of each line extracted from statements; user-applied categorization (account, vendor or customer, memo).	Local workstation only, in a local Absolute Database (ABS) file on disk.
Client records	Names, QuickBooks company file paths, default accounts, and per-client QBuddy preferences set by the bookkeeper.	Local workstation only.
QuickBooks Online connection tokens	Intuit OAuth refresh and access tokens and the QuickBooks Online realm (company) identifier, per connected QBO company.	Local workstation only, inside the same encrypted ABS file described above. Tokens are scoped to QuickBooks Online accounting and are revocable at any time from either QBuddy or QuickBooks Online.
Chart of Accounts, Vendor, and Customer names	The list of accounts, vendors, and customers from the QuickBooks company being processed.	Pulled from Intuit at the start of each Rules session and held in memory; not persisted between sessions.

3. How that information is used

To classify transactions: QBuddy compares transaction descriptions against rules you define and matches them against the Chart of Accounts and Vendor/Customer lists pulled from QuickBooks.
To post transactions: when you click Post, QBuddy sends the categorized transactions to Intuit's QuickBooks Online API (for QBO companies) or to the local QBFC SDK (for QBD companies). Each posted transaction is recorded by Intuit / QBD under the QuickBooks company you connected.
To recover from crashes: QBuddy writes a small per-batch state file to your local AppData folder so that an interrupted post can resume without re-sending duplicate transactions. State files are deleted after a successful batch.

4. Sharing with third parties

QBuddy shares information only with the following third parties, and only to the extent strictly necessary to perform the operation you initiated:

Intuit Inc. — for QuickBooks Online connections and posts. The data sent is the OAuth credentials at connect time and the transaction payloads at post time. Intuit's handling of this data is governed by Intuit's own Privacy Statement (intuit.com/privacy/statement).
Your firm's own file-transfer endpoint(s) — for uploading processed batches to your internal bookkeeping workflow, if you have configured them. The endpoint and credentials are yours; QBuddy uses them as configured and does not redirect data elsewhere.

QBuddy does not transmit Customer Data to bright i-deas, tech, LLC. bright i-deas does not host a customer-facing back end for QBuddy and has no access to your clients' QuickBooks data.

5. OAuth scope & data minimization

QBuddy requests the QuickBooks Online scope com.intuit.quickbooks.accounting at connect time. This scope grants read/write access to a single connected company's accounting data (chart of accounts, vendors, customers, journal entries, deposits, purchases). QBuddy does not request payroll or payments scopes and does not access them.

6. Data retention & deletion

Connection tokens and client preferences are retained locally for as long as the bookkeeper keeps a connection active. Disconnecting a client from QBuddy (or revoking the app from QuickBooks Online directly) clears the saved tokens for that client. Bank-statement files and parsed transactions are retained on the workstation per the bookkeeper's own retention practices; QBuddy does not impose a separate retention period.

7. Security

QBuddy stores its local data in an Absolute Database file with file-level encryption applied. All HTTPS connections to Intuit use TLS. The bookkeeper is responsible for the security of the workstation on which QBuddy is installed (operating-system updates, user-account isolation, backups, etc.).

8. Your rights

Because QBuddy stores all Customer Data on your local workstation, you have direct control over that data: you may inspect, export, or delete it from your workstation at any time. To revoke QBuddy's access to a QuickBooks Online company, click Disconnect QBO in QBuddy or remove the app from inside QuickBooks Online (Apps → My Apps → QBuddy → Disconnect).

9. Children

QBuddy is intended for professional bookkeepers and accounting firms. It is not directed to, marketed to, or intended for use by children under 13.

10. Changes to this Policy

bright i-deas may update this Privacy Policy from time to time. The version in force is the one published at this URL on the date you install or update QBuddy. Material changes will be reflected by an updated "Effective date" above.

11. Contact

Questions or concerns about this Privacy Policy can be sent to support@brighti-deas.com.

bright i-deas, tech, LLC
United States