RestorePulse for Jira ("the app") keeps snapshots of Jira issues so Jira administrators can see who deleted an issue and restore it. It is published by Ritom Puzari, trading as PuzariCloud, India ("we", "us").
| Data | Why | Where it is kept |
|---|---|---|
| Issue content: key, project, type, summary, description, status, priority, labels, components, versions, parent, links, simple custom field values, comments (as text) and attachment names/sizes | To show and recreate deleted issues | Forge SQL in your site, compressed; replaced when the issue changes |
| People inside issues: Atlassian account ids of the assignee, reporter, creator, comment authors, attachment uploaders, people in user custom fields and people @mentioned in descriptions and comments. Display names are not stored: they are looked up from Jira each time an administrator views a snapshot or restores an issue. | To restore people fields and credit comments | Inside the snapshot, as above, plus an index of which snapshots refer to which account id |
| Deletion details: account id of the person who deleted the issue, and the time | The deleted-issues log | Forge SQL in your site |
| Personal data reporting: each stored account id with the time it was first stored and last reported to Atlassian, and a one-way hash (SHA-256) of account ids Atlassian reported as closed | To meet Atlassian's personal data reporting and erasure requirements (see below) | Forge SQL in your site |
| Restore details: new issue key, time and account id of the administrator who restored it | Shows that an issue was already restored | Forge SQL / key-value storage in your site |
| Rating prompt record: the Atlassian account id of the administrator (as the storage key), how many restores that administrator has done, and the answer to the prompt (later, never, or rated) | To ask for a Marketplace rating once, after real use, and not ask again | Forge key-value storage in your site, until the app is uninstalled |
| Settings: retention days, project selection, snapshot-run progress | App configuration | Forge key-value storage in your site |
Attachment files are never copied. Error logs (Atlassian's Forge logging) contain technical messages, not issue content.
Atlassian hosts and runs the app (Forge). See Atlassian's privacy policy. No data is sent anywhere else.
The app uses Atlassian's Personal data reporting API. A daily scheduled job reports every account id the app stores to Atlassian, at most once per reporting cycle (7 days unless Atlassian asks for another period), in batches of up to 90 accounts. Atlassian answers for each account:
Account ids no snapshot refers to any more (for example after a snapshot was removed by the retention setting) are dropped from the report list.
Deleting your Atlassian account erases your personal data from the app automatically, as described above. Because the data stays in your Atlassian site and we can't access it, other requests about personal data in snapshots are handled by your Jira administrators, who can find and remove snapshots on the RestorePulse admin page. You can also contact us.
Ritom Puzari (PuzariCloud), Assam, India. Email: support@puzaricloud.in