Matify/Config Undo for Jira

Data security and privacy statement — Config Undo for Jira

Publisher: Matify · App: Config Undo for Jira (Jira Cloud) · Contact: support@matifyapps.de · Last updated: 7 October 2026

1. Overview

Config Undo for Jira records changes to Jira configuration and lets Jira administrators restore an earlier version of a configuration object after a preview and an approval. It is an Atlassian Forge app. This statement explains, technically and plainly, what the app processes, where it keeps it, and how it is protected. The formal policy is the privacy policy.

2. Hosting and architecture

3. Data we process

The app does not read or store issues, comments or attachments.

4. Personal data

The app stores Atlassian account ids for longer than 24 hours:

It also stores free text admins type (reasons, notes, labels) and, only where an admin configured one as a notification recipient, an email address that is part of the notification scheme. It stores no display names, avatars or other profile data.

5. Data storage

All stored data is in Forge hosted storage on Atlassian's infrastructure. Configuration versions are stored once per distinct content (content-hashed, compressed); metadata (journal, versions, restore points, requests, ledger) is in Forge custom entities.

6. Tenant isolation

Forge hosted storage is partitioned per installation by the platform. The app uses no global or shared storage across customers, keeps no state between invocations outside that storage, and its logs contain no identifiers of other installations.

7. Data residency

Forge hosted storage follows the Jira site's data residency and moves with the site. All stored data listed in sections 4 and 5 is in-scope end-user data held there. Forge application logs are operational data outside that scope and contain no personal data or configuration content.

8. External data egress

None. The app declares no external domains, no remote backend and no web triggers. It calls only Jira's REST APIs and Forge platform services. Exports are generated in the admin's browser and saved locally.

9. External services and subprocessors

None besides Atlassian (hosting, storage, the Forge platform). No analytics, telemetry, error reporting, email or content delivery service is used.

10. Permissions and scopes

Six classic scopes: read:jira-work, manage:jira-configuration, manage:jira-project, read:jira-user, storage:app, report:personal-data. With the two manage scopes Jira grants the app user Jira-admin-equivalent permissions (verified: Administer Jira, Administer projects, Bulk change). Each scope is explained in Permissions and security.

11. Read/write model

12. Data retention

13. Data deletion

14. Personal data requests

The app reports the account ids it stores to Atlassian every week through the Forge personal data reporting API. For a closed account it replaces the account id with a random closed-account: token in journal entries (authors, reviewers, change summaries), restore requests with their stored preview and result, restore points, stored configuration versions and the settings' last editor. It re-hashes the affected versions and deletes the old copies, removes the account id and token mapping from the ledger (the chain stays verifiable), deletes the cached administrator check for that account and records a count-only TOMBSTONE entry. Free text typed by administrators is not scanned. This runs even when the licence has lapsed. Other requests: support@matifyapps.de.

15. Logging

Forge logs contain event names, counts, durations, error codes and a random correlation reference. One warning event contains the numeric id of a configuration object Jira refused to show to the app. No account ids, names, email addresses, free text or configuration content are logged.

16. Transport and platform security

All traffic between the app, Jira and the browser runs inside Atlassian's platform (Forge functions call Jira through the Forge runtime; the Custom UI talks to the app's functions through the Forge bridge). Storage, transport encryption and infrastructure security are Atlassian's; see Atlassian's own Forge and cloud security documentation. Matify adds:

No compliance certification (such as SOC 2 or ISO 27001) is claimed for the app or for Matify.

17. Security contact

support@matifyapps.de with "security" in the subject, or the login-free support form with the type "Security vulnerability". Please don't report vulnerabilities in the public tracker. Matify follows Atlassian's Security Bug Fix Policy for Marketplace apps and notifies affected customers and Atlassian of a security incident affecting customer data.

18. Privacy policy

Privacy policy for Config Undo for Jira

19. Documentation

Config Undo for Jira documentation · Known limitations · Support

20. Last updated

7 October 2026.