Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Last revision date – June 22August 4, 2023.

In this Customer Privacy Policy you will find information about how we may process your personal data and what rights you have during the processing when you use our Apps and your company acts as the Customer of Broken Build under the EULA. 

...

To implement the Apps functionality

Agile Reports and Gadgets

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 implement the Apps functionality

Subcomponents for Jira Cloud

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

  • Project ID

  • Project component ID

  • Project version ID

End User data processed:

  • Anonymized user ID

  • Jira project details

  • Jira project components

  • Jira project versions

  • App configuration settings including:

    • Feature enablement status

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. 

...