Processing locations
StatusDeck processes Jira data in the browser, in temporary Forge runtime memory and in Atlassian-hosted Forge storage. QTI Labs does not operate an external backend or customer-data database for StatusDeck.
Retention table
| Data | Location | Retention | Deletion |
|---|---|---|---|
| Selected project, board and sprint | Browser memory | Active page/session | Refresh or close page |
| Active-sprint report cache | Forge KVS | Up to 5 minutes | Deleted when expired entry is read |
| Closed-sprint report cache | Forge KVS | Up to 1 hour | Deleted when expired entry is read |
| Outlook / similar cache | Forge KVS | Generally up to 5 minutes | Deleted when expired entry is read |
| Manually edited commentary | Browser memory | Active page/session | Refresh or close page |
| PowerPoint and PDF exports | User device | Customer-controlled | Customer deletes file |
| Usage counters | Forge KVS | While required for fair-use enforcement and app operation | Overwritten as windows reset; removed through cleanup, uninstall or Atlassian-supported processes |
| Operational logs | Forge logging | According to Atlassian platform retention | Atlassian expiry and supported processes |
| Licence information | Atlassian Marketplace / Forge | As required for subscription administration | Marketplace and Atlassian processes |
Usage-record growth
StatusDeck maintains one small usage record per user, keyed as usage:<userId>. The same record is updated as hourly and daily windows change. Repeated report generation by the same user does not create an unlimited sequence of new records.
Deletion requests
Customers may request deletion assistance through support@qtilabs.com. Jira content remains primarily controlled by the customer's Jira administrator. QTI Labs will act on Forge-hosted data subject to technical feasibility, Atlassian platform capabilities and legal obligations.