Matify/Config Undo for Jira

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

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

8. Deletion

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

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).