Forge Platform
We designed Drift with security and data privacy in mind. That’s why the app runs entirely on Atlassian Forge and doesn’t connect to external services other than Atlassian APIs.What data we store
- Jira configuration data (custom fields, workflows, schemes, screens)
- AI chat conversations (user prompts and assistant responses)
- AccountId
Where we store the data
All of the data is stored within Forge SQL.Data Egress
There’s no data egress. The app doesn’t connect to external services other than Atlassian APIs.Third-Party Services
The app doesn’t use any third-party services. Drift runs entirely on Atlassian Forge.Does the app support Data Residency?
Yes. All of the data is stored within Forge SQL which supports Data Residency.Why do we need specific permissions
read:jira-user - to be able to display Jira user names e.g. project leads
read:jira-work- to be able to read projects, issue types, fields & statuses
manage:jira-configuration- to be able to read screens and schemes
manage:jira-project- to be able to read project-level configuration (roles, scheme associations)
write:jira-work- to be able to update Jira tickets related to Jira configuration