Security Policy for User Manager for Jira
Last updated: March 31, 2026
This Security Policy describes the baseline security practices that D&L applies to User Manager for Jira (the "App") for Jira Cloud.
The App is built on Atlassian Forge and is intended for business use by Jira Cloud customers.
- Security principles
We design and operate the App with the following principles in mind:
- least privilege access to Jira and App data
- use of Atlassian-hosted infrastructure wherever practical
- limiting persistent storage to configuration and operationally necessary data
- controlled access to support and maintenance activities
- reasonable safeguards for confidentiality, integrity, and availability
- Platform and hosting model
The App runs on Atlassian Forge and uses Atlassian-hosted compute and Atlassian-hosted storage for App data.
Based on the current implementation, the App does not use a separate vendor-operated backend to store in-scope End-User Data outside of Atlassian apps and services. Network requests made by the App are limited to Jira Cloud and Atlassian APIs required for App functionality.
- Authentication and authorization
The App relies on Atlassian Forge authentication and the permissions granted during App installation.
Access to the App dashboard can also be restricted through App configuration so that only Jira administrators and customer-selected users or groups can open the dashboard.
Within our organization, access to App source code, configuration, and operational tooling is intended to be limited to personnel who require that access for development, maintenance, support, or security purposes.
- Data handling and minimization
The App is designed to process Jira user, group, project, and activity data only to provide its dashboard and related user insight features.
Persistent App storage is intended to be limited to:
- App configuration and access settings
- an optional customer-provided Atlassian Admin API key, if configured by a customer administrator
- short-lived cached operational data used to improve App performance
We aim to avoid storing more data than is reasonably necessary for the App to function.
- Encryption and transport security
The App depends on Atlassian cloud platform controls for secure transport and hosted service protections. Communications with Jira Cloud, Atlassian APIs, and Forge services are expected to occur over HTTPS.
Where customer-provided secrets are stored by the App, they are stored through Atlassian Forge hosted storage rather than in a separate vendor-managed database.
- Secrets and credentials
The App does not require end users to provide Jira account passwords or Atlassian Personal Access Tokens for normal operation.
A customer administrator may optionally configure an Atlassian Admin API key to enable additional profile enrichment features. If configured, the key is stored in Atlassian Forge storage and should be managed by the customer in accordance with its internal security policies.
Customers are responsible for rotating, replacing, or removing optional secrets they configure in the App when appropriate.
- Logging, monitoring, and troubleshooting
The App may generate operational logs and warnings to support debugging, maintenance, and error handling. We aim to keep logs limited to what is reasonably necessary for support and security purposes.
Where feasible, we seek to avoid unnecessary exposure of End-User Data in logs. Customers should understand that diagnostic records on hosted platforms can still contain limited technical metadata associated with App operations.
- Vulnerability management
We aim to address security issues in a risk-based manner and to remediate verified vulnerabilities within a reasonable timeframe, taking into account severity, exploitability, and platform constraints.
When relevant, we review Atlassian Marketplace security requirements, Atlassian platform updates, dependency advisories, and issue reports received through our support or security contact channels.
- Incident response
If we become aware of a confirmed security incident affecting the App, we will assess the scope, impact, and required remediation steps. Where notification is required by applicable law, contract, or Atlassian platform obligations, we will provide notice within a reasonable time after verification.
Our response may include investigation, containment, corrective changes, credential rotation guidance, and additional customer communication where appropriate.
- Customer responsibilities
Customers remain responsible for their Jira administration and internal security decisions, including:
- deciding whether to install and enable the App
- configuring which users or groups may access the App
- managing any optional Atlassian Admin API key provided to the App
- reviewing whether the App is appropriate for their compliance and governance requirements
- Responsible disclosure and contact
To report a suspected security issue, vulnerability, or abuse concern related to the App, contact:
- Security contact: dario3c0@gmail.com
Please include enough detail to reproduce or assess the issue, such as the affected feature, a description of impact, steps to reproduce, and any relevant timestamps or screenshots.
We request that reporters act in good faith, avoid privacy violations or service disruption, and do not publicly disclose a suspected vulnerability before we have had a reasonable opportunity to investigate and address it.
- Changes to this policy
We may update this Security Policy from time to time to reflect changes in the App, our practices, legal requirements, or Atlassian platform capabilities. If we make a material update, we will revise the "Last updated" date above.
- Contact information
D&L
Security contact: dario3c0@gmail.com
General support: dario3c0@gmail.com