Sprint Velocity Chart for Jira — Privacy Statement
What this app does
Sprint Velocity Chart shows, for the last closed sprints of a Jira board, how much work was committed, how much was completed, and what was added or removed while each sprint was running.
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 sprint or a board — not because it chooses not to, but because it never asked for the right to.
What the app stores
Two numbers per gadget: the ID of the board you picked, and the ID of the sprint you picked. That is all.
Storage is on the app storage provided by Atlassian, tied to your Jira site.
What the app sees while it works
To count a sprint, the app reads from Jira:
- the board's settings: its columns and its estimate field;
- the board's sprints and the issues in them;
- each issue's history of sprint, status and estimate changes;
- each issue's key and summary, for the sprint details.
The sprint details show who added or removed an issue, so the app reads the display name of the person who made the change.
The app sends this to your browser for display, and does not store it.
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 gadget 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 two numbers 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, and the IDs of the board, sprint, dashboard and gadget — 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 numbers 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.
Since the app stores nothing else, there is nothing else to delete.