Privacy policy

Last updated 2026/10/07

This policy covers the connector at this address, operated by Andy. Andy is responsible for the handling described here. It is a private deployment: data is not sold, rented, shared for advertising, or used to train any model.

What is stored

• Intuit tokens. The access and refresh tokens for each authorized QuickBooks company, encrypted at rest.
• Company records. The Intuit realm id, company name, and which connector user authorized it.
• Identity. An identifier derived by hashing the Intuit account that authorized a company — which is how several company files are recognized as belonging to one person — together with the email address and display name Intuit returns for that account, if it returns them.
• Authorization records. Registered client details and issued grants, so the assistant can reconnect without reauthorizing every time.

What is not stored

QuickBooks accounting records are not copied into a database here. Requests from the assistant are passed through to Intuit's API and the results returned; they are not retained after the request completes.

How it is protected

• Tokens are sealed with envelope encryption — a per-record AES-256-GCM key, itself wrapped by a master key held as a deployment secret and never written to the database.
• All traffic is HTTPS, TLS 1.2 or better.
• The company registry is stored on the machine running this service.
• Logs are structured records carrying realm ids and hashed user ids. Tokens, authorization codes, and encrypted values are never logged.

Retention and deletion

A company's stored tokens and registry entry are deleted when it is disconnected. Revoking the app inside QuickBooks invalidates Intuit's tokens immediately. Operational logs are retained for a limited period for troubleshooting.

Your requests

To ask what is held about you, or to have it deleted, write to andyaltepeter@invenshure.com.