Time in Status for Jira — Data Security and Privacy

Last updated: 29 July 2026.

The short version

Time in Status is a pure Atlassian Forge app. It declares no external.fetch permissions and makes no outbound network calls, so your data never leaves Atlassian's infrastructure. It also stores nothing of its own: every figure on the page is computed on the fly from data the app reads from Jira at the moment you open it.

What data the app accesses

The app requests exactly one permission scope:

• read:jira-work — read-only access, used to read the issues in the project you are viewing (their key, summary, current status and creation date), the project's workflow statuses and status categories, and each issue's change history (changelog), which is where the status transitions used for the timing calculation come from.

Jira is queried with the app's own installation credentials (Forge asApp), scoped to the project whose page is open, so the report is complete rather than partial. No end-user credentials or tokens are used or stored.

The app requests no write scopes, no admin scopes and no user scopes. It does not call read:jira-user, so it does not read user profiles, display names or e-mail addresses. It does not read comments, attachments or worklogs. The only fields requested from the issue search are summary, status and created.

Where data is stored and processed

Nowhere outside Jira. The app uses no Forge Storage (it does not request the storage:app scope), no Jira issue or entity properties, no app custom field and no external database. Jira data is read into the memory of a short-lived Forge function, turned into durations, returned to the page you are looking at, and discarded when the function ends. Processing happens inside Atlassian's Forge platform, in the region Atlassian runs your Jira site in. There is no cache, no copy and no export to any system we control.

What the app does not do

• It does not send data to any third party, and it cannot: no external endpoints are declared in its manifest.
• It does not sell, share or monetise your data.
• It contains no analytics, telemetry, tracking pixels, cookies or advertising SDKs.
• It does not modify, create or delete anything in Jira — the only permission it holds is read-only.
• It does not identify individual users. It reads no account IDs, no display names and no e-mail addresses.

Data retention and deletion

There is no retention period, because there is no retained data. The app keeps no records between page loads, so there is nothing to delete, export or request access to. Uninstalling the app removes it from your site immediately; no residual data belonging to the app exists in Forge Storage or elsewhere. Your issues and their change history stay in Jira, untouched and governed by Atlassian's own retention terms.

Contact

Questions about this statement, or a data request: info@kyc-checks.nl.