Draft. This app is not yet available.

Privacy Policy: MergeSafe – Merge & Undo Duplicate Tickets for JSM

Last updated: October 21, 2026 Provider: YuvGev, Israel ("we", "us") Contact: [email protected] (privacy and support)

1. What this policy covers

How MergeSafe (the "App"), an Atlassian Forge app for Jira Service Management and Jira Cloud, handles data, plus the limited data we receive when you email support.

The App runs entirely on Atlassian's Forge platform inside your Jira Cloud site. We operate no servers, databases, analytics, AI or third-party services for the App, and the App makes no network calls outside Atlassian (no web triggers, no remotes).

2. What a merge writes to your Jira site

When an authorized user merges a source ticket into a target ticket, the App writes normal Jira data: internal copies of the source's comments (with an "Originally by" header), the source description as one internal comment, copies of attachments under the size cap, the source requester and participants added to the target, a "duplicates" link (and, if enabled, other links, watchers and labels), and a closing transition plus one "merged into" note on the source (internal unless the project makes it public). These copies live in Jira, not in App storage.

3. Data the App stores

In Atlassian Forge hosted storage, per installed site: - Snapshots of the source and the target, taken for each merge: summary, description (capped at 8,000 characters), status, participant account IDs, watcher account IDs and labels. Snapshots don't contain attachment bytes or lists, comment bodies or email addresses. - Undo plans: the IDs of comments and attachments the merge created, and the participant IDs, watcher IDs and labels it added, so undo can remove exactly those. - Audit log entries: who merged which ticket into which, when, step results and the undo state, including the Atlassian account ID of the user. - Settings: per-project merge options (what to copy, attachment size cap, closure status and resolution, whether the closing note is public, who can merge, duplicate lookback).

Duplicate suggestions are stored in an issue property on the new ticket (merge-suggestions, in Jira): the keys and similarity scores of up to 8 similar tickets.

Diagnostic logs contain event names, counts, status and codes only, no ticket text or personal data.

4. Where the data is stored

Only in Forge hosted storage on Atlassian infrastructure, in your Jira site's data residency location (Forge data residency). We don't copy, export or download it, and use no sub-processors for it. Atlassian processes it under its own terms and privacy policy.

5. Why the data is processed

Only to provide the App's function: previewing, running and undoing merges, suggesting duplicates and keeping an audit trail. No advertising, profiling, analytics or AI training; we don't sell or share data. Your organization decides what is processed.

6. Who can access the data

• Jira site administrators: the Merge audit page (audit search and Clear history).
• Project administrators: the project's Merge settings.
• Users allowed to merge (by default anyone with Edit issues or Administer projects; a project can restrict it to project admins): preview, merge and undo in that project.
• Us: no back door, admin console or remote access. In support we see only what you send us.

7. How long the data is kept

• Snapshots and undo plans: 30 days after each merge (the undo window), then deleted by a daily job. After that the merge can't be undone.
• Audit log: 90 days, then deleted automatically. The audit search shows at most 100 entries per project and for the site.
• After uninstall: the App can no longer read its data. Atlassian soft-deletes Forge hosted storage and keeps it 28 days; reinstalling doesn't restore it (Forge storage overview). Comments, attachments and links the App created in Jira stay in Jira.
• Support emails: as long as needed to resolve the request and up to 24 months after, unless you ask us to delete them sooner.

8. Your choices and rights

• A Jira administrator can use Clear history on the Merge audit page. It deletes every audit entry and the undo plans of merges that are finished or older than 30 days. Snapshots of merges still inside the 30-day window are kept and auto-delete when it ends. Merges in progress are kept. Finished merges can't be undone after Clear history.
• Uninstalling removes everything the App stores.
• End users of a customer's site should contact that organization; we'll help them.

• Otherwise email [email protected]. We reply within 5 business days.

9. Security

Scopes approved at install: - read:jira-work: read tickets, comments, attachments, links and transitions, and search for duplicates. - write:jira-work: add internal comments, upload attachments, add and delete links, transition the source, and delete the App's own comments and files on undo. - read:jira-user: show display names in the "Originally by" header and the audit log. - storage:app: store snapshots, undo plans, the audit log and settings in Forge storage. - read:servicedesk-request: list a request's participants, so undo removes only people the merge added. - write:servicedesk-request: add and remove request participants.

We never ask for passwords, API tokens or personal access tokens. Stored data is protected by Forge platform controls (Atlassian Trust Center).

10. Data we receive directly (support)

Your name, email address and whatever you include. Used only to answer you. Mail sent to our addresses is received through Cloudflare Email Routing (which forwards it without storing it) and is stored in Google Gmail.

11. Children

Business tool, not directed at children.

12. Changes

We update the "Last updated" date on change; material changes are noted in Marketplace release notes.

13. Contact

YuvGev, Israel. [email protected]