Last updated: October 2026
1. Overview
Blocker Radar for Jira is provided by Guardian Apps and is built on Atlassian Forge. Security is considered throughout the design, development and operation of the App.
2. Hosting and infrastructure
Blocker Radar runs on Atlassian Forge-hosted infrastructure. The App does not require an external application server or external database for its core functionality.
The current version has been verified as eligible for Atlassian's Runs on Atlassian program.
3. Authentication and authorization
Blocker Radar relies on Atlassian authentication and Jira platform permissions.
Access to the App requires access to the relevant Atlassian Jira Cloud environment.
4. Secrets and credentials
Blocker Radar does not require customers to provide Jira passwords, Atlassian API tokens, Personal Access Tokens or shared authentication credentials.
5. Data handling
Blocker Radar reads Jira issue and issue-link information only as required to identify and display active blocker relationships.
The current version does not persist Jira issue content or blocker relationships in an external database and does not send this data to external analytics or advertising services.
6. Jira permissions
Blocker Radar uses read-only Jira access for its current functionality.
The App does not require permission to modify Jira issues in order to provide the Blocker Radar view.
7. Security vulnerabilities
If you believe you have identified a security vulnerability in Blocker Radar, please report it privately and do not disclose the issue publicly before it has been investigated.
Security reports should include, where possible:
- a description of the issue
- steps to reproduce the issue
- the potential impact
- relevant screenshots or error messages
Do not include passwords, authentication tokens or unnecessary confidential customer data in security reports.
Security issues can be reported privately at security@guardianapps.ch .
8. Security response
Guardian Apps will review reported security issues and prioritize remediation based on severity, exploitability and customer impact.
Where appropriate, fixes will be deployed through the Atlassian Forge deployment process.
9. Dependency management
Blocker Radar dependencies are periodically reviewed. Known dependency vulnerabilities are assessed according to their severity and relevance to the App.
10. Changes to this policy
This Security Policy may be updated as the App evolves or security requirements change. The current version will remain available at this URL.
11. Contact
Security issues can be reported directly to security@guardianapps.ch .
For non-security questions, please use the Blocker Radar Support page.