Security
Built on Forge, nothing leaves Atlassian
- Sprint Truth runs only on Atlassian Forge.
- It has no servers of its own, no outside network access and no remote backend.
- Data is kept in Forge hosted storage for your site, which Atlassian encrypts and keeps separate for each site.
Least access
The app asks only for the Jira permissions it needs to read sprint history, write its own fields and property, show names live, and report personal data. Each one, and why:
| Permission | Why |
|---|---|
read:jira-work | Read work items, their sprint and story-point history, search, the field list, and permission checks. |
write:jira-work | Write and remove the app's own hidden record on each work item. It never edits work items, sprints or boards. |
read:sprint:jira-software | Read sprints and the work items in a sprint, for history and the check against Jira. |
read:board-scope:jira-software | List Scrum boards and read a board, to check who can see it. |
read:project:jira | Needed by Jira to list boards. |
read:issue-details:jira | Needed by Jira to read the work items in a sprint for the check. |
read:jql:jira | Needed by Jira for the same sprint read. |
read:jira-user | Show people's names on the Sprint review page, read live and never stored. |
storage:app | The app's own settings and job state. |
report:personal-data | Tell Atlassian every week which account ids the app stores, so closed accounts are erased. |
write:app-data:jira | Write values into the app's own nine read-only fields. |
Who can see what
- Admin page: Jira admins only. Every action re-checks admin rights as the signed-in person.
- Sprint review page, PMO view and gadget: show a board's data only after checking that the viewer can open that board.
- Work item summaries and names: read with the viewer's own permissions.
- Rovo agent: checks that the person asking can browse the board's project before it answers.
- Search functions: Jira runs the search with your own permissions.
Data we keep, and don't
We keep sprint facts and Atlassian account ids. We never keep work item text, names, emails or sprint goals. Error records hold codes, never Jira's error text. Privacy policy
Licensing fails safe
If the license can't be confirmed as active, the app stops updating fields, the hidden record on each work item and sprint history, and the Sprint review page, PMO view and gadgets stop showing data. Existing values stay. Two things keep running on purpose: closed Atlassian accounts are still erased every week, and an admin can still remove the app's record from work items.
Testing
The logic is covered by automated tests, and the app is reviewed against Atlassian's Runs on Atlassian requirements, which keep it inside Forge with no network access of its own. We don't hold a security certification, and we haven't had an independent penetration test.
Fixing vulnerabilities
We follow Atlassian's Security Bug Fix Policy for cloud apps. If we have a security incident, we tell Atlassian within 24 hours and affected customers within 72 hours.
Report a security issue
Email hello@goldstandardweb.com with "Security" in the subject. Please give us time to fix it before going public.