Privacy and data
Collision Guard is built on Atlassian Forge and runs entirely on Atlassian's infrastructure. It is eligible for the Runs on Atlassian program: no data leaves your site, and Systematic has no server that receives your data.
What it stores
The app keeps a small store inside your Atlassian site, managed by Forge:
- Settings: whether the app is on, alerts, the portal notice, the claim expiry and excluded project keys.
- Active claims: for each claimed issue, the Atlassian account ID of the person who claimed it and when the claim expires. A claim is deleted when it is released or expires.
- Daily counts: the number of collisions spotted, changed-while-open warnings and claims per project per day, kept for 90 days.
It stores no issue content, no field values, no comments and no customer data.
What travels between browsers
- Presence (who is viewing an issue) is sent between the browsers of people looking at the same issue through Forge Realtime. It contains an Atlassian account ID and whether the tab is in view. It is never stored.
- Change alerts contain the names of the fields that changed and the account ID of the person who changed them, never the values. Each issue's alerts go only to people who have that issue open, over a channel signed for that issue.
What it reads
To show names and photos, and to tell you what changed while you were away, the app reads users' display names and avatars, and an issue's recent history, through Jira's own API. It reads only what the person viewing the issue can already see.
What it never does
- Send data outside Atlassian, to Systematic or to anyone else.
- Track people across issues, or keep a history of who viewed what.
- Use your data for advertising, analytics or training.
Deleting data
Uninstalling Collision Guard removes the app, and Atlassian deletes its stored data under the Forge platform's data retention policy. To ask about your data, write to us at info@systematic.com.lb.