Processing locations
StatusDeck processes authorised Jira/Confluence information in the browser, temporary Atlassian Forge runtime memory, Atlassian-hosted Forge KVS and—only when the user publishes—inside the customer’s selected Confluence space/page. QTI Labs does not operate a separate StatusDeck customer-data backend or database.
Processing and retention table
| Data | Location | Retention | Deletion/expiry |
|---|---|---|---|
| Selected project, board, Sprint and report context | Browser / active Forge request | Active interaction | Refresh/close or request completion |
| Active-Sprint report cache | Forge KVS | Up to 5 minutes | Expired entries are deleted when next read; oversized results may skip caching |
| Closed-Sprint report cache | Forge KVS | Up to 1 hour | Expired entries are deleted when next read |
| Velocity/outlook and similar short-lived caches | Forge KVS | Short-lived; typically minutes based on operation | Expired entries are deleted when next read |
| Reporting settings | Forge KVS | Until changed/reset, installation cleanup or supported deletion process | Overwritten when settings are saved; deletion assistance available |
| Management Commentary draft/published overlay | Forge KVS | Until changed/reset, installation cleanup or supported deletion process | Updated by Save Draft/Publish/Restore workflows and supported deletion processes |
| Reporting Scheduler configuration | Forge KVS | Until changed/disabled, installation cleanup or supported deletion process | Updated when schedule is saved/changed |
| Last successful Confluence publication metadata | Forge KVS | Until replaced/cleanup | Replaced by later publication for the same reporting context or supported deletion process |
| Downloaded PowerPoint/PDF | User device | Customer controlled | Customer deletes the file |
| Confluence report content and attachments | Customer Confluence | Customer/Atlassian controlled | Customer manages page/attachment versions and deletion in Confluence |
| Usage counters | Forge KVS | Operational; hour/day counters are reused | Same per-user record is overwritten as windows reset |
| Operational logs | Forge logging | According to Atlassian platform retention | Atlassian platform processes |
| Licence information | Atlassian Marketplace / Forge | Subscription administration | Atlassian Marketplace processes |
Confluence publishing
When a user explicitly publishes, StatusDeck sends the generated report content and files to the selected Confluence destination using Atlassian APIs and the current user context. QTI Labs does not receive a separate copy of the published report.
Deletion requests
Customers may request deletion assistance through support@qtilabs.com. Jira and Confluence content remains primarily controlled by the customer’s Atlassian administrators. Forge-hosted data deletion is subject to Atlassian platform capabilities and applicable legal obligations.