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.
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.
Deletion
If you remove the app from your Jira site, the stored choice is deleted. Since the app stores nothing else, there is nothing else to delete.