LogoLogo
  • Acceleration Docs
  • Apps
    • Issue Create Analytics
      • Configuration
      • Security Statement
      • Supported entry points, project types and fields
    • Subject Matter Experts
      • Security Statement
    • X5 Deep Work
      • Security Statement
  • Support and links
    • Book a free demo call
    • Report a bug
    • Suggest a feature
    • Our website
    • Marketplace Partner profile
Powered by GitBook
On this page
Export as PDF
  1. Apps
  2. Issue Create Analytics

Security Statement

PreviousConfigurationNextSupported entry points, project types and fields

Last updated 20 days ago

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.

The platform

The app is built entirely on Forge, a platform developed by Atlassian with a strong focus on security and data privacy. Forge provides enterprise-grade security and reliability, making it an ideal foundation for our applications. See more on

Where we store the data

In the provided by Atlassian.

Does the app have Data Egress?

  • no. The data is within Atlassian Cloud infrastructure at all times.

  • We designed the app to be maximally secure for our customers.

Does the app support Data Residency?

Yes, the Forge SQL we use supports it out of the box and it's managed by Atlassian. See and the .

All of the data stored by the app is in-scope for data residency.

What data we store

  • issueId

  • issueKey

  • projectId

  • issueTypeId

  • issueTypeIconUrl

  • accountId

  • fieldId

  • fieldName

  • createdAt - timestamp, the issue field presenting when the issue was created

  • coupled with the app metrics.

The API used

Why do we need specific permissions

  • storage:app - to be able to use Forge storage

  • write:app-data:jira - required by the Jira UI modifications REST API

Does the app have a data backup?

How the communication between Jira and the app works:

Privacy Policy

In case you have any questions related to security

Feel free to contact us at security@acceleration-engineering.com. We'll answer any questions in detail. We know that security and data privacy are the key aspects for our customers.

We use the extension point to provide app functionality. It's the only module that enables the detailed analytics use case. See more about the API .

read:jira-user , read:jira-work , manage:jira-configuration , write:jira-work , manage:jira-project - . This extension point is backing one of the most popular apps in Atlassian Marketplace and it's mostly used to customize field properties and values, for example by templating apps. We use it to provide detailed user behavior analytics.

Yes. See

Through OAuth 2.0:

You can view our privacy policy here:

https://developer.atlassian.com/platform/forge/
Forge SQL storage
data residency docs
information here
Jira UI modifications
here
required by the Jira UI modifications extension point
https://www.atlassian.com/trust/security/security-practices#backups
https://developer.atlassian.com/platform/forge/manifest-reference/permissions/
https://acceleration-engineering.com/privacy