Privacy Policy for Backlog Guardian for Jira

Last updated: October 2026

1. Overview

Backlog Guardian for Jira ("Backlog Guardian", "the App") is provided by Guardian Apps. This Privacy Policy explains how Backlog Guardian processes data when installed and used in Atlassian Jira Cloud.

2. Hosting and infrastructure

Backlog Guardian is built on Atlassian Forge.

Application compute and persistent application storage are provided by Atlassian infrastructure. Backlog Guardian does not use an external application server or external database for its core functionality.

3. Data accessed from Jira

Backlog Guardian accesses Jira data required to provide backlog health checks, including information such as:

• Jira project identifiers and names
• Issue keys
• Issue summaries
• Issue status
• Assignee status
• Due dates
• Issue update timestamps
• Estimate information
• Issue type and hierarchy information

This information is used to calculate backlog health checks and display affected Jira issues to authorized users.

4. Data stored by the App

Backlog Guardian stores application configuration and scan results using Atlassian Forge storage.

Stored information may include:

• Project key
• Monitoring enabled or disabled state
• Stale issue threshold
• Stale epic threshold
• Selected estimate method
• Latest scan timestamp
• Aggregated check counts
• Backlog Health Score and score breakdown

Backlog Guardian is designed not to persist Atlassian user profiles, email addresses, user account IDs, passwords or authentication credentials in its application storage.

5. Personal data

Backlog Guardian does not intentionally store personal data associated with individual Atlassian users in its own application storage.

Jira issue data displayed by Backlog Guardian is retrieved from Jira when required and is subject to the permissions of the current Jira user.

6. Data sharing

Backlog Guardian does not sell customer or user data.

The App does not send Jira data to third-party advertising services, analytics providers or external application databases as part of its core functionality.

7. Permissions

Backlog Guardian requests Jira permissions required to read project and issue data and to provide its functionality.

Interactive access to Jira data is performed using the permissions of the current Jira user where applicable.

8. Data residency

Backlog Guardian uses Atlassian Forge-hosted services. Data residency capabilities therefore depend on and follow the capabilities provided by Atlassian Forge and the relevant Atlassian Cloud product.

9. Security

Backlog Guardian is designed to use Atlassian-hosted infrastructure and Forge security controls.

Customers remain responsible for configuring Jira permissions appropriately for their users.

10. Data retention and deletion

Application configuration and scan data are stored within Atlassian Forge storage for as long as required to provide the App.

Data associated with an installation may be removed in accordance with Atlassian Forge storage and uninstall lifecycle behavior.

11. Changes to this Privacy Policy

This Privacy Policy may be updated as Backlog Guardian develops or legal and technical requirements change. The current version will always be published at this URL.

12. Contact

For privacy questions regarding Backlog Guardian, please use our support page.