Jira app privacy and security
Last updated 2026-10-27
This page covers privacy and security for Gladmill's apps for Jira Cloud. Right now that is one app, Async Estimate for Jira. Its full policy is the Async Estimate privacy policy. This website itself is covered by Site privacy.
At a glance
Async Estimate for Jira
What it stores
Everything is stored in Atlassian's Forge app storage for your Jira site:
- Estimation rounds, one per issue: the issue id, issue key and project id, the scale (Fibonacci or T-shirt) and when the round started.
- Votes: the voter's Atlassian account id, the value chosen and when it was cast. Values stay hidden from everyone until someone reveals the round.
- After a reveal: who revealed the round and when. If the estimate is written back, who applied it, the value and when.
Names and avatars are shown by Jira in your browser when you view a round. The app never saves them. The Estimation board reads issue keys, summaries and statuses through Jira to show the list, and doesn't store them.
What it can access in Jira, and why
| Scope | Why the app needs it |
|---|---|
read:jira-work | List the issues being estimated on the Estimation board, and find the story points field. |
write:jira-work | Write the agreed estimate to the story points field when a user clicks Set story points. |
read:jira-user | Show who has voted. |
storage:app | Keep rounds and votes in Forge storage. |
Jira calls are made as the signed-in user. The app can only show issues that the user can view, and only edit issues that the user can edit. It has no permissions of its own beyond those of the person using it.
Where data goes
Nowhere outside Atlassian. The app declares no external domains, so Forge itself blocks it from sending data elsewhere. Data is stored in Forge-hosted storage, which follows Atlassian's data residency for Forge apps.
Logs
The app's Forge logs contain only operational counts and error status codes. For example: how many closed accounts were erased, or that a personal data report request failed. They contain no account ids, issue content or vote values. Atlassian keeps them under its Forge logging retention.
Retention and deletion
- Closed accounts: every week the app reports the account ids it stores to Atlassian's personal data reporting API. When Atlassian reports an account as closed, the app erases that person's votes and removes them from revealed rounds.
- New rounds: starting a new round on an issue deletes the previous round's votes.
- Uninstall: Atlassian soft-deletes the app's stored data and then permanently deletes it after its standard retention period. If you reinstall within 21 days, Atlassian can restore the data on request.
- On request: a site admin can email us to ask how to remove data for a project or a person. We can't see your data, so we tell you what to do in Jira.
Security policy
Architecture
The app runs entirely on Atlassian Forge: its code runs in Atlassian's Forge functions and its data sits in Forge storage. We run no servers of our own, so there is no Gladmill system that holds or can leak your Jira data. Hosting, encryption of stored data and data in transit, and isolation between customer sites are handled by Atlassian (Forge security).
Access control
- Least privilege: the app asks for only the four Jira scopes listed above and declares no external domains.
- Acts as the user: every Jira call is made as the signed-in user, so the app never shows or changes anything that person couldn't see or change in Jira.
- No secrets: the app handles no passwords, API tokens or keys.
- Hidden votes: before a reveal, the app sends nobody else's vote values to the browser, only who has voted.
Development and releases
- Every change goes through a reviewed pull request before it is deployed.
- Automated tests cover vote validation and summaries, licence checks and the erasure of closed accounts, and they must pass before a release.
- Few dependencies: Atlassian's Forge libraries and React.
- Releases go out through Atlassian's Forge deployment. If a new version needs new permissions, a site admin has to approve them.
Reporting a vulnerability
Email [email protected] with "Security" in the subject. Include the steps to reproduce, and please don't test against other customers' sites. We reply within 2 working days. Reports through Atlassian's Marketplace Security program are welcome too.
We fix confirmed vulnerabilities within the deadlines in Atlassian's Marketplace security bug fix policy for cloud apps:
| Severity | CVSS | Fixed within |
|---|---|---|
| Critical | 9.0 and above | 10 days |
| High | 7.0 to 8.9 | 4 weeks |
| Medium | 4.0 to 6.9 | 12 weeks |
| Low | below 4.0 | 25 weeks |
Incidents
If we learn of a security incident that affects customer data, we contain it, tell Atlassian, and notify the admins of affected sites without undue delay. We tell you what happened, what data was involved and what we have done about it.
Changes
If a Jira app starts to store new kinds of data or send data outside Atlassian, we update this page and the date above first. Atlassian also asks admins to approve any new permissions before the app gets them.
Contact
Questions, or a data request: [email protected].