Effective 16 October 2026. This policy covers Sprint Pack, an app for Jira Cloud sold on the Atlassian Marketplace by Weave Commons (“we”). We, not Atlassian, are responsible for how Sprint Pack processes your data.
Sprint Pack runs on Atlassian’s Forge platform and has no server of its own. Everything it reads and stores stays in Atlassian’s cloud, with your Jira site. We don’t receive a copy of it.
The app’s storage is kept in the same country or region as your Jira site’s data: your site’s data residency location if your organization has chosen one, otherwise wherever Atlassian hosts your site. The app’s logs are kept by Atlassian and aren’t covered by data residency. Support email is stored in the United States (see “Services we use” below).
In Atlassian’s storage for your site:
assignee = 712020:…), so a board filter that names people holds their account IDs; so does the copy of the filter kept with each closed sprint.In Jira itself: the app’s read-only fields on issues, its stored JQL search results, and, if an admin publishes BI data, sprint totals saved as board properties.
The app doesn’t collect email addresses, passwords or API tokens.
Atlassian’s platform keeps the app’s logs. They hold issue, sprint and board IDs, search text and error messages. Account IDs are replaced with <account> before anything is logged. We read them only to support and fix the app.
Nothing, by the app. Files you export are built in your browser and saved by you; they include the names of the people who changed issues, issue assignees, the reasons people wrote with their authors’ names, and the name of the person who made the file. A copied summary names the person it was counted for. BI data you pull into another tool with your own credentials is your export.
We don’t sell personal data and don’t use it for advertising.
Support and security email is handled by Fastmail (Fastmail Pty Ltd, Australia), which stores it on servers in the United States. Fastmail processes it only to deliver and store our mail.
While the app is installed. When it’s uninstalled, the app deletes the BI data it published; on a site with many published boards, use “Unpublish all” on the admin page first, as uninstalling allows the app only a minute. Atlassian keeps the app’s storage for 28 days before deleting it. The app’s fields on issues and its stored search results stay in Jira; they hold sprint IDs, names and labels, no personal data. Support emails are kept as long as needed to answer them, and at most 2 years.
Closed Atlassian accounts: once a week the app reports the account IDs it stores to Atlassian, as Atlassian requires of every app, and erases the ones Atlassian says are closed, usually within a week of the closure. A reason written by a closed account keeps its text and loses its author. A board filter that names a closed account is read from Jira again at once; if the app can’t read the board then, it keeps the filter it has and tries again the next week. If the board’s filter in Jira still names the account, the app keeps the filter as Jira has it, because the board’s numbers depend on it, and doesn’t report the account again; the admin page lists those boards so an admin can edit the filter in Jira. The app keeps a one-way hash of each closed account, so the list doesn’t hold the account ID itself and the app doesn’t store the account again when it reads it from Jira’s history. Reporting needs a permission added in a later version of the app: until your admin approves that update, the app keeps erasing old caches but can’t hear about closures.
For data in your Jira site, contact your site admin, who can uninstall the app. For anything we hold, email support@sprintpack.weavecommons.com.
We’ll post changes here with a new effective date.