Privacy Policy

Cycle Time Scatter Chart for Jira Dashboard

Last updated: 1 October 2026

This app is a Jira dashboard gadget published on the Atlassian Marketplace by the Marketplace partner flowscope (referred to below as "we"). This page describes exactly what the app does with data. It is written to match the app's source code, not to describe a general policy.

1. What the app reads

The app reads Jira issues through the official Jira REST API, using the read:jira-work scope and nothing else. All requests are made as the user who is viewing the gadget — the app can only ever see the issues that the person looking at the dashboard is already allowed to see. It never uses an administrator identity and it cannot read anything a viewer could not read themselves.

Specifically it reads, for issues matched by a JQL filter that a Jira administrator configures on the gadget:

the issue key (for example ABC-123)
the issue's status transition history — which status it moved to, and when
the issue creation date

The app does not read issue summaries, descriptions, comments, attachments, custom field values, user profile details, email addresses, or any other content.

2. What the app stores

The app writes one short-lived cache record per configuration per user, into Atlassian's own Forge app storage. That storage lives inside Atlassian's infrastructure and is provisioned for this app by Atlassian; we have no server of our own and no database of our own.

What	Detail
Cache key	Includes the Atlassian account ID of the user who loaded the gadget, together with a short hash of the gadget's configuration
Cache value	The computed result only: the number of completed issues, each issue key with its completion date and cycle time in days, the percentile values, and counts of excluded items
Lifetime	1 hour. Entries are overwritten on the next load and are never archived or copied elsewhere

Why the account ID is in the key. Because the app reads Jira as the viewing user, two different people looking at the same gadget can legitimately see two different sets of issues. The cache is therefore keyed per user, so that one person's cached result is never served to another. Removing the account ID from the key would create a risk of showing one user data derived from another user's permissions, so it is kept deliberately.

An Atlassian account ID is a pseudonymous identifier. The app never resolves it to a name, an email address, or any other profile information, and it is never transmitted anywhere.

3. What the app does not do

This is the part that matters most, and every line of it is verifiable in the app's manifest and source:

No external servers. The app makes no network requests to any host other than Atlassian's own Jira REST API. There is no egress, no webhook, no callback URL, and no third-party integration of any kind.
No analytics or telemetry. No usage tracking, no error reporting service, no cookies, no fingerprinting.
No advertising. No ad networks, no trackers, no profiling.
No selling or sharing. We do not sell, rent, or share any data with anyone. There is nowhere for it to be shared to.
No AI or machine-learning processing. No data is sent to any model or inference service.
No data outside Atlassian. All processing happens inside Atlassian's Forge runtime, in the region your Jira instance is pinned to.

4. Sub-processors

None. Atlassian provides the platform (Forge runtime and storage) under your own agreement with Atlassian. Beyond Atlassian, no other company processes any data on our behalf.

5. Retention and deletion

Cache entries expire after 1 hour and are overwritten in normal use.
Uninstalling the app removes its Forge storage, including any cache entry that has not yet expired. Atlassian removes app storage on uninstall.
We hold no separate copy of anything, so there is nothing else for us to delete.

6. Your rights

Because the app stores nothing outside Atlassian and keeps data for one hour, a data subject request is normally satisfied by removing the app from the site (which clears its storage) or simply by waiting for the cache to expire. If you need something specific, contact your Jira administrator first — they control the installation — and you may also contact us at the address below.

7. Changes to this policy

If the app's data handling changes, this page changes with it, and the "Last updated" date above changes. The app's listing on the Atlassian Marketplace links to this page.

8. Contact

Questions about this policy, or about the app's data handling: wangxydlut@gmail.com. See also the support page.