Effective date: 1 August 2026 · Vendor: Schema Tools
ScopePulse — Sprint Scope Change Tracking for Jira runs entirely on Atlassian Forge, inside Atlassian’s infrastructure. We do not operate any servers, and your data never leaves Atlassian.
The app reads, with the viewing user’s own permissions: Jira boards, sprints, issues (summary, status, estimate, created date) and issue change histories of the Sprint field. It does not modify any Jira data.
Computed per-sprint summaries for closed sprints (issue keys, category flags, timestamps, change-author account IDs — never display names — and totals) are cached in Forge app storage, hosted by Atlassian, to speed up repeat views. No data is sent to the vendor or any third party. Uninstalling the app removes its storage per Atlassian’s Forge data lifecycle.
The app displays the names of users who changed sprint scope, as recorded by Jira in issue histories; names are resolved at viewing time and are not stored — only Atlassian account IDs are cached. This data stays inside your Atlassian site. The vendor has no access to it.
None. The app declares no external endpoints and is eligible for Atlassian’s “Runs on Atlassian” program.
Privacy questions: support@sixwiki.com.