What data we process
Issue fields such as summary, status, assignee, type, and timestamps. Configuration metadata such as board ID and filters to build the standup view.
Privacy and Security Statement
This page explains how the Sprint Assistant plugin handles data when used inside Jira.
Summary
- We do not sell or share your data with third parties.
- We only access Jira data necessary to render the views you request.
- No personal data is stored by the information website itself.
What we do not process
We do not collect authentication credentials, payment details, or store issue contents outside Jira.
Data retention
By default, Sprint Assistant does not persist your Jira data. Any transient caching (if enabled in your Jira instance) is memory-only and cleared automatically when the session ends.
Security
All communication happens within Jira’s secure context. If a backend is used, it follows Atlassian Forge
security constraints and least-privilege scopes.
The application runs inside the Atlassian Forge
framework and the users browser. The backend process is acting on behalf of the rights of the current logged
in user when calling APIs.
The application is running on the Atlassian Forge platform which is a SOC 2 certified. Further details can be found here.
Your rights
For access, correction, or deletion of personal data, contact your Jira administrator first. For plugin-specific questions, email our support.