Scope
This policy applies to ReleaseLint for Jira, an Atlassian Forge app that provides an on-demand review of direct issue dependencies for a Jira project version.
Data processed
When a user runs a review, the app transiently processes Jira project and version metadata and the issue fields required for that review: issue keys, summaries, status and status category, direct issue links, due dates and fix versions. Jira permissions and issue-security rules control what the current user can read.
The app does not request a Jira write scope or a user-profile scope. It does not use advertising identifiers, external analytics, publisher cookies, remote APIs or artificial-intelligence services.
Purpose
Data is processed only to display the dependency review requested by the user and to generate an optional CSV in that user's browser. ReleaseLint supports a human review; it does not approve a release or change Jira.
Storage, sharing and retention
ReleaseLint does not persist Jira content or app configuration. Processing runs on Atlassian Forge and results return to the current browser session. The publisher does not send Jira content to an additional subprocessor or external service. Atlassian remains the hosting platform provider under the customer's Atlassian agreements.
A downloaded CSV is controlled by the customer after download. Customers should retain and share it under their own policies.
Security and data location
The app uses current-user Forge authorization, validates inputs, requests one read-only Jira scope and contains no publisher-managed database or network service. Atlassian controls Forge hosting, encryption and data-location capabilities.
Access, correction and deletion requests
Because ReleaseLint stores no customer content, the publisher normally has no app-held customer record to access, correct, export or erase. Requests concerning Jira-hosted data should be directed to the customer's Jira administrator or Atlassian as applicable.
Contact
Privacy questions can be opened through the public ReleaseLint privacy repository issue tracker. Do not include passwords, tokens, personal data or private Jira content in a public issue.
Changes
Material changes will be posted at this same URL with a revised effective date. Where required, customers will be notified through appropriate Marketplace or support channels.