Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Current »

Overview

This document is in addition to the 55 Degrees Privacy document and the Customer Agreements for Jira Cloud or OnPrem products (including the DPA) provided by 55 Degrees. It explains how ActionableAgile for Jira stores the data it captures. This document will be updated as new features are added to ActionableAgile for Jira.

Data storage terms and data storage location

  • ActionableAgile for Jira retrieves data from the customer Jira instance (for example yourinstance.atlassian.net) using the Atlassian provided rest API. Once retrieved, a subset data is stored in the local browser using DOM localStorage in order to improve any future data retrievals. The end-user can at any time empty the localStorage through the ActionableAgile User Interface.

  • Jira Cloud: In addition to this, 55 Degrees, may in the future, maintain a database that contains basic information about the instances using our preferred vendors (see below). If this occurs - we’ll inform you of this through release notes and this page.

  • At no point is any customer-specific data retrieved and stored on any 55 Degrees servers.

  • We store user preferences on the current user’s user object in the Jira instance.

  • Please read the product documentation for further details.

Preferred Vendors

Jira Cloud: At this time, 55 Degrees utilizes two vendors to host the functionality within ActionableAgile for Jira:

  • DigitalOcean (utilizing the Frankfurt and Amsterdam DataCenters)

  • Amazon AWS (S3 Global)

Jira Server/ Jira Data Center: All actions happen on your local instance and the user's browser.

Logging

Jira Cloud: We make use of sentry.io to collect any javascript errors in the browser. For more details about their security&legal statements - please see https://docs.sentry.io/product/security/

Jira Server/ Jira Data Center: At this time. we do not collect any logs in an automated fashion and rely on the user to assist in any troubleshooting.

Product Analytics

Jira Cloud: We make use of http://mixpanel.com to gather anonymous product usage analytics. All the data collected is subject to the terms in https://www.55degrees.se/agreement-cloud-products. The information collected is related to the type, volume, and frequency of feature usage within the product. We use this information to understand better how ActionableAgile is used so that we can improve the product in future releases. If you have any questions or want more information about this, please reach out to us at support@55degrees.se.

Jira Server/ Jira Data Center: At this time, we do not collect product usage analytics.

Account removal and data retention

This section explains how a customer can close an account and completely remove their data from our service.

  • Jira Cloud: A customer can uninstall the ActionableAgile for Jira app from their Jira instance. Any data stored on the user object will continue to persist on the user entity in Jira Cloud’s database.

  • Jira DataCenter and Jira Server: There is currently no database usage.

  • Any data stored in the browser's localStorage (for performance reasons) will persist in the browser until the user enters into the ActionableAgile app, at which point it may be expired due to timeliness OR the end-user may choose to clear the localStorage manually.

  • At any time, the end-user may choose to use the browser controls to clear the localStorage outside of ActionableAgile for Jira's user interface.

  • Please read the product documentation for further details.

Data portability

This section explains if and how a customer can extract their data from your service.

  • The ActionableAgile for Jira app does not create any new data but rather analyses and visualizes it. Because of this, there is no data stored on our services.

  • Please read the product documentation for further details.

Application and infrastructure security

This section explains what security measures we've taken in our application and infrastructure.

  • The 55 Degrees support team accesses app data only for purposes of application health monitoring, performing system updates, application maintenance, and/or upon customer request for support purposes.

  • Only authorized 55 Degrees employees to have access to customer data.

  • Customers are responsible for maintaining the security of their own Confluence and JIRA Cloud login information.

  • Communication between the Cloud products and the 55 Degrees servers is done using web requests. All web requests are digitally signed, authenticated, and authorized.

  • 55 Degrees' servers are only accessible through secure protocols (e.g. https and/or ssh).

  • Please read the product documentation for further details.

Security disclosure

This section explains how and under what circumstances we notify our customers about security breaches or vulnerabilities and indicate how a user or security researcher should disclose a vulnerability found in our add-on to us.

  • Security breaches or vulnerabilities with the proposed solution of the problem are published on the Security Advisories page in our documentation.

  • Critical vulnerabilities are communicated out to technical contacts of the affected products and to anyone subscribed to the Alerts, Advisories, & Policy Updates mailing list. You can sign up for this mailing list at https://55degrees.se/subscribe.

  • Customers can report security breaches or vulnerabilities via email to support@55degrees.se.

  • Please read the product documentation for further details.

Privacy

Data collected during the use of our add-on will not be shared with third parties except if required by law.

  • No labels