Skip to content

Privacy Policy - Qaden - SLA Engine for Jira

Effective Date: 01 February 2026

1. Introduction

Qaden is a Forge-based application designed for Atlassian Cloud environments. It provides multi-objective SLA automation, business calendar tracking, and issue visibility inside Jira Cloud.

This Privacy Policy explains how Qaden processes data when used within Jira Cloud.


2. Scope

This Privacy Policy applies to the Qaden application available through the Atlassian Marketplace and installed within Jira Cloud.

Qaden does not operate external servers for data processing and does not collect personal data outside the Atlassian Cloud environment.


3. What Data Qaden Processes

Qaden processes only the data necessary to compute and display SLA objectives. This may include:

  • Issue fields such as status, timestamps, and workflow metadata
  • Project and issue type identifiers
  • Objective definitions, calendars, and configuration metadata
  • User identifiers for notification recipients (assignees, users, groups)
  • Objective state and timer metrics stored in Forge storage

Qaden does not access or process data beyond the permissions granted during installation.


4. How Data Is Processed

Qaden is built on Atlassian Forge and operates within Atlassian Cloud infrastructure. Data processing occurs within the Forge runtime and interacts with Jira Cloud using the permissions granted to the app.

Qaden does not:

  • Route customer data through external servers
  • Store Jira issue content outside Atlassian Cloud
  • Transfer data to third-party analytics platforms

5. Notifications

Qaden can send notifications using Jira’s native notification system when SLA thresholds are approaching or breached.

Notifications are delivered through Jira and respect Jira user notification preferences and system email configuration.


6. Data Storage

Qaden stores limited configuration data required to operate, such as:

  • Objective definitions and notification rules
  • Business calendar configurations
  • Objective state, timers, and time-in-status metrics
  • Project and issue type mappings

This information is stored within Atlassian Forge storage. Qaden does not maintain external databases for customer data.


7. Data Sharing

Qaden does not sell, rent, or share customer data with third parties.

Data is processed within Jira Cloud and Forge infrastructure. Notification messages are sent only to Jira users and groups configured by administrators.


8. Analytics and Tracking

Qaden does not include:

  • Behavioral analytics
  • Usage tracking
  • Telemetry collection
  • Advertising technology

No personal data is collected for marketing purposes.


9. Access to Data

Qaden accesses Jira data strictly according to the permissions granted during installation. Administrators control the app's access via Jira's permission and app management controls.

The Qaden development team does not have access to customer Jira data through the app.


10. Data Retention

Qaden retains configuration data for as long as the app remains installed.

When the app is uninstalled:

  • Forge-managed storage is removed in accordance with Atlassian's platform lifecycle.
  • No external backups of Jira issue content are maintained by Qaden.

11. Security Measures

Qaden relies on Atlassian Forge security controls, including:

  • Runtime isolation
  • Permission-based access controls
  • Secure storage APIs
  • Platform-managed infrastructure security

12. International Data Transfers

Because Qaden operates within Atlassian Cloud infrastructure, data processing aligns with the data residency configuration of the customer's Jira Cloud environment. Qaden does not independently transfer data outside Atlassian infrastructure.


13. Changes to This Policy

This Privacy Policy may be updated to reflect improvements or changes in functionality. The latest version will always be available within the app listing.


14. Contact

For privacy-related inquiries regarding Qaden - SLA Engine for Jira, please visit here.

Last Updated: 01 February 2026