Privacy Policy

← Sheet Sync for Jira

Sheet Sync for Jira, published by Cody Labs. Effective 20 July 2026.


Sheet Sync for Jira (the “add-on”) imports issues from your Jira Cloud site 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 Jira site and your Google Sheet — Cody Labs operates no servers and never receives, stores, or transmits your issue data or your Jira credentials.

Information the add-on accesses

Where your data goes

All processing happens inside Google’s Apps Script runtime, in your Google account. Issue data is fetched from your Jira site 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 credentials are stored

Your Jira credentials are stored using Google’s PropertiesService (user properties), 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.

Scheduled refresh

If you set an import to refresh automatically, the add-on uses Google Apps Script’s time-driven triggers to re-run it on your chosen schedule. These triggers run inside your own Google account, using the credentials you stored; no data leaves that flow.

Network requests

The add-on makes outbound requests to exactly two destinations: your Jira site (to read issues) and, only if you activate a paid license, Polar (to verify the license — see below). It contacts no other services.

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 issue data or Jira credentials are involved. See Polar’s privacy policy.

Anonymous product analytics

The add-on keeps aggregate counts of six one-time milestones in Google Apps Script Properties: install, first connection, first successful run, free-limit reached, checkout opened, and license activation. The counters contain no account identifier, email, credentials, Jira issue data, spreadsheet content, or license key. Per-user markers in your Google account prevent duplicate counting and ensure a Marketplace review is requested only after the first successful import.

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 Jira issues and fields you choose to import — plus a run log — into that same spreadsheet, and to read back the cells and saved settings it previously wrote so it can refresh or resume an import you have set up. Separately, Google Workspace Marketplace shows its own standard account-identity disclosure at install time — your basic Google profile and email, used to sign you in — which is a Marketplace-level disclosure, not spreadsheet data the add-on itself reads or stores. The add-on:

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:

Data retention and deletion

We retain nothing, because we receive nothing. Data written to your spreadsheet is under your control in your Google account; stored credentials are removed when you disconnect or uninstall the add-on.

Changes and contact

Material changes to this policy will be reflected by the effective date above. Questions: [email protected].


Jira is a trademark of Atlassian Pty Ltd. Google Sheets is a trademark of Google LLC. This add-on is independent and not affiliated with or endorsed by either.