Privacy

Last updated June 2026

Snap to Jira is built so your captures stay yours. Here is exactly what that means.

Captures stay on your device

Screenshots, full-page captures, and screen recordings are created and edited locally in your browser. Nothing is uploaded until you click Send — at which point your capture and ticket details go directly to your Jira site.

Deep context is opt-in, per app

Steps to reproduce, console errors, and failed network requests are collected only on the domains you explicitly add under “Your apps.” On every other site, Snap to Jira does nothing in the background. This context records what was interacted with (control labels), never the values you type.

Connecting Jira

You connect Jira with one-click OAuth. We never see your Atlassian password. Access credentials are stored encrypted and used only to create the tickets you send.

Analytics

We collect anonymous, aggregate usage analytics (Google Analytics, through a backend proxy) to understand which features get used. Analytics carries no account identifiers, and we never record the contents of your captures or what you type.

Permissions, explained

storage — save your Jira connection and preferences locally.
activeTab + scripting — capture the page you are on, only when you click.
downloads — let you save a screenshot locally.
identity — one-click Jira (OAuth) sign-in.
notifications — alert you if your Jira session needs reconnecting.
webRequest + optional host access — collect failed-request context, only for the domains you add under “Your apps.”

What we never do

Sell or share your data.
Read or collect anything on sites you have not added.
Record the values you type into forms.

Questions

Reach out through the Chrome Web Store support tab and we will help.