Privacy policy — Config Undo for Jira
Publisher: Matify · App: Config Undo for Jira (Atlassian Jira Cloud) · Contact: support@matifyapps.de Effective date: 7 October 2026 · Last updated: 7 October 2026
1. Who this policy covers
This policy explains how the Config Undo for Jira app handles data when a Jira Cloud site installs it from the Atlassian Marketplace. The organisation that installs the app decides what is configured in its Jira site and who administers it. Matify provides the app, which records and restores that site's Jira configuration on the instructions of the site's Jira administrators.
The app runs on Atlassian Forge. Atlassian's handling of your Jira site and of Forge hosted storage is governed by Atlassian's privacy policy.
2. Products
The app is installed into Jira Cloud and works with company-managed projects. It processes no data from other Atlassian products or other sites.
3. What the app processes
Jira configuration (read, stored as versions) Permission schemes, notification schemes, workflows, workflow schemes, screens, custom-field options, field schemes and project settings (name, description, lead, default assignee, category, scheme associations, project role actors, components, versions).
Jira audit-log records and workflow history (read, stored as journal entries) Who changed which configuration object, when, and what the audit log recorded about the change.
Personal data
- Atlassian account ids contained in configuration: users granted permissions, users receiving notifications, project leads, component leads, project role members, users named in workflow rules.
- Atlassian account ids in the app's own records: authors of configuration changes (from the audit log; change summaries can also name users added to or removed from configuration), administrators who request, approve, reject, cancel or retry restores or review changes, administrators who create restore points, the administrator who last changed the app's settings, and the actor of each ledger entry.
- Email addresses only where a Jira administrator configured an email address as a notification recipient in a notification scheme; it is stored as part of that scheme.
- Free text administrators type into the app: restore reasons, review notes, restore point labels.
Not stored Names, avatars and other profile information of people (names are looked up from Jira when a page is shown and kept only in the browser session), issues, comments, attachments, passwords, API tokens, IP addresses, device or usage analytics. The names of project roles and groups, which are not personal data, are cached by the app for display.
4. Why
Only to provide the app's functions to the installing organisation: a change history of Jira configuration, comparison of versions, restore points, restores with approval and verification, a tamper-evident ledger of restores and settings changes, change reviews and exports, and support diagnostics the administrator chooses to download.
5. Where the data is stored
Only in Forge hosted storage on Atlassian's infrastructure, separate for each installation. Matify runs no server or database of its own and has no access to the stored data.
Data residency: Forge hosted storage follows the Jira site's data residency and moves with the site. All data listed in section 3 is in scope. Forge application logs are out of scope; they contain no personal data or configuration content.
6. Sharing, egress and subprocessors
The app sends no data outside Atlassian. It has no external connections, no remote backend and no web triggers, and uses no analytics, telemetry, error-reporting or email service. The only subprocessor is Atlassian as the provider of Jira and the Forge platform. Matify does not sell or share data.
7. Retention
- Retention period: 13 months by default; the site's Jira administrators can set 3 to 36 months. A weekly job deletes data past the retention period.
- Configuration versions and journal entries are deleted once older than the retention period. Kept regardless: the latest version of every object, the version that was current at the retention boundary, versions in pinned restore points and versions of unfinished restore requests.
- Restore points are deleted once older than the retention period unless pinned. Finished restore requests are deleted with their preview and result once older than the retention period; previews that were never submitted are deleted after 24 hours.
- The restore ledger is kept for the life of the installation.
8. Deletion
- Delete all app data (Settings → Danger zone, with a typed confirmation) deletes every stored version, journal entry, restore point, restore request and ledger entry.
- Administrators can shorten retention and exclude projects or objects from recording.
- Data the app deletes is removed from its storage at once; Atlassian may keep a deleted copy for a limited time to recover from accidental deletion, under its own Forge data retention.
- Uninstall: the app records a final ledger entry. Data in Forge hosted storage is then retained and deleted per Atlassian's Forge data retention for uninstalled apps. Nothing is exported or sent to Matify on uninstall.
9. Personal data requests and closed accounts
The app uses Atlassian's personal data reporting API: every week it reports the account ids it stores. When Atlassian reports an account as closed, the app replaces that account id with a random placeholder that cannot be traced back to the account in its journal (authors, reviewers, change summaries), its restore requests with their stored preview and result, its restore points, its stored configuration versions and its settings. It recalculates the affected records, deletes the replaced copies, removes the account id from its ledger while keeping the ledger verifiable, and deletes its cached permission check for that account. Free text that administrators typed is not searched. This continues even if the subscription has lapsed.
Requests to access, correct or delete personal data held in the app should go to the organisation that administers the Jira site, which controls the app's data. Matify will help that organisation; contact support@matifyapps.de. Matify itself cannot see the data in your site.
10. Security
- Only users with the Administer Jira permission can use the app; this is checked on the server for every request.
- Restores are off by default, need a preview, a reason and (by default) a second administrator's approval, are verified afterwards and recorded in a hash-chained ledger. A site-wide kill switch blocks every write.
- Request data is validated on the server; text is displayed as text; exports are protected against spreadsheet formula injection.
- Logs contain no account ids, names, email addresses, free text or configuration content.
Details: the data security and privacy statement.
11. Changes to this policy
Material changes are published on this page with a new "last updated" date before they take effect.
12. Contact
Matify · support@matifyapps.de (privacy questions and requests; for security reports use "security" in the subject).