Approval Gate for Jira — Privacy Policy

Last updated: 1 October 2026.

The short version

Approval Gate is a pure Atlassian Forge app. Its manifest declares no external.fetch permissions at all, so the app cannot make any outbound network call — your data never leaves Atlassian's infrastructure. There is no vendor server, no database of ours, and no account to create.

What data the app accesses

The approval records the app writes contain: the request title and optional description you type, the decision rule (one approval or unanimous), timestamps, any comments you add to a decision, and the Atlassian accountId of the requester, the approvers and every actor in the audit trail. Display names and e-mail addresses are not written into the record — names are resolved fresh from Jira each time the panel loads (/rest/api/3/user/bulk) and are discarded afterwards.

Where data is stored and processed

All approval data is stored inside Jira itself, as a Jira issue property with the key greenlight-approvals on the issue the approval belongs to. Decision mirrors are stored as ordinary Jira issue comments; the comment posted when approvers are reassigned does not name individuals. A second issue property, approval-gate-exceptions, records the moments the workflow validator allowed a transition through without being able to enforce the gate — for example when the subscription was inactive or Jira did not return the approval data. Each entry holds a timestamp, a reason code and the issue id; it contains no personal data beyond that. Processing happens in the Forge function running in Atlassian's cloud environment; nothing is copied anywhere else.

From version 4.0.0 the app also keeps a small account index in Forge Storage (Atlassian's key-value store, scoped to your installation): for each Atlassian account ID found in an approval record, the IDs of the issues it occurs on and the date it was first indexed, plus technical progress markers for the one-time scan and for a running erasure. The index holds no names, no e-mail addresses and no approval content. It exists for one purpose: so that the app can report the accounts it holds to Atlassian and find them again when an account is closed.

What the app does not do

Data retention and deletion

Because approval data lives on the Jira issue, it follows that issue's lifecycle: when the issue is deleted, its greenlight-approvals property is deleted with it. The audit trail is append-only by design — entries are never rewritten or silently removed, with one exception: when Atlassian reports an account as closed, its account ID is replaced by an anonymous marker, as Atlassian's user privacy rules require. The decision itself is kept. A request that has been approved, rejected or cancelled can otherwise no longer be modified.

Uninstalling the app removes its access to your site, the panel disappears and its Forge Storage (the account index) is discarded with the installation. It does not by itself erase data already written into Jira: the issue property and any mirrored comments remain part of the issue. A Jira administrator can remove them at any time — comments through the normal Jira UI, and the issue property through the Jira REST API (DELETE /rest/api/3/issue/{issueIdOrKey}/properties/greenlight-approvals, and DELETE /rest/api/3/issue/{issueIdOrKey}/properties/approval-gate-exceptions for the exception log). We can neither reach nor retain that data ourselves.

Personal data reporting and erasure

From version 4.0.0, once a week the app reports the account IDs it holds to Atlassian through the Personal Data Reporting API. What happens next depends on Atlassian's answer:

Versions before 3.8.0 posted a comment that listed the new approvers when approvers were reassigned. During its one-time scan, version 4.0.0 rewrites those comments — only the ones the app itself posted — to the current form, which states the number of approvers and the decision rule and names nobody.

Not covered by this erasure: free text that people type themselves (the request title and description, comments on a decision) and ordinary Jira comments. That text is part of the issue and is managed in Jira by your administrators.

Version 4.0.0 adds two permissions (storage:app and report:personal-data), so a site administrator has to approve the update. Until then the earlier version keeps running on that site, without the account index, the report and the erasure described here.

Contact

Questions about this statement or about data handling: info@kyc-checks.nl.