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-tree-templates/privacy and put the URL in the developer console under Distribution → Edit → Privacy policy.
Issue Tree Templates for Jira lets you save a Jira work item and everything beneath it as a reusable template, then recreate that structure in any project on your site.
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 or writes leaves Atlassian's infrastructure, and the vendor has no server that your data passes through.
Templates are stored in Forge storage, which is hosted by Atlassian inside your Atlassian cloud environment and is scoped to your installation of this app.
When you save a work item as a template, the app stores a copy of that item and its descendants:
issue type names, hierarchy levels and the parent/child structure
summaries and descriptions
the values of fields the target project would accept on create
the links between the captured items
The app stores no personal data. When a captured work item has a value in a user field — most commonly Assignee, but also any custom user-picker field — the app does not store that person. It replaces the value with a named variable, such as {{assignee}}, and asks who it should be each time the template runs. The account ID you pick is used for that one run and is never written to storage.
That is also better behaviour: a template that hard-codes whoever happened to be assigned on the day is wrong the next time you use it.
The app also stores, per template: how many times it has been run, how many work items it created, and when it was last run.
No account IDs, email addresses, display names or avatars
No attachments
No comments or work logs
No credentials or tokens
No analytics, telemetry or tracking of any kind
To report what will happen before creating anything ("preflight"), the app reads the target project's issue types and field metadata. To save a template it reads the chosen work item and its children. Saving a template only ever reads; it never changes anything in Jira.
All reads and writes run as the signed-in user, so the app can only ever see or create what that person could see or create themselves.
Scope | What it is for |
|---|---|
| Read project field metadata for preflight, and read a work item and its children when saving a template |
| Create the work items a template describes, and the links between them |
| Store templates in Forge storage inside Atlassian |
The app deliberately does not request manage:jira-configuration, does not request delete:jira-work, and does not use offline user impersonation.
Templates persist until someone deletes them in the app. Deleting a template removes its content and its usage statistics.
Uninstalling the app removes all of its stored data, because Forge storage is scoped to the installation. Work items the app created are ordinary Jira work items and are not affected — they remain yours.
Forge storage follows your Atlassian cloud instance's data residency. The vendor cannot choose or change where it is held.
Questions about this policy, or a request to remove data: support@maxpetrov.pp.ua
Last updated: 6 September 2026.