Junban Desk privacy policy
Effective date: 4 July 2026
This policy describes how the Marketplace (Forge) edition of Junban Desk 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.
Using the Cloud edition (app.junbandesk.com)? It is hosted outside Atlassian and its data handling differs from what is described here. See its own policy at app.junbandesk.com/privacy.
Summary
- Junban Desk stores no data outside your Atlassian site. The only data it persists is per-project configuration, kept in the app’s isolated Forge storage on your own site.
- Junban Desk makes no external network calls — it talks only to the Jira REST API inside Atlassian’s Forge platform.
- Every request runs as the logged-in user, so Jira’s permission model always applies.
What data the app processes
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:
- Issue data: summaries, descriptions, statuses, timestamps
- Comment threads, including internal agent notes
- User display names and account IDs (reporters, assignees, assignable users)
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.
When a project administrator saves settings on the app’s settings page (a custom queue JQL and feature toggles), the app writes that configuration to its own Forge storage (see below).
What data the app stores
Only per-project settings. When a project administrator saves settings (custom queue JQL, security-level selector toggle), Junban Desk stores them in its own isolated Forge KVS store, scoped to the app and to your Atlassian site — not readable by other apps or users, and never sent anywhere external. The app has no external database, no analytics, and no tracking. Jira issue and comment data 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.
Where data goes
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.
Personal data rights (GDPR and similar)
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.
Contact
Questions about this policy: support@confluenceservice-dev.atlassian.net or via our support portal.
Changes
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.