← Choose language · Polski

Privacy Policy

Last updated: 22 February 2025

1. Introduction

The Jira Issue Creator extension (“Extension”) lets you create Jira issues directly from any webpage — attaching screenshots, picking elements, and assigning team members.

This policy describes what data is collected, stored, and shared, and for what purpose.

2. Data Controller

You are the data controller for data processed by the Extension — it runs locally in your browser and does not send data to the Extension developer’s servers. The only external recipient of data is Atlassian (owner of Jira) when you explicitly create an issue.

3. What Data Is Processed

3.1. Data Stored Locally

• Authentication tokens — OAuth 2.0 access and refresh tokens used to communicate with Atlassian APIs. Stored only in your browser’s local storage (chrome.storage.local).
• Atlassian cloud information — identifier, name, and URL of your Jira instance, required to create issues.

3.2. Data Sent to Atlassian

Data is sent to Atlassian servers only when:

• you sign in via OAuth (auth.atlassian.com) — to obtain tokens and access Jira;
• you create an issue — in which case the following are sent: title, description, attached screenshots, selected page elements, and any other form fields you fill in.

Data sent to Atlassian is governed by Atlassian’s Privacy Policy.

3.3. Screenshots and Page Elements

Screenshots and information about selected elements (e.g. selector, text, link) are generated locally and sent to Jira only when you explicitly create an issue and attach them to the form. They are not sent or stored outside your Jira instance.

4. Extension Permissions

The Extension uses the following Chrome permissions:

• storage — storing authentication tokens locally.
• identity — running the OAuth flow with Atlassian.
• activeTab, scripting, offscreen — capturing screenshots and picking elements on the currently active tab.
• tabs, sidePanel — displaying the side panel and managing tabs.
• alarms — refreshing tokens in the background.
• host_permissions — access to Atlassian sites (api.atlassian.com, auth.atlassian.com, *.atlassian.net) and to pages where you create issues (e.g. for screenshots).

5. No Tracking or Analytics

The Extension does not collect analytics, use tracking cookies, or send data to any servers other than Atlassian. It has no integrations with analytics or advertising tools.

6. Data Deletion

You can delete all Extension data at any time by:

• signing out from the Extension (this removes tokens from local storage);
• uninstalling the Extension — Chrome then removes locally stored data.

Data already sent to Jira remains in your Atlassian instance according to its retention policy.

7. Security

Authentication tokens are stored in Chrome’s isolated extension storage and are not shared with other extensions or websites. Communication with Atlassian uses HTTPS. The Extension uses OAuth 2.0 with PKCE.

8. Policy Changes

Changes to this policy will be published on this page with an updated “Last updated” date. We recommend checking this page periodically.

9. Contact

For questions about privacy and data processing, contact the Extension developer via the project repository or the contact channel indicated there.