Content Comparison

To implement the Apps functionality

Advanced Velocity Chart

Role of Broken Build: processor

Which Service it relates to: Cloud Apps 

Processing we perform

Data we process

Legal basis for the processing

Implement the App’s functionality.

Although data shared to achieve that purpose may include personal data, accessing personal data is not our main objective. In some instances, access to personal data is purely incidental and therefore very limited in practice to:

End User data stored (does not contain personal data):

• Anonymized user ID

• Jira issue standard fields:

  • Issue key

  • Issue type

  • Issue status

End User data processed:

• Anonymized user ID

• Jira issue standard fields:

  • Issue key

  • Issue type

  • 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:

  • Chart title

  • JQL filter - may contain personal data

Not applicable

(data is provided to perform obligations before the Customer under the EULA, as described in the DPA)

Data retention period: data may be processed and stored during the term of EULA and up to 12 months after the termination of EULA. 

Sub-processors engaged:

• AWS Elastic Kubernetes Service (AWS EKS) (Amazon Web Services, Inc.) is aimed to store data necessary for the App to properly function.

• Amazon RDS for MySQL(Amazon Web Services, Inc.) is also aimed to store data necessary for the App to properly function.

To proactively monitor App health and fix issues

Role of Broken Build: processor

Which Service it relates to: Cloud Apps 

Processing we perform

Data we process

Legal basis for the processing

Proactively monitor App health and fix issues (troubleshooting)

End User data processed and stored: 

• Anonymized user ID

• App (chart) configuration excluding any data that may potentially be deemed personal data

Not applicable

(data is provided to perform obligations before the Customer under the EULA, as described in the DPA)

Data retention period:

Data may be processed and stored only for 2 days following the collection of data. 

Sub-processors engaged:

• Logz.io (LogsHero Ltd.) is aimed to monitor Apps health and troubleshoot. 

To support End Users, to fix issues in the Apps

Role of Broken Build: processor

Which Service it relates to: Cloud

Apps 

Nature and purpose(s) of processing

Data we process

Legal basis for the processing (if applicable)

Answer End Users support requests regarding bugs, product usage, feature requests etc.

The data is both processed and stored:

1. End User’s personal data (if and as provided by data subject):

• Email address;

• Full name.

2. Personal data related to our Customer:

• the Customer’s name and/or email (if the Customer is an individual);

• Contact data (email address, full name);

3. End User data: 

• Anonymized user ID

• device and browser information (IP address, browser, locale, operating system)

4. Non-personal company data, including: company name, license information, Atlassian host ID, Jira version, App version.

5. App environment data: Atlassian host ID, Jira version, App version.

6. Other information you provide to us in connection with the support matter (screenshots, screen casts, HAR files etc.).

We encourage you not to share sensitive personal data with us, as well as excessive data which we do not need to resolve your issue.

Not applicable

(data is provided to perform obligations before the Customer under the EULA, as described in the DPA)

Data retention period:

We will store the data from when the support request was initiated, until we resolve the matter. We intend to store your personal data for up to 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 your request. 

Sub-processors engaged:

1. Atlassian Corporation Plc (Jira Service Desk/Management) (Atlassian Pty Ltd) allows us to manage customer support requests.

2. Segment (Twilio Inc.) captures App usage events.

3. Intercom, Inc. also allows us to manage customer support requests.

4. Calendly Inc. is designed to easily book the meeting with us. 

5. Google Meet, Google Calendar (Google, Inc.) help to book and conduct online meetings with you.

6. Atlas CRM (Avisi Apps B.V.) is aimed to aggregate support requests under one company account, so that to enrich our support context and provide better support.

To enter into an agreement with the Customer and administer our relationship

Role of Broken Build: 

controller

Which App it relates to:

Cloud

Apps

Processing we perform

Data we process

Legal basis for the processing

Enter into an agreement with the Customer under the EULA, including any negotiations between us in order to conclude the agreement, as covered by the Atlassian Marketplace Partner Agreement.

Administer our relationship with the Customer, i.e. send information about our terms and other information that the Customer needs, as allowed by the Atlassian Marketplace Partner Agreement.

The data is both processed and stored:

1. Non-personal company data, including: company name, license information, Atlassian host ID.

1. Personal data related to our Customer:

• the Customer’s name (if the Customer is an individual);

• Technical contact data (email address, full name);

• Billing contact data  (email address, full name).

Entering into and performance of a contract

(Article 6.1(b) GDPR).

Data retention period:

We will store the data during the term of EULA and for up to 12 months afterwards.

Sub-processors engaged:

1. Atlassian Marketplace partner admin portal (Atlassian Pty Ltd) helps us to administer relationships with the Customer and provides us with licensing information.

2. Chart Mogul (Chart Mogul GmbH & Co) is a financial analytics service we use to ensure financial efficiency of our agreements.

3. Active Campaign, Inc. allows us to send updates, information about our products and other marketing we deem interesting to the Customer (see our Marketing Privacy Policy).

To improve our Apps

Role of Broken Build: controller

Which Service it relates to: Cloud

Apps 

Processing we perform

Data we process

Legal basis for the processing

Analyze the Apps to optimize user experience.

Test and develop new features and functions.

The data is both processed and stored:

1. End User’s personal data (if and as provided by data subject):

• Email address;

• Full name.

2. End user data: 

• Anonymized user ID

• device and browser information (IP address, browser, locale, operating system)

3. Non-personal company data, including: company name, license information.

4. App environment data:

• Atlassian host ID

• Jira version

• App version

5. Personal data related to our Customer:

• the Customer’s name (if the Customer is an individual)

• Technical contact data (email address, full name);

• Billing contact data (email address,  full name).

6. End User requests and feedback on improving the Apps.

We encourage you not to share sensitive personal data with us, as well as excessive data which we do not need to resolve your issue.

Consent 

(Article 6.1(a) GDPR)

Legitimate interest 

(Article 6.1(f) GDPR).

Data retention period:

We will retain your data related to our Customer during the term of EULA and for up to 12 months afterwards. End User data will be deleted 12 months after the last request/communication of the End User. 

Sub-processors engaged:

1. Atlassian Corporation Plc (Jira Service Desk/Management) (Atlassian Pty Ltd) allows us to manage customer support requests.

2. Roadmap portal for Jira Service Desk by Amoeboids (Amoeboids Technologies Private Limited) is aimed to let us know about your interest when you submit, vote and comment for features. 

3. Segment (Twilio Inc.) captures App usage events.

4. Amplitude, Inc. helps us to improve your usage experience and functionality of the App.

5. Journy.io BV ensures we could monitor the health of customers (both at company and user levels).

6. Intercom, Inc. allows us to communicate with End Users regarding the feedback, product updates, and onboarding materials.

7. Calendly Inc. is designed to easily book the meeting with us.

8. Google Meet, Google Calendar (Google, Inc.) help to book and conduct online meetings with you.

9. Atlas CRM (Avisi Apps B.V.) helps us to communicate with End Users regarding the feedback, product updates, customer support cases.