Privacy policy
1. Operator and scope
This policy describes the QuickBooks Online connection in Flux, a private AI workspace used for the operator’s own internal business work. Operator: Bruno Vargas. Privacy contact: bruno@transparence.co.
This policy does not describe Intuit’s own processing or the separate policies of model, network, hosting, or other service providers chosen by the operator.
2. Information the connector accesses
With the company administrator’s authorization, the connector can read the selected QuickBooks company’s identity and preferences, saved invoices and line items, customers, recorded payments, and supported accounting reports. Results may include names, contact details, transaction dates, descriptions, taxes, currencies, amounts, and outstanding balances.
Flux requests Intuit’s standard Accounting permission. That provider permission also allows changes, but the current connector exposes only approved retrieval operations and does not create, edit, send, delete, post, or reconcile accounting records. It does not provide a live bank connection.
3. Purpose and control
Information is retrieved to answer the operator’s requests about their books. Access is limited to the company selected for the conversation. New conversations start with QuickBooks access off. The connector records the company, environment, currency context, and retrieval time to help the operator assess the result.
4. Credentials and local storage
Intuit app credentials and authorization tokens are stored in the host Mac’s login Keychain, separately from Gmail credentials. They are not included in model tools, conversation exports, synced preferences, or the source repository.
Company connection metadata, callback configuration, and hashed browser-management keys are stored in a private local SQLite database. A browser’s management key is stored in that browser’s local storage. The connector keeps a timestamp of the last successful read.
5. Accounting results in conversations
Retrieved accounting records are supplied to the selected chat model as tool results. Those results and the resulting messages may be retained in Flux’s conversation database on the Mac and in browser caches, synchronized to the operator’s connected devices, included in exports, and retained in backups. The connector does not maintain a separate full mirror of the QuickBooks ledger.
Model processing follows the operator’s configuration. With a local model, inference runs on the operator’s machine. If the operator enables a remote model or endpoint, accounting excerpts included in the conversation may be sent to that provider. The operator must review that provider and configuration before using it with accounting information.
6. Service providers and network access
Flux communicates with Intuit to authorize access, refresh tokens, and retrieve accounting data. The operator may use a temporary HTTPS tunnel for Intuit’s sign-in callback. That tunnel forwards only the dedicated callback endpoint; its provider handles the callback connection and one-use authorization code, not the company’s accounting API responses or the Intuit client secret.
Ordinary API reads and token refreshes run from the Mac directly to Intuit and do not require the callback tunnel. Private remote access to Flux may use the operator’s configured network service. Additional processing by those providers is governed by their own policies.
The custom QuickBooks connector does not sell accounting information or use it for advertising. It does not add advertising trackers or third-party analytics to these pages.
7. Retention, disconnection, and deletion
Company authorization tokens are retained until the company is disconnected or the operator removes them. Disconnecting a company in Flux deletes its local tokens and connection record and prevents further reads through that connection. Intuit app-level credentials and callback configuration remain available for future connections.
Disconnecting does not automatically revoke Intuit’s provider-side grant. The company administrator can also remove Flux in QuickBooks’ connected apps. Disconnecting does not delete accounting excerpts already saved in conversations, browser caches, exports, or backups. The operator must manage those copies separately.
8. Security and questions
The connector uses HTTPS for Intuit API calls, Keychain for secrets, company access checks, a retrieval-only endpoint allowlist, and request logging that excludes OAuth query parameters. These controls do not replace the operator’s responsibility to secure their Mac, browser, connected devices, model configuration, exports, and backups.
Questions or requests about information held in the operator’s Flux installation can be directed to the confirmed contact above. The operator will assess applicable access, correction, deletion, and other privacy requests.
9. Changes
The operator will update this policy when the connector’s processing changes, including before enabling accounting writes or making Flux available to additional users. The effective date appears at the top of this policy.