Zenthas

Privacy Policy, Ticket Merge (working name)

Version: 2026-10-24


1. Who is responsible

Operator of the app: Zenthas, Tien Duy Vo, Alter Schulpfad 6, 65934 Frankfurt am Main, Germany. Contact for privacy questions: support@zenthas.com. You (the customer, owner of the Jira site) are the controller of the data in your Jira site. The app processes this data on your behalf, only to perform the actions you start.

2. What the app is

Ticket Merge is an Atlassian Forge app. It adds the action "Merge into another ticket" to Jira issues. It runs on Atlassian's Forge platform. The code contains no call to any server outside Atlassian: all requests go to the Jira REST API of your own site.

3. What data the app reads

When an agent opens the merge dialog or starts a merge, the app reads from your Jira site, using the agent's permissions (preview) or the app's own account (background work):

  • ticket key, title, status, project, reporter (account ID, display name);
  • comments of the source and target ticket (text, author display name, date, internal/public flag);
  • attachments (file name, size, type, and the file content while copying);
  • issue links;
  • for Jira Service Management requests: the request's participants (account IDs). Not yet tested on a Jira Service Management site.
  • the account ID of the agent who started the merge, and the agent's permissions on both tickets. The preview shown to the agent contains only counts, warnings and the step types, no ticket content.

4. What the app writes

In your Jira site, as part of a merge: copies of comments (with a header line showing source key, author name and date), copies of attachments, issue links, a note comment on the target and, for service requests, a note for the customer and added participants; a "Duplicate" link; a transition that closes the source ticket. Undo removes the copies and reopens the source ticket. These contents belong to your Jira site and follow your retention rules there.

5. What the app stores

In Forge storage (key-value store) of your installation, one record per merge ("job"):

  • job ID, source and target ticket keys, account ID of the agent, language (en/de), options, timestamps, status, undo deadline;
  • per step: type, ID of the source comment/attachment/link, ID of the created copy, link type and direction and the other ticket's key, for added participants their account IDs, the ticket's status name before and after closing, attempt count, and short error text (HTTP status and message) if a step failed. Not stored: comment texts, ticket titles, attachment files or file names, customer names or email addresses. Personal data: the stored account IDs (agent, added participants) are personal data, so the app answers 'stores personal data: yes' in the Marketplace and the Developer Console. The display name of the person who ran a merge is read from Jira only to show it in the history (scope read:jira-user) and is not stored. Attachment files pass through the memory of the running function while they are copied and are not kept. Queue events (Forge queue) carry the job ID, ticket keys, agent's account ID and language until processed. Forge platform logs: the app logs only step IDs and error text of failed steps (no ticket content). Retention of Forge platform logs is set by Atlassian.

6. How long

Merge records are kept for 30 days after the merge (the undo period). A daily job removes expired records. The job runs once a day, so deletion can happen up to about a day after the 30 days. Copies made in your tickets stay there until you or the app (undo) delete them. When the app is uninstalled, Forge removes the app's stored data.

7. Who gets the data

  • No third party, no analytics, no tracking, no advertising, no AI model. No data leaves Atlassian's Forge platform.
  • Atlassian hosts and runs the app (Forge) and the Jira site. Atlassian's own terms and privacy policy apply to that.
  • Licensing and billing: the Atlassian Marketplace gives the operator licence information (customer site, contact, number of users, licence state). The operator uses it only to manage the licence and support.
  • Support: if you write to the support address, we process your email and what you send. Please do not send customer data or passwords.

8. Where

Forge storage and functions run in Atlassian's regions. The data residency options of your Atlassian product apply to the storage.

9. Permissions the app requests, and why

read:jira-work (read tickets, comments, attachments, links); read:jira-user (read display names of users for the merge history); write:jira-work (create copies, links, transitions; undo deletes what the app created); read:servicedesk-request and write:servicedesk-request (read and add request participants); storage:app (store the merge records). Undo and background steps run under the app's account, and the app deletes only items it created itself (recorded IDs). Whether this works in service projects with restricted permissions is not tested.

10. Legal basis (EU/EEA)

As processor on your instructions (the actions your agents start); the legal basis for the controller (you) is yours to determine. For support emails and licence administration: our legitimate interest in answering requests and managing licences (Art. 6(1)(f) GDPR) and, where applicable, performance of a contract (Art. 6(1)(b)). Data processing agreement (DPA): on request to support@zenthas.com we sign a data processing agreement with you as controller; it covers the processing described in sections 3 to 7. California: we do not sell or share personal information and use it only to provide the app to you. We are a small operator based in Germany and do not expect the CCPA to apply to us; if it does, we act as your service provider.

11. Your rights

You can request information, correction, deletion and restriction of your data and object to processing. Because the merge records contain only IDs and keys in your own Forge storage, deletion happens by itself after 30 days or on uninstall. Contact: support@zenthas.com. You may also complain to your data protection authority.

12. Changes

We update this page when the code changes the data handling. Version and date are at the top.