Privacy Policy

← QuickBooks Reports Exporter

QuickBooks Reports Exporter, published by Cody Labs. Effective 2 August 2026.

QuickBooks Reports Exporter (the "add-on") moves your QuickBooks data into your own Google Sheets. This policy explains what the add-on accesses and how that data is handled. The short version: your data flows directly between your QuickBooks account and your Google Sheet. Cody Labs operates no servers and never receives, stores, or transmits your financial data or your QuickBooks OAuth connection.

Information the add-on accesses

• A QuickBooks OAuth connection you authorize, used to authenticate to the QuickBooks Online API on your behalf, scoped to report reads only.
• Financial report data, the report rows returned by the Profit and Loss, Balance Sheet, Trial Balance, Cash Flow, Aged Receivables, Aged Payables, Customer Sales, and Vendor Expenses reports you choose to save and run.
• The active Google Spreadsheet, only the spreadsheet you run the add-on in (via the restricted spreadsheets.currentonly scope). The add-on cannot see your other files in Google Drive.

Where your data goes

All processing happens inside Google's Apps Script runtime, in your Google account. Financial data is fetched from your QuickBooks account and written into your spreadsheet. It is not sent to Cody Labs or any third party. We have no database and no server that could receive it.

How your QuickBooks OAuth connection is stored

Your QuickBooks OAuth tokens are stored per user by the official Apps Script OAuth2 library, scoped to your Google account. They are never written into the spreadsheet and are not visible to other people you share the sheet with. They remain until you disconnect or uninstall the add-on, at which point they are removed.

License verification

If you enter a license key to unlock paid features, the add-on sends only that license key and a product identifier to our payment processor, Gumroad, to confirm your subscription is active. No QuickBooks data is involved. See Gumroad's privacy policy.

How the add-on uses Google user data

The only Google user data the add-on accesses is the content of the single Google Sheets spreadsheet you open it in, through the spreadsheets.currentonly scope. It uses that data for one purpose only: to write the QuickBooks report rows you choose to export, plus status notes and a run log, into that same spreadsheet, and to read back the cells it previously wrote so it can update or resume an export you have set up. The add-on:

• never reads or writes any other file in your Google Drive (the spreadsheets.currentonly scope makes this technically impossible);
• never uses your Google user data for advertising, profiling, or training any model;
• never sells your Google user data or shares it with third parties; and
• never transmits it to Cody Labs or any external server, all processing runs inside Google's Apps Script runtime under your own account.

The add-on's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Data protection & security

We protect your data, including any sensitive data, with the following mechanisms:

• Encryption in transit: every network request (to the QuickBooks API, and to Gumroad for license checks) is made over encrypted HTTPS/TLS.
• Encrypted, isolated credential storage: your QuickBooks OAuth tokens are held by the official Apps Script OAuth2 library, encrypted at rest by Google and scoped to your own Google account. They are never written into the spreadsheet and are never exposed to other people you share the sheet with.
• Least-privilege access: the add-on requests only the narrow spreadsheets.currentonly, script.container.ui, script.external_request, and script.scriptapp scopes, so it can only ever touch the active spreadsheet, the endpoints described above, and its own scheduled triggers, never your wider Google Drive or account.
• Read access only: this add-on only reads QuickBooks data into your spreadsheet; it never writes back to your QuickBooks account.
• No developer-side attack surface: Cody Labs runs no servers and no database, so your Google user data and your QuickBooks data are never received, stored, or processed on our systems, there is no back end that could be breached.
• Immediate revocation: disconnecting or uninstalling the add-on removes the stored QuickBooks OAuth connection and revokes its access straight away.

Data retention & deletion

Because we store nothing on our own systems, there is nothing for us to retain or delete. Your QuickBooks OAuth connection and settings live in your Google account's add-on storage and are removed when you disconnect or uninstall. Report data lives in your spreadsheet, under your control.

Third-party services

• QuickBooks: your own QuickBooks account, accessed with the QuickBooks OAuth connection you supply.
• Gumroad: used only to verify license keys for paid subscriptions.

Changes

We may update this policy; material changes will be reflected by the effective date above.

Contact

Questions about this policy: [email protected].

QuickBooks and Google Sheets are trademarks of their respective owners. This add-on is independent and is not affiliated with or endorsed by either.