Security Statement
Last updated
Last updated
We understand that security is a top priority for our customers. That's why we process only minimal data required to provide the functionality and that's why we chosen Forge storage as a place to keep the data - this way it never exits Atlassian infrastructure. We are transparent in how we handle customer data.
We follow Atlassian requirements and recommendations regarding apps security.
Our privacy policy can be found here:
The app is built fully on Forge, a platform built by Atlassian, designed with security and data privacy in mind. See more on
domain name (e.g. React, Java)
only accountId of the expert assigned. We fetch display names and avatars dynamically on rendering
Subject Matter Experts custom field id
in the , a service provided by Atlassian which is secure, reliable and highly available
no. The data is within Atlassian infrastructure at all time.
We designed the app to be maximally secure for our customers.
storage:app
- to be able to use Forge storage
read:jira-user
- to be able to fetch users data while rendering (display name and avatar)
write:jira-work
- to be able to add comments notifying experts about being assigned to the issue
Feel free to contact us at security@acceleration-engineering.com. We'll answer any questions in detail. We know that security and privacy are the key aspects for our customers.
read:jira-work
- to be able to run our code on , to notify the experts after being assigned. Forge Events are fully asynchronous and decoupled from the main Issue Creation process and cannot affect or break it.
Yes. Forge storage which we use, supports it out of the box. It is handled by Atlassian. See
Yes. See
Through OAuth 2.0: