Queue TidyPrivacy policy
This policy explains what data Queue Tidy ("the app") processes, why, and where it is kept. The app is provided by [Company legal name], [Registered address] ("we", "us").
1. Summary
- The app runs entirely on Atlassian's Forge platform. Your data stays inside Atlassian's cloud.
- We do not send your data to our own servers or to any third party.
- We do not sell data, use it for advertising, or use it to train AI models.
- We (the people at [Company legal name]) cannot see your Jira data unless you share it with us, for example in a support request.
2. Who is responsible
For the Jira data the app processes, your organization is the data controller and Atlassian hosts the app. We act as the app's provider. For data you send us directly (such as support emails), [Company legal name] is the controller.
3. What the app processes and why
| Data | Why the app uses it |
|---|---|
| Ticket keys, summaries, descriptions and comments in projects where the app is used | To find likely duplicates and copy the conversation when tickets are merged |
| Attachments on merged tickets | To copy them to the ticket that stays open |
| Account IDs and display names of reporters, participants and agents | To match requests from the same customer, add customers to the open ticket, and show who merged what |
| How a request arrived (email, portal, API) | To check only the channels you choose |
| Your app settings | To apply your choices per project |
The app processes this data only when it is needed for these purposes, and only in projects where Jira Service Management is used.
4. What the app stores
Inside Atlassian's Forge storage, per project:
- Settings you choose on the settings page.
- Suggestions waiting for review: the two ticket keys and summaries, the customer's display name, the match score and when it was found.
- Merge history: the two ticket keys and summaries, the customer's and agent's display names, how the merge happened, and counts of comments, files and people moved.
- Counters for the Duplicates page, for example the number of merges.
On the tickets themselves, as Jira issue properties: a record of which ticket a duplicate was merged into, when and by whom.
The app also writes notes, labels, links and customer replies into tickets as part of a merge. These become normal Jira content and follow your Jira retention, not this app's.
5. Logs
The app's operational logs, kept by Atlassian, contain ticket keys, the action taken and error messages, so we can investigate problems you report. They do not contain ticket text or customer contact details.
6. Sharing
The app does not share data with anyone. Atlassian hosts and runs the app under its own terms and privacy policy. We access app logs only to provide support and fix problems.
7. Retention and deletion
Stored data is kept while the app is installed. When you uninstall the app, Atlassian deletes its stored data according to its Forge data deletion process. To ask for earlier deletion, contact support@queuetidy.com.
8. Security
- Atlassian encrypts app data in transit and at rest.
- Before the app acts for an agent, it checks that the agent's own Jira permissions allow it.
- Only project administrators can change the app's settings.
- The app makes no connections outside Atlassian.
9. Your rights
Because your Jira data stays in your Atlassian site, most requests (access, correction, deletion) are handled by your Jira administrator or by Atlassian. For anything the app stores, contact us at support@queuetidy.com and we will help within 30 days.
10. This website
queuetidy.com uses no cookies, analytics or tracking. It loads fonts from Google Fonts, which receives your browser's IP address under Google's privacy policy.
11. Changes
If we change how the app handles data, for example by adding a new feature, we will update this policy and its effective date before the change is released.
12. Contact
[Company legal name], [Registered address]. Email: support@queuetidy.com. Security issues: security@queuetidy.com.