Effective date: 4 July 2026
This policy describes how Junban Desk (the app) handles data. Junban Desk is published on the Atlassian Marketplace by Collaboration Services (“we”, “us”). It applies to the app only; your use of Jira itself is governed by Atlassian’s privacy policy.
To render the queue workspace, the app reads the following from your Jira site, in-flight only, at the moment a user loads or acts on the page:
When an agent replies, adds an internal note, transitions, or assigns a ticket, the app writes that change to Jira through the Jira REST API — exactly as if the agent had done it in Jira directly.
None. The app runs entirely on Atlassian’s Forge platform and has no database, no external storage, and no analytics or tracking. Data read from Jira is processed in memory to answer the request that asked for it and is not retained afterwards.
The app’s frontend keeps three small UI preferences (selected filter, selected ticket key, and pane-divider position) in your browser’s local storage on your own device. These never leave your browser.
Nowhere outside Atlassian. The app declares no external egress in its Forge manifest, which Atlassian enforces at the platform level: the app is technically incapable of sending data to non-Atlassian hosts.
Because the app persists no personal data, there is nothing held by us to report or erase. Requests concerning personal data in your Jira site (issue content, comments, profiles) are handled by your Jira administrators and Atlassian’s own data-subject tooling.
Questions about this policy: support@confluenceservice-dev.atlassian.net or via our support portal.
We will update this page if the app’s data handling ever changes (for example, if a future version adds storage). Material changes will be noted in the app’s changelog.