Team Pivot Gadget for Jira — Privacy Statement
What this app does
Team Pivot shows the issues of a saved filter or a JQL query in one table: a row for each Team, a column for each value of a field you pick, and a count of issues or story points in each cell.
Where your data goes
Nowhere. The app sends no data outside Atlassian's cloud. There is no external service, no analytics, no advertising, no subcontractor.
This is not a promise but a structural property: the app runs on Atlassian's Forge platform, under the terms of the Runs on Atlassian program, and the source code contains zero outgoing network calls. An automated check guards this on every change.
What the app writes
Nothing. The app has no write permission to Jira. It cannot change an issue, a filter or a field — not because it chooses not to, but because it never asked for the right to.
What the app stores
The settings of each gadget:
- which saved filter it uses (its ID), or the JQL query you typed;
- the field you picked for the columns;
- whether it counts issues or story points;
- how the rows are sorted.
That is all. Storage is on the app storage provided by Atlassian, tied to your Jira site.
One thing to know about the JQL query: it is stored exactly as you typed it. If you type a person's name into it — for example assignee = "Jane Doe" — that name is stored with the gadget's settings. The app stores no other personal data.
What the app sees while it works
To build the table, the app searches Jira for the issues that match your filter or query. For each issue it reads only the fields the table needs: the Team, the field you picked for the columns, and the story points. If you pick Assignee for the columns, that includes the assignee's name.
The app sends this to your browser for display, and does not store it. The names of your saved filters, shown in the settings, are not stored either.
Who sees what the app shows
The app queries Jira with your permissions. What you cannot see in Jira, you do not see in the app — the table never shows more than Jira itself would show you.
Data residency
Atlassian lets your admin pin your site's data to a region. The app's stored data follows that setting, because it sits on Atlassian's own app storage and nowhere else.
Covered by it: the gadget settings listed above.
Not covered: nothing, because there is nothing else. What the app reads from Jira goes to your browser and is never kept.
Logging
The app writes a log for debugging, which the developer can see. The log contains counts, timings, error types, the column and value choice, and the length of your query — not the query itself, no names, no email addresses, no issue summaries.
Your Jira admin controls this. From admin.atlassian.com they can read and download these logs, or switch off our access to them entirely. Switching it off does not affect the app: it keeps working exactly the same. It only means that if you report a problem, we have to ask you for details we would otherwise be able to look up ourselves.
Deletion
If you remove the app from your Jira site, Atlassian soft-deletes the stored settings straight away: the app can no longer read them. Atlassian then holds them for its own retention period before erasing them for good.
For 21 days after removal, that data can be relinked to a fresh installation, if someone asks Atlassian for it. We ask for it only if you ask us to — for instance if the app was removed by mistake and you want your gadget settings back.
Since the app stores nothing else, there is nothing else to delete.