Your data, and uninstalling
On this page
The app records nothing about the people who use it. It keeps templates and numbers. It never records who made, changed, used, restored or deleted a template, or anyone's account ID. A template holds whatever your administrators type into it or copy from an issue, so it holds personal data only if someone puts it there. See Save as template for what is taken out of a copied description.
| What | Where, and for how long |
|---|---|
| Templates | Forge storage, Atlassian's storage for the app on your site. Until deleted, then 30 days in Recently deleted. |
| Versions: the template as saved, the date and time, and what changed | Forge storage. The last 50 per template, removed with the template. |
| Usage counts, and the time of the last use | Forge storage. While the template exists, and 30 days after it is deleted. |
| For the whole site: how many times a template was used from a Templates page, and the date of the first | Forge storage. Until the app is uninstalled. |
| Whether an administrator chose Hide these steps on Get started, and when: once for the Jira settings page and once per project | Forge storage. Until the app is uninstalled. |
| Your answer to the rating ask: Rate it, or how many Not nows and when | Your browser’s storage for the Templates page, written only when you click. It never leaves your browser. |
| The daily check's settings, the problems it found last time, its last 20 checks that found something, and when the banner was dismissed | Forge storage. The settings stay until you change them, and the dismiss time until the next Dismiss. The problems found last time are replaced at each complete check, and the list of checks keeps the last 20. |
| Runs, while a template's child work items are added: a copy of the work items to create, the key of the work item they go under, the keys and summaries of those created, and Jira's message if it refused one. No account IDs | Forge storage. Removed by the daily check 30 days after the run last changed. |
| Create dialog settings: a copy of each default template, one record per project that has any | In Jira, through its UI modifications feature. Only the app can read or change them. Removed when a project has no default templates left. |
| Alert issues | Your Jira project. Ordinary issues, yours to keep or delete. |
| Error log lines: when Jira rejects a change the app made in the Create dialog, only the kind of error and the field's id; when saving a version, the daily check or clearing expired deleted templates fails, a short error message | The app's log on Atlassian's platform. No account IDs, and nothing from the form. |
| While a Create dialog opened from the gallery is open: the picked template's summary and description text, and the time it was picked | The person's browser, in that tab only. Removed when the dialog closes or the tab is closed, and replaced by the next pick. If Jira does not report the dialog closing, it stays in that tab and is ignored after two hours. It holds template text, not what people type. |
Not kept anywhere:
- Who created, edited, restored, deleted or used a template. The app adds no account IDs, names or email addresses of its own. A template holds them only if someone types them in or copies them from an issue. From a copied formatted description, Save as template removes @mentions, attachments, other apps' content, profile and email links, and email addresses. A name written as ordinary words stays (see Save as template).
- What people type in the Create dialog. The app looks at the summary and description in the browser only to decide whether to add the line naming the default.
- Which issue a template was saved from. Its key is not kept, only what you chose to copy into the template. The keys of issues created from the gallery are not kept either.
Nothing is sent outside Atlassian. The app declares no outside connections, and every request it makes goes to your own Jira site or to the app's own functions on Atlassian's platform.
Data residency
In scope: everything the app keeps in Forge storage. That is templates, their versions, deleted templates, usage counts, and the daily check's settings and findings.
Out of scope: the Create dialog settings, which Jira stores through its UI modifications feature, and alert issues, which are ordinary issues in your Jira project. Neither is kept in the app's storage. Nor are the error log lines, or the picked template's text that the gallery keeps in the person's browser tab while its Create dialog is open. Both are listed in the table above.
Uninstalling
Once the app is uninstalled, the Create dialog no longer names a default, and its pages, the gallery and the daily check are gone. Alert issues stay, because they are ordinary issues in your project.
The app has no step of its own that erases data when it is uninstalled. Its Forge storage belongs to its installation on your site, and what happens to it afterwards follows Atlassian's rules for Forge apps.
To take the Create dialog settings out of Jira before you uninstall, clear Default for these issue types on every template, or delete the templates. The app removes a project's record as soon as the project has no default templates.
More in our privacy policy.
Licensing
Without an active license, for example after a subscription ends:
- Templates cannot be saved, restored, or made from an issue.
- The gallery shows This app needs an active license.
- The Create dialog names no default template.
- The daily check does not run on its schedule.
Your templates are kept. The admin and project pages still open, with a warning, so you can see your templates and their history, delete them, and run the health check.