CopyMyBooks

Privacy policy

Last updated October 18, 2026

In short

Who we are

This policy covers CopyMyBooks (copymybooks.com), called "CopyMyBooks", "we" or "us" here. For anything about it, email [email protected].

What CopyMyBooks does

CopyMyBooks helps software developers who build apps for QuickBooks Online. With the company owner's approval, it reads a real QuickBooks company and copies it into a test company (a QuickBooks "sandbox") that belongs to the developer, so they can test against realistic books. Two kinds of people use it:

What we collect

Data Where it comes from Why
Developer's name, email address, profile picture, and the sign-in provider's ID for your account (to recognise you next time) The sign-in provider you choose (Google, GitHub or Intuit) To sign you in and run your account
Access to your QuickBooks sandboxes (tokens) Intuit, when you connect a sandbox To clear your sandbox and write copies into it
Access to an approved company (tokens), which CopyMyBooks uses only to read it Intuit, when the company owner approves To read the company when the developer makes a copy
The company's accounting records: lists (customers, vendors, products, accounts), transactions, reports, tax settings, and attached files if the developer chooses them QuickBooks, read only To make the copy the developer asked for
The email address a developer enters when sending a connect link The developer To send the invitation, and a receipt once access is approved
The protections the company owner chooses The company owner To apply them to every copy (see below)
Job history: what was copied, when, counts, and records QuickBooks refused (it can name individual records). Unless amounts were disguised, a copy's check also keeps the real company's report totals (income, expenses, assets and so on) it compared. CopyMyBooks To show the developer their results
Server logs: IP address, pages requested, errors, and sometimes a QuickBooks company's ID. Your browser and our server To keep the service running and secure

How long we keep it

Protections the company owner chooses

When approving, the company owner can require that every copy:

Disguising works on fields named as such; other free text and files aren't searched. The developer can't turn off a protection the owner required: changing it takes a new approval by an admin of the QuickBooks company.

Where the copy goes

A copy is written only into a QuickBooks sandbox the developer connected. Sandboxes are test companies in the developer's Intuit developer account, and Intuit's terms govern them. Once a copy is in the developer's sandbox, the developer is responsible for it.

Who we share it with

We don't sell or rent personal or company data, and we don't use it for advertising or to train AI models. We share it only with the services that run CopyMyBooks:

We may also disclose data if the law requires it.

Cookies and storage

We use no advertising or tracking cookies and no analytics. Signing in keeps a session token in your browser's local storage. Signing in with Google, GitHub or Intuit, and connecting to QuickBooks, each set a short-lived cookie (minutes) that makes sure the step finishes in the same browser that started it.

Security

Everything travels over HTTPS. Access tokens and stored books are encrypted at rest (AES-256-GCM). CopyMyBooks asks QuickBooks only to read a real company and never writes to it; writing happens only in sandboxes.

Your choices and rights

Children

CopyMyBooks is a tool for businesses. It isn't meant for anyone under 18.

Changes

If we change this policy, we'll update the date above and, for important changes, email developers with an account.