Privacy Policy
Draft, ready to host. The Marketplace distribution form requires a Privacy policy URL before an app can be shared or listed; this is that page's content.
Host at https://<domain>/issue-hierarchy/privacy and put the URL in the developer console under Distribution → Edit → Privacy policy.
Issue Hierarchy for Jira shows the epic-to-subtask hierarchy of any work item, and across projects from any JQL filter.
The app runs entirely on Atlassian's own infrastructure using Atlassian Forge, and it is eligible for the Runs on Atlassian programme. It calls no external service, and it declares no remote hostnames. Nothing this app reads leaves Atlassian's infrastructure, and the vendor has no server that your data passes through.
Nothing. The app has no Forge storage, no database and no external service. Every render reads live from Jira and is discarded once the response is sent. Nothing persists between one page load and the next.
To build a hierarchy tree the app reads work items and their parent relationships, issue types, status and story-point fields. To show who owns each row it reads the display name and avatar of assignees. The app is read-only: it never creates, changes or deletes anything in Jira.
All reads run as the signed-in user (asUser), so the app can only ever show what that person could already see in Jira themselves.
No account IDs, email addresses, display names or avatars
No work item content of any kind
No credentials or tokens
No analytics, telemetry or tracking of any kind
Scope | What it is for |
|---|---|
| Read work items and their parent relationships, issue types, status and story-point fields to build the tree |
| Read the display name and avatar of assignees so each row can show who owns the work |
The app deliberately does not request any write, delete or configuration scope, and does not use offline user impersonation.
There is nothing to retain or delete: the app stores no data of its own, in Forge storage or anywhere else.
Because the app stores nothing, there is no data of the vendor's to reside anywhere. Any work item data it displays stays inside your own Atlassian cloud instance, under your own instance's data residency, exactly as it already does today.
Questions about this policy, or a request to remove data: support@maxpetrov.pp.ua
Last updated: 5 October 2026.