Gladmill

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

Your data stays in Atlassian.The app runs on Atlassian Forge and makes no requests outside Atlassian. It has no external servers, and Gladmill has no copy of your data.
The smallest amount of personal data.The app stores Atlassian account ids only. It never stores names, email addresses, avatars, issue summaries or comments.
No tracking.The app uses no analytics, cookies, ads or third-party scripts.
Closed accounts are erased.The app takes part in Atlassian's personal data reporting.
No sub-processorsother than Atlassian.

Async Estimate for Jira

What it stores

Everything is stored in Atlassian's Forge app storage for your Jira site:

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

ScopeWhy the app needs it
read:jira-workList the issues being estimated on the Estimation board, and find the story points field.
write:jira-workWrite the agreed estimate to the story points field when a user clicks Set story points.
read:jira-userShow who has voted.
storage:appKeep 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

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

Development and releases

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:

SeverityCVSSFixed within
Critical9.0 and above10 days
High7.0 to 8.94 weeks
Medium4.0 to 6.912 weeks
Lowbelow 4.025 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].