Sprint Scope Guard — Privacy and Data Handling

Sprint Scope Guard is provided by FrisForge LLC. Questions about privacy or stored app data may be sent to [email protected].

Purpose and information processed

The app reads Jira board, filter, project, and permission information to diagnose one selected user's Manage Sprints coverage and to monitor a healthy baseline. The administrator selects the board and Jira user. Jira's native user picker and user display can process current account identity/profile information while presenting that selection.

Board names, project names and keys, filter JQL, and permission responses are used during the evaluation. The app does not persist issue content, display names, email addresses, avatars, project names, filter JQL, permission schemes, group/role membership, or credentials in its Guard records.

Information stored by the app

The app stores personal data. Native Atlassian Forge storage retains the selected user's Atlassian account ID, linked to:

• the board ID;
• the healthy project-ID baseline, its version, and establishment time;
• the most recent outcome, reason, project IDs, deficient project IDs, Guard status, and evaluation time;
• scheduler deduplication state and the earliest retained-data retrieval time; and
• the account's privacy-reporting cycle and pending-erasure metadata needed for the Atlassian personal-data lifecycle.

Short-lived tokens coordinate concurrent app actions. Guard and privacy state are separated by the Forge app, environment, and installation. Hashing an account-linked storage key does not make the record anonymous.

Retention and deletion

Guard records remain while the administrator keeps a Guard enabled. Remove Guard deletes its monitor record; privacy metadata is removed once no records remain for that account. This app does not promise a fixed Guard-record TTL.

The app periodically reports retained account identifiers and retrieval dates to Atlassian through its Personal Data Reporting interface. It follows the reporting cycle returned by Atlassian. If Atlassian returns closed or updated for an account, the app removes all that account's Guards and associated privacy metadata. It does not silently rebuild those Guards; a Jira administrator must select the current user and enable a fresh healthy baseline. Legacy Guard records without trustworthy retrieval timestamps are removed during migration rather than being assigned an invented age.

The uninstall handler attempts application-record cleanup. Atlassian controls platform storage, recovery, backups, and residual post-uninstallation retention. Application deletion is not a promise that every underlying platform copy is immediately or permanently purged. See Atlassian's Forge storage lifecycle.

Hosting, processing, and logs

Core app execution and Guard storage use Atlassian Forge and Jira. The app has no external customer-data backend, Forge Remote, external application analytics, or external application data destination. Privacy reporting stays within Atlassian services. Scheduled application logs contain aggregate operational counts rather than raw user identifiers or customer payloads. Atlassian may maintain its own operational, diagnostic, and security logs under its applicable terms.

For SSG data residency, all retained account-linked Guard records and privacy metadata described above are in scope. They are stored only in persistent Forge hosted storage. Forge manages pinning and migration with the host Jira site's supported data-residency location. SSG has no separate remote storage location to select or migrate. Aggregate operational logs are not retained account-linked Guard data. See Forge data residency.

Processing locations and underlying platform controls follow Atlassian's applicable Forge documentation and agreements. Data residency describes supported storage pinning; this page does not promise that every processing activity or platform log remains in one jurisdiction.

Support communications

If you contact FrisForge, we receive the contact information and app details you choose to include, such as screenshots and error descriptions. These communications are separate from the app's Forge data path and are used to respond to the request, investigate defects or security concerns, administer support, keep appropriate records, and meet legal obligations. They may be retained as reasonably necessary for those purposes and legal obligations. Do not send passwords, API tokens, or unnecessary Jira content.

Contact your Jira administrator or [email protected] with an access, correction, deletion, or privacy question. Jira source data remains governed by your Jira environment; removing a Guard does not delete your Jira boards, projects, users, or configuration. See the Data Processing Addendum and Support.