Last revision date – June 22February 9, 20232024.
(A) Description of processing (processor)
...
Please also keep in mind that Broken Build also processes data that is not “personal data” within the meaning of law (does not relate to identified or identifiable person). Such data could still be is named “End User Data” within the meaning of the Atlassian Marketplace Partner Agreement.
The Provider as the controller may also process other types of personal data received directly from data subjects or from other controllers/processors. You may find more details on such processing in our Privacy Policy.
Details on the data processed
Purpose(s) of processing | Type of data | Nature of the processing | Duration of the processing and retention | Which Service it relates to | |||||
To show velocity charts and implement the App’s functionality |
| Data is collected, analysed; entered into a database; The personal data we process, but do not store:
| Data is organised and/or structured; disclosed to third parties, including transferred for storage to cloud storage services; used to provide services; deleted, erased or destructed. For the list of all sub-processors and their roles and data they access check section (B) below. | Data may be processed | /stored (if applicable) during the term | of EULA and up to 12 months after the termination of EULA. | Cloud App | 2. End User data processed: Anonymized user ID Jira issue standard fields: Issue key Issue status Assignee (anonymized user ID, username, full name, URL to avatar, status) - personal data Sprint ID Created date Reporter (anonymized user ID, username, full name, URL to avatar, status) - personal data Changelog - may contain personal data App (chart) configuration including:
| |
Data is collected, analysed; organised and/or structured; used to provide services. | To proactively monitor App health and fix issues (troubleshooting) |
| Data is collected, analysed; entered into a database; organised and/or structured; disclosed to third parties, including transferred for storage to services that allow monitoring Apps health and troubleshoot; used to provide services; deleted, erased or destructed. | Data may be processed and stored only for 2 7 days following the collection of data. | Cloud and Software AppsApp | ||||
To support End Users, to fix issues in the Apps, answer End User support requests regarding bugs, product usage, feature requests etc. |
2. Personal data related to our Customer:
3. End User data:
43. Non-personal company data, including: company name, license information. 5. App environment data: Atlassian host ID, Jira version, App version. 64. Other information End User provides to us in connection with the support matter (screenshots, screen casts, HAR files etc.). We encourage you to instruct your employees (End Users) not to share sensitive personal data with us, as well as excessive data which we do not need to resolve the issue. | Data is collected, analysed; entered into a database; organised and/or structured; disclosed to third parties, including transferred for storage to aggregate support requests under one company account; used to provide services; deleted, erased or destructed. For the list of all sub-processors and their roles and data they access check section (B) below. | Data will be processed from when the support request was initiated, until we resolve the matter and for 12 months afterwards, to make sure the future requests regarding product usage are properly satisfied, taking into account the history of the requests. However, we aim to delete sensitive attachments such as HAR files within 3 months of the closure of the request. | Cloud and Software Apps App |
(B) List of third party processors
For the detailed list of third party processors please follow the link.
(C) Technical and organizational measures
...