Data Retention and Deletion Policy
Effective date: 13 May 2026 Last updated: 13 May 2026
This page describes how the Wheel of Fortune for Jira app (“the App”) retains and deletes customer data. It complements our Privacy Policy.
1. Data categories
The App stores only the data needed to operate its randomization feature. All data is held in Atlassian Forge App Storage (storage:app), which is hosted on Atlassian Cloud and scoped to the customer’s Jira instance.
| Data | Source | Storage location | Purpose |
|---|---|---|---|
| Lineup configuration (name, description, participants) | Administrator input | Forge App Storage | Persist the wheel between sessions |
| Selection history and “already chosen” list | App runtime | Forge App Storage | Display previous results and avoid duplicate picks |
| Timestamp of last spin | App runtime | Forge App Storage | Display the last-spin time |
| Custom-object entries | Administrator input | Forge App Storage | Free-text alternatives to Jira users |
| Jira directory fields (accountId, displayName, avatarUrls, emailAddress, active, accountType) | Atlassian Jira REST API | Read on demand, not persisted in App Storage beyond the accountId references in a lineup |
Render the user picker |
2. Retention while installed
- App configuration is retained for as long as the App is installed on the Jira instance.
- An administrator can edit or clear the lineup at any time from the App’s UI; doing so overwrites or removes the corresponding entries in App Storage immediately.
- The App keeps no historical revisions, backups, or audit trails outside of Atlassian’s own platform logging.
3. Retention after uninstall
When the App is uninstalled from a Jira instance, the Atlassian Forge platform automatically deletes all data stored under that installation’s storage:app namespace. We do not retain any copy of customer data because no data ever leaves Atlassian’s infrastructure.
There is no separate “manual deletion” step required from the customer; uninstalling the App is sufficient.
4. Customer-initiated deletion
Administrators have two ways to delete data without uninstalling:
- In-app edit / delete — open the App, modify or remove the lineup; changes are persisted immediately.
- Reset by re-installation — uninstalling and re-installing the App produces a fresh, empty configuration.
End users who appear in a lineup should contact their Jira administrator to be removed. We do not have a separate back-channel mechanism, because all data is controlled by the customer’s Forge installation.
5. Data-subject requests
If a person exercises a right of erasure under GDPR, CCPA, UK GDPR, or a similar law:
- The Jira administrator can satisfy the request directly by removing the user from any saved lineup or uninstalling the App.
- If administrator-side assistance is required, email support@florenco.tech and we will respond on a best-effort basis, ordinarily within 30 days.
6. Backups
We operate no off-platform backups. The Forge platform manages its own redundancy as part of Atlassian’s Cloud service; that is the only redundancy in scope for the App.
7. Logs and telemetry
The App does not emit custom telemetry, analytics events, or remote logs. The Forge runtime may capture short-lived diagnostic logs as part of Atlassian’s platform operations; those are managed and retained by Atlassian, not by the Partner.
8. Changes to this Policy
Material changes will be reflected in the “Last updated” date above. Continued use of the App after the effective date constitutes acceptance.
9. Contact
Data retention or deletion questions: support@florenco.tech.