Backlog Guardian for Jira

Security Policy

Security practices, data handling and vulnerability reporting for Backlog Guardian.

Last updated: October 2026

1. Overview

Backlog Guardian 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

Backlog Guardian uses Atlassian Forge for application compute and persistent storage. The App does not require an external application server or external database for its core functionality.

3. Authentication and authorization

Backlog Guardian relies on Atlassian authentication and Jira permissions. Users can only access Jira data that they are authorized to access through their Jira environment.

Configuration changes are restricted according to the permissions available to the current Jira user.

4. Secrets and credentials

Backlog Guardian does not require customers to provide Jira passwords, Atlassian Personal Access Tokens or other shared authentication secrets.

5. Data handling

Backlog Guardian accesses Jira project and issue data only as required to provide its functionality.

Application configuration and scan results are stored using Atlassian Forge storage. The App does not use external analytics services, advertising services or external databases for its core functionality.

6. Security vulnerabilities

If you believe you have identified a security vulnerability in Backlog Guardian, 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 .

7. 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.

8. Dependency management

Backlog Guardian dependencies are periodically reviewed and updated. Known dependency vulnerabilities are assessed and addressed according to their severity and relevance.

9. 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.

10. Contact

Security issues can be reported directly to security@guardianapps.ch .

For non-security questions, please use the Backlog Guardian Support page.

Report a security issue

Please report potential vulnerabilities privately so we can investigate them responsibly.

security@guardianapps.ch