QueueGuard Privacy Policy
Effective date: May 5, 2026
Contact: contact QueueGuard support
QueueGuard is a standalone Chrome extension for Jira Service Management. QueueGuard provides workflow governance and decision support by ranking visible Jira queue/list items, surfacing operational risk signals, and guiding execution order.
QueueGuard is designed to run locally in your browser. QueueGuard does not operate a QueueGuard backend service and does not send Jira data to QueueGuard servers.
1. What QueueGuard Does
QueueGuard helps users evaluate visible Jira Service Management queue/list items by providing:
- Queue risk ranking
- SLA confidence indicators
- Execution guidance
- Queue health signals
- Governance reasoning
- Local configuration and licensing controls
QueueGuard evaluates visible Jira queue/list items only. It does not inspect hidden Jira data beyond what is available to the user through the configured Jira page or Jira Cloud connection.
2. Information QueueGuard Processes
QueueGuard may process Jira issue information that is already visible or available to the user in Jira, including:
- Issue key
- Issue summary
- Issue status
- Priority
- Assignee
- Reporter or visible user-related fields
- Age or staleness indicators
- Available SLA-related information
- Visible queue/list structure
This processing occurs locally in the browser extension context and is used only to provide QueueGuard’s queue governance, ranking, execution, and decision-support features.
3. Information Stored Locally
QueueGuard stores configuration locally in Chrome extension storage, including:
- Jira site URL
- Atlassian email used for the configured Jira connection
- Jira API token or credential information
- QueueGuard license state
- User preferences
- Governance settings
- Execution and display settings
Jira credentials and tokens are stored locally in Chrome extension storage. QueueGuard does not send these credentials to a QueueGuard backend.
4. Data Transmission
When configured, QueueGuard sends requests directly from the Chrome extension to the user’s configured Jira Cloud site.
QueueGuard does not proxy Jira data through a hosted QueueGuard service. QueueGuard does not transmit Jira queue data, issue data, credentials, or tokens to QueueGuard servers.
5. Remote Code
QueueGuard does not use remote hosted code for its core extension logic.
All core JavaScript used by the extension is included in the packaged Chrome extension files. QueueGuard does not load external JavaScript or WebAssembly from a QueueGuard server or third-party code host.
6. How QueueGuard Uses Data
QueueGuard uses visible Jira queue/list data only to provide its single purpose:
- Ranking queue work
- Evaluating operational risk
- Showing SLA confidence
- Guiding execution order
- Displaying queue health
- Explaining governance reasoning
- Supporting local configuration and license state
QueueGuard does not use Jira data for advertising, credit decisions, lending, unrelated analytics, or unrelated profiling.
7. Data Sharing
QueueGuard does not sell user data.
QueueGuard does not share Jira data with third parties through a QueueGuard backend.
QueueGuard does not transfer user data for purposes unrelated to its single purpose of Jira queue governance and decision support.
8. Authentication Information
QueueGuard may store Jira API tokens or credential-related information locally in Chrome extension storage so the extension can connect directly to the configured Jira Cloud site.
Users are responsible for creating and managing their Jira API token through Atlassian. QueueGuard does not send Jira API tokens to QueueGuard servers.
9. User Control
Users can remove QueueGuard data by:
- Clearing the license or configuration from the QueueGuard Options page
- Clearing saved Jira credentials from the QueueGuard Options page
- Removing the QueueGuard extension from Chrome
- Clearing Chrome extension storage through browser settings, where applicable
Removing the extension from Chrome removes extension-local data stored by QueueGuard.
10. Security
QueueGuard is designed as a local-first standalone Chrome extension. Configuration and credentials are stored in Chrome extension storage on the user’s device.
No method of local storage or data transmission can be guaranteed to be perfectly secure, but QueueGuard is designed to limit data movement by avoiding a QueueGuard backend and sending configured Jira requests directly between the extension and the user’s Jira Cloud site.
11. Changes to This Privacy Policy
This privacy policy may be updated as QueueGuard evolves. Updates will be posted on this page with a revised effective date.
12. Contact
For privacy questions, support requests, or data-handling questions related to QueueGuard, contact: contact QueueGuard support.