π Privacy Policy
We value your privacy. Sprint Health Analyzer is built on the Atlassian Forge platform and fully respects Atlassianβs data security and privacy standards.
This page outlines what data the app uses, how it is processed, and what guarantees are in place to protect your Jira instance.
β Key Principles
π§© No external data transfer β all processing occurs inside your Jira Cloud environment
π No data storage β the app does not persist data anywhere (locally or remotely)
π§ In-memory computation only β all metrics are calculated at runtime, on the fly
π Forge-hosted β infrastructure is managed and secured by Atlassian
π¦ What Data Is Accessed
The app only reads metadata from issues inside the current Jira project. Specifically:
Data Type | Purpose |
---|---|
Issue key | To link and identify each issue |
Summary, status | For display and filtering |
Changelog | To calculate delivery metrics |
Story Points | To compute velocity and Agile progress |
Issue links | To detect blocking dependencies |
Sprint field | To group and analyze issues by sprint |
This data is accessed read-only via Forge APIs.
π What the App Does Not Do
β Does not send any data to third-party servers
β Does not write or update any Jira issues or fields
β Does not store any data locally in your browser or Forge storage
β Does not track users or usage analytics
π Hosting & Infrastructure
Sprint Health Analyzer is deployed on the Atlassian Forge platform, which offers:
Enforced data residency inside Atlassianβs secure cloud
Strict app sandboxing and permission scopes
OAuth 2.0 and JWT-based authorization
Built-in rate limiting and access control
π₯ Data Visibility
Only users with access to the Jira project can view metrics and issue data in Sprint Health Analyzer. The app does not elevate or bypass existing Jira permissions.
π§ Contact
If you have privacy or compliance questions, contact us:
π© support@typeswitch.net
We respond to security inquiries within 1β2 business days.
Β