...
- Rule config information:
- Rule name and description
- Rule component config information (e.g. JQL strings used in triggers could contain project keys etc)
- Audit log entries
- We store what you see in the audit log UI basically. Issue keys & ids as well as any changes made to the issue shown on the left hand side in the audit logWe don't
- Issue Details: We store full issue details for the lifetime of the rule execution. (This may change in the future to enable
- This enables us to make our rule execution queue more fault tolerant , but this data would only exist for the lifetime of the rule execution)
- .
- Contact information for users that setup a rule
- We store username, name and e-mail address. This is so we can send these users an e-mail in case a rule doesn't execute due to add-on licensing issues
...
Myself and my co-founder have both worked at Atlassian for 10 years previously and we treat customer privacy and security seriously. We believe in full transparancy transparency around these issues. As far as we are concerned, your data is yours and we do not share your data with any third parties (unless we are legally obligated to do so - however this case has not arisen yet).
...
| Page Properties | ||
|---|---|---|
| ||
|