Last updated: October 2026
1. Overview
Blocker Radar for Jira ("Blocker Radar", "the App") is provided by Guardian Apps. This Privacy Policy explains how Blocker Radar processes data when installed and used in Atlassian Jira Cloud.
2. Hosting and infrastructure
Blocker Radar is built on Atlassian Forge and runs on Atlassian-hosted infrastructure.
The App does not require an external application server, external database or third-party hosting service for its core functionality.
Blocker Radar is designed to be eligible for Atlassian's Runs on Atlassian program.
3. Data accessed from Jira
Blocker Radar reads Jira information required to identify and display active blocking relationships, including:
- Issue keys
- Issue summaries
- Issue status and status category
- Issue priority
- Assignee display name
- Project name
- Jira issue links and their relationship types
This information is used to identify active "is blocked by" relationships and present them to Jira users.
4. Data stored by the App
The current version of Blocker Radar does not persist Jira issue content, blocker relationships or Atlassian user profiles in its own application storage.
Jira data is retrieved when the App is used and processed to produce the Blocker Radar view.
5. Personal data
Blocker Radar may display an assignee's Jira display name as part of the issue information returned by Jira.
The App is not designed to persist Atlassian email addresses, passwords, authentication credentials or user account profiles in its own application storage.
6. Data sharing
Blocker Radar does not sell customer or user data.
The App does not send Jira issue data to third-party advertising, analytics or external application services as part of its core functionality.
7. Permissions
Blocker Radar requests the Jira read permissions required to retrieve issue information and issue-link relationships used by the App.
The App does not require Jira write permissions for its current functionality.
8. Data residency
Blocker Radar uses Atlassian Forge-hosted compute. Data residency capabilities therefore depend on the capabilities provided by Atlassian Forge and the relevant Atlassian Cloud product.
9. Security
Blocker Radar relies on Atlassian Forge infrastructure, authentication and platform security controls.
Customers remain responsible for configuring Jira access and permissions appropriately for their users.
10. Data retention and deletion
The current version of Blocker Radar does not maintain a persistent application database containing Jira issues or blocker relationships.
Removing the App therefore does not require deletion of a separate external Blocker Radar customer database.
11. Changes to this Privacy Policy
This Privacy Policy may be updated as Blocker Radar develops or legal and technical requirements change. The current version will remain available at this URL.
12. Contact
For privacy questions regarding Blocker Radar, please use our support page.