Last updated 16 August 2026
There is no server of ours. This app runs entirely inside Atlassian's own infrastructure on the Forge platform. Nothing it reads or writes is sent anywhere else, because there is nowhere else for it to go.
It runs the JQL query you configured and counts the results, grouped by the field you chose. That is the whole job.
It stores nothing. Not the counts, not the issues, not a cache. Every chart is
drawn from a query run at the moment you look at it, which is also why there is no
storage:app permission in the list below and why there is no data of yours to delete.
The only thing kept anywhere is the gadget's own settings, which are the JQL and field you typed;
Jira holds those with the dashboard itself, not us.
It never writes to your Jira. There is no write permission, so it
could not create, edit or transition anything even if it were asked to.
| Permission | What it is for |
|---|---|
read:jira-work |
To run your query and to list the fields you can group by. Charts run as you, using your own permissions, so a gadget can never show anyone an issue they would not already be allowed to open. |
That is the entire list. There is no permission here for writing, for user directories, for attachments, or for site administration, and none is requested.
If you group a chart by a person — Assignee, Reporter, Creator — then the app reads those users' display names, because the chart cannot label a bar "Dana Ruiz" without them. Those names are read at the moment the chart draws, shown to you, and then gone. They are not stored, not logged, and not sent anywhere.
Beyond that it does not read issue contents. It asks Jira only for the single field you chose to group by, which keeps the query small and means descriptions, comments and attachments are never fetched at all.
None. No analytics, no tracking pixels, no third-party scripts, no telemetry back to us. Atlassian collects its own platform-level operational metrics about app invocations, as it does for every Forge app, and that is described in Atlassian's own privacy policy.
Inside your Atlassian instance, in the region Atlassian hosts it in. The app makes no outbound network calls to any other host. It is eligible for Atlassian's Runs on Atlassian programme, which is their check for exactly this: that an app stores its data on Atlassian infrastructure and does not egress.
There is nothing to delete, because nothing of yours is stored. Uninstalling the app removes the gadgets from your dashboards; the issues they were counting are your own and are untouched.
Support requests reach us by email. If you send us a description of a problem, we hold that email in order to answer it, and for no other purpose. We do not add support contacts to any mailing list.
If this policy changes, the date at the top changes with it. If a change ever made the statement at the top of this page untrue, that would be a different product, and it would be said plainly here and on the listing rather than buried in a revision.