Sprint Scope Changes for Jira — Privacy Statement
What this app does
Sprint Scope shows what was added to and removed from a sprint while it was running: issue by issue, who made the change, when, and with how many story points. To do this, it reads Jira's own change history.
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 field — not because it chooses not to, but because it never asked for the right to.
What the app stores
Two numbers per gadget: which board and which sprint you looked at last. That is all, and nothing else. Storage is on the app storage provided by Atlassian, tied to your Jira site.
The app stores no personal data.
What the app sees while it works
To build the report, the app reads change history entries, and in them it sees the name and Atlassian account ID of the person who made each change — the same thing you see in Jira's own interface. It sends this data to your browser for display, and does not store it.
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's configuration — the board and the sprint you picked.
Not covered: nothing, because there is nothing else. What the app reads from Jira's change history goes to your browser and is never kept.
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 — and your report never shows more than Jira itself would show you.
Logging
The app writes a log for debugging, which the developer can see. The log contains call counts, timings, error codes and IDs — 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 choice straight away: the app can no longer read it. Atlassian then holds it for its own retention period before erasing it 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.