BlueTrue Books
Blue True Books LLC

Privacy policy

Last updated: October 11, 2026 · Business software pilot

This notice explains how the current BlueTrue Books pilot handles information and how to contact its operator.

On this page

1. Who we are and when this policy applies

Blue True Books LLC operates BlueTrue Books, a business accounting and bookkeeping workflow application. This policy describes our current pilot application, its public information pages, and the information processed when an authorized user uses available features or contacts us.

Bookkeeping firms and client businesses determine the records they submit, the purposes for their accounting work, and their authorized users. We process those business records to provide the service under authorized instructions. We also use account, security and support information for our own service administration. A firm's separate bookkeeping engagement and privacy notices are not replaced by this policy.

2. Information processed

Submit only information necessary for the authorized business task. Do not place passwords, secret keys, full payment-card details or unrelated sensitive records in transaction memos, uploads or support messages.

3. How information is used

We use information to authenticate users; enforce firm and company permissions; store and display authorized business records; perform requested accounting and source-file comparisons; route authorized documents and communications; maintain change history and source evidence; troubleshoot problems; prevent unauthorized use; and respond to support, privacy and legal requests.

Source retrieval and matched comparison fields are review evidence. They do not by themselves establish that a complete company's books have been transferred or certified.

4. QuickBooks Online connections

A firm Owner chooses and confirms the QBO company through Intuit authorization. The current historical-source workflow reads available records and selected-period reports into separate retained source storage. It preserves raw source fields and review evidence subject to displayed coverage and capacity limits. The current source reader does not create, edit or delete QBO accounting transactions.

Current records returned by QBO are not necessarily a complete history of deleted records, earlier versions, payroll, reconciliations, bank-feed items or other subsystems. Attachment metadata and transaction links may be retained; this source workflow does not retrieve original receipt/PDF/image contents or perform OCR.

Disconnecting or revoking permission stops future authorized retrieval. It does not automatically erase source records already saved in BlueTrue, financial/audit history, downloaded exports or copies held by a firm or user. See the retention and request sections below.

5. When information is shared

Business records are available to the firm, company and portal users authorized for the applicable workflow. What a client user can see may differ from what assigned firm staff can see. Access to one company does not intentionally grant access to another company's books.

We use service providers as needed for the enabled service. The current pilot uses Cloudflare for hosting and application data storage and Clerk for sign-in and identity checks. Configured features may use Resend for application email/reply processing, Google Drive for a firm's chosen document storage, Intuit for QBO authorization and source retrieval, and Stripe for supported payment test workflows. Providers receive information needed for those functions and have their own privacy and service terms. A listed optional integration is not automatically enabled for every company.

Following a transaction's Google search link sends the selected bank memo as a search query to Google. This happens when you choose the external link, not as an automatic source pull. Review the memo before sending it outside the workspace.

We may disclose information when required by law or valid legal process, to protect rights/security or investigate misuse, and in a business reorganization subject to appropriate protections and applicable notice requirements. We do not sell client records or use client financial records for targeted advertising.

6. AI and automated review

The current QBO CSV/XLSX discrepancy review uses programmed comparison rules. It does not submit those source files to a public generative-AI service or train a public AI model on client books. Receipt/PDF/image content review and OCR are not implemented in this QBO source workflow.

Before enabling a future feature that sends records to an additional AI/OCR provider, we will describe its data use, providers and controls, update relevant notices, and obtain authorization where required. This statement is not a promise about unreviewed future providers.

7. Sessions, cookies and public pages

The signed-in application uses authentication/session information. QBO authorization uses a short-lived browser confirmation cookie and a one-time authorization attempt to bind the connection to the initiating browser and user. These are used to provide and secure requested features.

The license, privacy, connect-information and disconnect-information pages added with this policy contain no application data requests, sign-in scripts, analytics scripts or advertising trackers. Hosting still processes the network requests needed to serve them.

8. Security

The pilot uses HTTPS delivery, verified identity and role checks, server-side firm/company access controls, protected QBO authorization-token storage and recorded change/source evidence. We restrict access according to assigned permissions and investigate reported access concerns.

No service is completely secure. This policy is not a certification of SOC 2, ISO, PCI, HIPAA or any other framework, and it does not promise a particular geographic data-residency boundary. Production security, recovery and operational acceptance must be evaluated before expanding the pilot.

9. Retention and deletion

During an authorized pilot, accounting records, raw source archives, discrepancy reviews and audit history are retained for testing, review, record integrity and recovery. Some source/audit records are protected against ordinary editing or deletion. Disconnecting an integration, closing a browser window or removing a user's access does not erase company data.

The current pilot does not offer an automatic full-company purge or a promised fixed backup-deletion schedule. Deletion and retention requests require verified operator review. We will identify what can be removed, what a firm or client must authorize, and what must be retained for legal, security or recordkeeping reasons. A production retention and controlled-deletion program remains required before broader live use.

Downloaded exports and copies in a firm's separately controlled storage are controlled by that firm or recipient. Their removal requires action by the applicable controller. For a request about retention or deletion, contact the address below and identify the relevant firm/company without sending unnecessary sensitive records.

10. Requests and choices

You may request information about our use of your data, access or correction, deletion, restriction or other rights provided by applicable law. Contact info@bluetruebooks.com. We verify identity and authority before disclosing or changing business records. Available rights and exceptions depend on applicable law and the record involved.

For records managed by your bookkeeping firm or employer, contact that organization first; we can assist its authorized request. You may also ask the firm Owner to remove your application access or disconnect the relevant integration. Removing access is different from deleting records.

11. Intended users and changes

BlueTrue Books is intended for adults authorized to perform business accounting and related work. It is not directed to children. Contact us if you believe a child has submitted personal information without appropriate authorization.

We may revise this policy as the service changes. We will post a revised date and provide additional notice or obtain authorization where required for material changes. A future commercial, AI, payment or integration release may require an updated notice; this pilot policy does not establish those features as currently available.

12. Contact

Blue True Books LLC
Support and privacy inquiries: info@bluetruebooks.com

Please describe the issue and the relevant firm/company. Do not send account passwords, payment-card information or confidential client files unless an appropriate secure method has been arranged.