Privacy policy – Migration Doctor for Jira Cloud
Effective date: 11 October 2026.
This policy explains what the Migration Doctor app ("the app") for Atlassian Jira Cloud and its companion snapshot script, published by Nox Development ("we"), do with data.
Summary
The app runs entirely on Atlassian's Forge platform. Everything it stores stays in your Atlassian site's app storage, and it sends nothing to us or to any third party. We cannot see your data. The snapshot script runs on your own computer and sends nothing anywhere.
The snapshot
The snapshot is a JSON file you create with the snapshot script from your Jira Data Center. It contains configuration: projects, fields, statuses, groups, filters (name, JQL, owner username, sharing), dashboards (name, owner, sharing, gadgets), workflows (transitions and rule types), permission schemes, and the list of Data Center users with username, user key, display name, e-mail address and active flag. It contains no issues, comments, attachments or passwords.
The file stays on your computer until you upload it to your own Jira Cloud site. The upload goes directly to the app's storage in your site.
Data the app stores in your site
| Data | Purpose |
|---|---|
| The uploaded snapshot | Comparison with your Cloud configuration |
| Cloud configuration read for a check run (projects, fields, statuses, groups, filters with JQL, owner account ID and owner display name, dashboards with owner account ID, workflows, permission schemes) | Comparison and repairs; only the newest completed run of a snapshot keeps it, older and failed runs lose it |
| The Cloud user list (account ID, display name, e-mail where visible) read during a run | Matching Data Center users to Cloud accounts; deleted as soon as the run's comparison finishes, or when the run fails or stops |
| E-mail to account ID matches and your corrections | User mapping for checks and repairs |
| Findings, "mark as OK" flags and who set them | The report |
| The change log: each repair with before and after, and the account ID of the admin who approved it | Audit of changes |
Where the data lives and for how long
- In Forge hosted storage (Forge SQL) of your site, which follows your site's data residency settings.
- A snapshot and everything derived from it (runs, findings, matches, corrections) are deleted 90 days after upload, or immediately when an administrator deletes the snapshot. Change log entries are deleted 90 days after the repair.
- Uninstalling the app deletes all stored data.
Personal data
- Every Atlassian account ID the app stores (in matches and corrections, findings, the stored Cloud configuration, the change log, and the record of which administrator uploaded, ran or approved something) is reported to Atlassian every week through the Forge Privacy API. When an account is closed, the app removes its account ID everywhere, together with the display name and e-mail stored next to it, or replaces it with "closed-account".
- Data Center user names and e-mail addresses in the snapshot are personal data of your organisation's users. They are stored only inside your site, used only for matching and for showing findings to your administrators, and deleted with the snapshot.
Data we receive
None from the app or the script. If you contact support by e-mail, we receive what you send us and use it only to answer your request. We keep support e-mails for up to 24 months. Please do not send snapshots by e-mail.
Your rights and contact
Data in your site belongs to your organisation and is managed by your Jira administrators. For questions about this policy, write to support@687.monster.
Data controller for support communication: Nox Development, support@687.monster.