MergeDeskIn short
Runs on Atlassian
No MergeDesk servers. Your data never leaves your Atlassian site.
We can't see your data
Request content is copied between your own requests and never stored by the app.
Account ids only
The only personal data is Atlassian account ids, removed when the undo window ends.
No tracking
No analytics, ads or cookies, in the app or on this website.
Who we are
MergeDesk for Jira Service Management is provided by Sarkhail Niyazi, trading as Findigo, India (“we”, “us”). You can reach us at support@findigo.in.
Your organization installs MergeDesk on its Atlassian site and decides how it is used. For data the app processes on that site, your organization is the controller.
Where MergeDesk runs
MergeDesk is built on Atlassian Forge and qualifies as “Runs on Atlassian”. Its code runs on Atlassian's infrastructure, its storage is Forge hosted storage on your site, and it has no permission to contact any outside server. That's why we have no way to see your requests, customers or settings.
What it stores
| Data | Why | Kept |
|---|---|---|
| Settings | The options your Jira admins choose, including any group names allowed to merge. | Until changed or uninstalled |
| Merge records | To run and undo a merge: the request keys, the steps the merge ran, the ids of comments, files, links, labels and organizations it added, any priority, assignee or due date it changed, and the account ids of the person who merged, of people it added as participants or watchers, and of assignees it changed. | Full details until the undo window ends (1–30 days, default 7), then reduced to request keys for 180 days |
| Merged-request index | Request keys, so later replies on a merged request can be forwarded. | 180 days |
| History | What was merged, when, how and the result, shown to Jira admins. | 90 days |
| Duplicate suggestions | Stored on the request itself (as an issue property) so agents see them in the Duplicates panel. | With the request |
What it doesn't do
- It doesn't store request content: comments, descriptions and files are copied from one of your requests to another, inside Jira, and nowhere else.
- It doesn't store names or email addresses.
- It doesn't send data to us or to any third party.
- It doesn't use AI services, analytics or advertising.
Personal data
The only personal data MergeDesk stores is Atlassian account ids, kept in merge records so a merge can be undone and in the history. As Atlassian requires, the app reports these ids to Atlassian every week and erases any that belong to closed accounts.
To access, correct or delete data the app holds about you, contact your Jira admin, who controls the site. You can also write to us and we'll help them.
Data residency: Forge hosted storage follows your site's data residency settings.
How long data is kept
- Merge records: full details until the undo window ends; then account ids and step details are deleted and only request keys remain, for 180 days.
- History: 90 days.
- After uninstalling: Atlassian deletes the app's stored data under its Forge data retention policy. Content already merged into your requests stays, as it's part of your Jira data.
Sub-processors
None. Apart from Atlassian, which runs the Forge platform, no one processes data for MergeDesk.
This website
mergedesk.findigo.in uses no cookies, analytics or third-party scripts. If you pick light or dark mode, that choice is saved in your own browser and never sent anywhere. The site is hosted on GitHub Pages, which may log visitors' IP addresses for security, as described in GitHub's privacy statement.
If you email us, we use your message and address only to answer you.
Changes
If we change what MergeDesk stores, we'll update this page and the date at the top before releasing the change.
Contact
Questions about privacy or security: support@findigo.in.