Project Lead & Scheme Switcher for Jira privacy
This section describes how Project Lead & Scheme Switcher for Jira handles data. It supplements the site-wide privacy policy.
Where the application runs
The application is an Atlassian Forge application. Its interface and functions run on infrastructure operated by Atlassian, and it stores data only in Atlassian-hosted storage for your own installation. Atesen Software operates no server and no database for it.
What it talks to
Your own Jira site, plus Atlassian's Personal Data Reporting service for the account ids it keeps. The application requests no permission to send data outside Atlassian. It contains no analytics and no third-party code.
What it stores
- The last 20 runs: for each project its id, key and name; the old and new permission, notification and issue security scheme and project category (ids and names); the Atlassian account id of old and new leads; the outcome per project; and the account id of the admin who ran it.
- For Atlassian's Privacy API: an index of the account ids that have appeared in a run, each with the date of its oldest stored copy, and for accounts Atlassian reported as updated, the time the application retrieved the account again. These records hold account ids and times only.
- It does not store email addresses or the display names of users.
How long it is kept
There is no timer. A preview that was never confirmed is deleted the next time anyone on the site starts a preview, once it is more than 24 hours old. When there are more than 20 runs, older unconfirmed previews are removed first, then the oldest finished runs; a run that is still being applied is kept for at least 7 days, and a run whose undo is in progress is kept.
Account ids stay in the index after their runs are removed and are reported weekly through Atlassian's Privacy API. When Atlassian marks an account closed, every run that references it is deleted with its undo data, and the account id is removed from the index and no longer reported. When Atlassian marks an account updated, the runs are kept, because a profile change does not change the account id; the application records the time it retrieved the account again and reports that time from then on.
When the application is uninstalled, Atlassian deletes its stored data for your site.
Data residency
The application uses Atlassian-hosted storage, which follows the residency of your Jira site.