Privacy Policy — Undelete for Jira
Last updated: 22 October 2026 · Regulation (EU) 2016/679 (GDPR)
The short version
Undelete for Jira runs entirely inside Atlassian. It is a native Forge app that declares no external network permission — permissions.external.fetch is absent from its manifest.yml — so the Atlassian platform itself prevents it from sending anything anywhere. We do not operate a server, a database or analytics for this app.
To be able to bring a deleted work item back, the app keeps a copy of your work items inside your own Atlassian site, in Forge storage. That copy never leaves Atlassian and never reaches us.
Who we are
Pieran Lab di Erik Pieran — sole trader, Italy
Via Bruno Mion 100, 30038 Spinea (VE), Italy
VAT / Tax code: IT04915430278 · REA: VE-463627
Email: support@pieranlab.cloud
Why the app keeps a copy
When a work item is deleted, Jira tells apps only a handful of its fields, and the item can no longer be read: the description, the assignee, the labels and the comments are gone. So the app keeps an up-to-date copy of each work item from the moment it is created or changed, and moves that copy to the bin when the item is deleted. Work items that have not changed since the app was installed are not copied until they change; if one of them is deleted, the bin keeps only the basic fields Jira provides, and says so.
What the app reads
- A work item, when Jira reports that it was created or updated (
GET /rest/api/3/issue/{id}). This read uses the app's identity because it is triggered by a Jira event, not by a person. - A comment, as Jira sends it with the comment event.
- Whether the person using the admin page holds Administer Jira (
POST /rest/api/3/permissions/check), as that person. - Display names of the people shown in the bin (
GET /rest/api/3/user/bulk), as that person: read each time the page opens, never stored.
What the app stores
- Copies of work items: summary, description, type, space, priority, labels, components, versions, due date, parent, environment, status, dates, the names and sizes of attachments (not the files), the values of custom fields, and the account ids of the assignee and reporter.
- Comments: their text, date and the account id of the author.
- Bin entries: the copy above, when it was deleted and the account id of who deleted it.
No names and no e-mail addresses of Atlassian accounts are stored. People are kept as account ids, and the names in a mention (@Name) are removed before saving: Jira draws the current name again from the id.
Be aware: the content of a work item is copied as it was written. If someone typed personal data into a description or a comment, the copy contains it too, exactly like a backup would. It stays inside your Atlassian site.
- Retention: copies of live work items are kept and updated while the app is installed. Bin entries are kept for 90 days by default; a Jira administrator can choose between 7 and 365 days, and a daily job removes older entries.
- Deletion: a Jira administrator can remove any bin entry at any time from the app. That works even if the subscription is not active.
- On uninstall: Atlassian keeps the app's storage for that installation for 28 days, so that it can be restored if the app is reinstalled, and then deletes it.
What the app does not do
- It does not send data to us or to anyone else. It cannot: the app has no egress permission.
- It does not store attachment files, only their names.
- It does not use cookies, trackers or analytics, and it has no sub-processors.
- It never asks for an API token, a password, or an account with us.
Where the data lives
In your Atlassian site and in Atlassian's Forge platform, under Atlassian's own data residency arrangements. We do not choose or control that location, and we never hold a copy.
Your rights under the GDPR
Because we never receive your data, requests are satisfied inside the app: the bin shows what is stored for deleted items and removes it on demand, and uninstalling the app removes everything after Atlassian's 28 days. For written confirmation, write to support@pieranlab.cloud.
Roles: for the personal data in your Jira site you, the customer, are the controller. We do not act as a processor in the usual sense, because no data reaches us: the processing happens inside your own Atlassian tenancy, under Atlassian's terms.
See also
The security statement and the support page.
Changes
This policy is versioned with the app. The date at the top changes when the content does.