Native Issue Templates for Jira, operated by ResiliaTech. Last updated 1 October 2026.
Native Issue Templates for Jira ("the app") is an app for Atlassian Jira Cloud. This policy explains what the app processes, where that data lives, and what we, ResiliaTech, can and cannot see.
In short: the app runs entirely on Atlassian's Forge platform, inside your Atlassian site. It stores only your templates and their history. It stores no issue content and no personal data, sends no data to ResiliaTech's servers or to any third party, and we cannot browse your templates or issues.
Who we are
ResiliaTech (Resilia Tech (Private) Limited), 14885 Pleasant Valley Road, Tynwald South, Harare, Zimbabwe. Contact: support@resiliatech.com.
For the data described below, your organisation, the Atlassian customer, is the controller. ResiliaTech provides the app, which processes the data on your organisation's behalf.
Data the app works with
Jira data read through Atlassian's APIs. When a template is applied, the app reads the issue: its key, summary, description, labels, priority, components, issue type, project, the reporter's display name and the summaries of its sub-tasks. It also reads the lists of projects, issue types, priorities and project components. From the issue view this runs as the signed-in user, so the app only sees what that user can already see in Jira. Auto-apply on create runs as the app.
Changes the app writes to Jira. Applying a template updates the issue's description, summary, labels, priority and components, and creates sub-tasks. These are ordinary Jira data.
The app's own records, kept in Atlassian Forge storage for your site:
templates: name, summary pattern, description text, labels, priority, component names, sub-task summaries, the issue types and projects they apply to, a version number and the times they were created and last saved;
the last 5 previous versions of each template.
No personal data. The app stores no Atlassian account IDs, names or email addresses, and does not record who saved a template. The {{reporter}} variable inserts the reporter's display name into the issue when a template is applied; the name is written to that issue in Jira and is not kept by the app. Template text is free text, so it contains whatever your admins type into it.
The app has no advertising, and no analytics or tracking of any kind.
Where the data is stored
Issues, and everything a template adds to them, stay in your Jira site as normal Jira data.
Templates and their history are kept in Atlassian Forge storage, which Atlassian hosts and isolates per site, under Atlassian's terms and privacy policy. Data residency follows Atlassian's Forge data residency rules for your site.
The app makes no calls to servers outside Atlassian ("no egress"). It is eligible for Atlassian's Runs on Atlassian programme.
What ResiliaTech can see
We cannot browse your site's issues or templates. Atlassian gives us operational logs and metrics for the app, such as error messages and how often features are used. These can contain technical identifiers, for example an issue key in an error. We use them only to keep the app working and to resolve support requests. If you send us information in a support request, we use it only to help you, and delete it when it is no longer needed.
Sub-processors
Atlassian, which hosts the app on its Forge platform and runs Jira. We use no other sub-processors for app data.
Retention and deletion
Content that a template added to an issue is Jira data. It stays in Jira until your users or admins change or delete it, including after the app is uninstalled.
Deleting a template also deletes its history. Older versions beyond the last 5 are deleted automatically.
Templates and their history are deleted by Atlassian after the app is uninstalled from your site, in line with Atlassian's Forge data retention policy.
Because the app stores no personal data, there is nothing for it to erase when an Atlassian account is closed.
The app runs inside Atlassian's infrastructure. It uses the minimum Jira permissions needed:
read Jira work, for issues, projects, issue types, priorities and components;
write Jira work, to update an issue's fields and create sub-tasks;
read Jira priorities, for the priority list in the template editor;
app storage, for templates and their history.
All traffic is encrypted by Atlassian.
Your rights
Because your organisation controls this data, requests to access, correct or delete personal information should go to your Jira administrator first. We will help them fulfil any request. You can also contact us at support@resiliatech.com.
Changes
If we change this policy, we will update the date above. For significant changes, we will tell customers through the Marketplace listing.