Privacy Policy

← QuickBooks Reports Exporter

QuickBooks Reports Exporter, published by Cody Labs. Updated 3 October 2026. Background-access disclosures below describe a proposed release awaiting deployment and installed validation.

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, using Intuit’s accounting permission. The add-on uses that permission only to read the reports you request; the permission itself is broader than report-only access.
• 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 spreadsheet for manual exports, through spreadsheets.currentonly. The proposed background release also requests drive.file and a native per-file grant so it can write scheduled reports through the Google Sheets API to spreadsheets you explicitly authorize. It does not request access to your entire 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. Disconnect removes the locally stored connection and attempts to revoke its Intuit token. Uninstalling is not a guarantee that all stored settings or previously exported data are deleted.

License verification

If you enter a license key to unlock paid features, the add-on sends only that license key and the Cody Labs organization identifier to our payment processor, Polar, to confirm your subscription is active. No QuickBooks data is involved. See Polar's privacy policy. A disabled legacy Gumroad verifier remains in the release only as a rollback path and is not called during normal use.

How the add-on uses Google user data

Manual exports use the active spreadsheet. In the proposed background release, an owner must explicitly grant a spreadsheet and save a schedule before the add-on writes reports to it while it is not open. Each registration binds the owner, spreadsheet ID, QuickBooks company (realm) and sandbox or production environment. Changing the connected company does not silently retarget an existing schedule.

The add-on reads spreadsheet metadata and its completion note, and replaces report values in the selected destination tab. A signed completion marker in the first-cell note records configuration and execution evidence so an interrupted status save can be recovered. People with access to that sheet may see the note, including its owner identifier, file/company identifiers and report configuration. The signing key stays in the owner's private add-on storage.

• Google user data is used only for the exports and status information you request;
• it is not used for advertising, profiling or model training, or sold;
• financial report data is processed in Google Apps Script and written through Google's spreadsheet services, not sent to Cody Labs or Polar.

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 QuickBooks, Google Sheets, and Polar 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: manual spreadsheet access uses spreadsheets.currentonly; script.container.ui displays the interface, script.external_request permits the disclosed API requests, and script.scriptapp manages scheduled triggers. The proposed release adds drive.file for explicitly granted spreadsheet files. It does not request broad Drive access.
• 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.
• Access controls: disconnecting removes the local QuickBooks connection and pauses scheduled exports. Remote token revocation is attempted, but is not guaranteed if the provider request fails. You can also revoke access in your Google and Intuit account settings.

Data retention & deletion

QuickBooks tokens, licence settings, and the proposed background registry live in per-user Apps Script storage. The registry includes file and company/environment bindings, report configuration and execution status. Saved manual exports and jobs also use document properties; new records are owner-scoped, while existing shared records retain their legacy behavior. Disconnect pauses schedules and preserves their configuration. Delete a saved export or switch it to manual to remove its background registration; removing the final registration also attempts to remove the owner’s dispatcher. A leftover dispatcher cannot run a removed registration. Remove schedules before uninstalling rather than relying on uninstall to erase stored settings. Exported values and completion notes remain in your spreadsheet until you delete them.

Third-party services

• Google Apps Script and Google Sheets API: process exports and, in the proposed release, write reports to explicitly granted spreadsheet files.
• QuickBooks: your own QuickBooks account, accessed with the QuickBooks OAuth connection you supply.
• Polar: handles paid subscriptions and verifies license keys during normal use.
• Gumroad: a disabled legacy verifier is retained only as a rollback path and is not called during normal use.

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.