Privacy Policy
Jira QuickView
Overview
Jira QuickView is a Chrome extension that detects Jira issue keys on pages you enable, shows Jira issue details in a hover popup, and lets you perform Jira actions without opening a separate Jira tab.
The extension does not operate a developer-run backend service. In the current implementation, it works inside your browser, stores its own settings in Chrome storage, and sends Jira requests directly from your browser to the Jira instance you configure.
Information The Extension Handles
Extension configuration data
Jira QuickView stores extension settings in Chrome storage so the extension can keep working across browser sessions. This can include your configured Jira instance URL, enabled pages or domains, popup layout, custom field IDs, theme settings, hover preferences, Team Sync source details, and Team Sync status metadata.
Page content on enabled pages
When Jira QuickView is enabled on a page, it scans page text locally in your browser to detect Jira issue keys such as ABC-123. This page scanning is used only to provide the core user-facing feature of the extension. The extension does not send full page contents to the developer.
Jira data
When you configure a Jira instance and use the extension, Jira QuickView may request and display data from that Jira instance using your existing browser session. Depending on the feature you use, this can include issue metadata, descriptions, linked records, comments, reactions, attachments, avatars, workflow options, worklogs, and custom field values.
If you use editing features, the extension may also send updates you initiate to your Jira instance, including field edits, comment creation or updates, attachment uploads, workflow transitions, watcher changes, and worklog changes.
Authentication and session data
The extension uses your existing browser session with Jira. It does not ask you to create or store a separate Jira password inside the extension.
Shared settings file data
If you enable Settings Sync, Jira QuickView may request a shared JSON configuration file from a Jira attachment on your configured Jira instance or from a direct URL that you or your administrator configured in the extension.
That shared JSON file can include organization-level Jira QuickView configuration such as layout settings, allowed page patterns, popup behavior, and Team Sync policy metadata.
How Information Is Used
Jira QuickView uses the information above only to provide the extension’s user-facing functionality, including detecting Jira issue keys on enabled pages, fetching and showing Jira issue context, rendering avatars and attachments, saving your extension preferences, loading and applying shared Team Sync configuration when you enable Settings Sync, and performing Jira actions that you explicitly trigger.
How Information Is Shared
Jira QuickView does not sell personal data. It does not send your data to advertising networks, data brokers, or analytics services run by the developer.
Information is transmitted only as needed to your configured Jira instance, using your browser session, to provide the requested feature, and to a user-configured or administrator-provided shared settings URL when you enable Settings Sync URL mode. In the current implementation, pull request information shown in the popup is obtained from Jira issue data returned by Jira, not by separate GitHub API calls from the extension.
Data Retention
Extension settings remain in Chrome storage until you change them, clear browser storage, or remove the extension. Team Sync source details and last sync metadata remain in Chrome storage until you change them, disconnect Team Sync, clear browser storage, or remove the extension. Jira issue data, images, and popup state are primarily processed in memory during use and are not stored by the developer on a separate server.
Your Choices
You can choose which pages or domains the extension is allowed to run on, change or remove the configured Jira instance URL, change or disconnect the Team Sync source at any time, remove the extension at any time, and revoke site access and Chrome permissions through Chrome’s extension settings.
Security
Jira QuickView is designed to use the minimum data needed for its features. Requests to Jira are made from your browser to the Jira instance you configured. If you enable Settings Sync URL mode, the extension also requests the shared JSON settings file from the URL you configured. The extension does not use remote code in its current implementation.
Children’s Privacy
Jira QuickView is not directed to children.
Changes To This Policy
This policy may be updated if the extension’s functionality or data handling changes. The effective date at the top of this page will be updated when changes are made.
Contact
Support: github.com/dgebaei/Jira-QuickView/issues
Email: dgebaei@gmail.com