Versions Compared

Key

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

...

Data Processing Agreement (DPA) pursuant to Art. 28 (3) GDPR between the customer ("Controller") and yasoon GmbH, Julius-Hatry-Straße 1Glücksteinallee 69, 68163 Mannheim, Germany ("Processor") (collectively also "Parties"). 

...

(3) The Processor has appointed as contact person for data protection: Andreas Schmidt, yasoon GmbH, Julius-Hatry-Straße 1Glücksteinallee 69, 68163 Mannheim ; e-mail: datenschutz@yasoon.com

...

The following processes are available no matter which app or apps you use and regardless of whether you use Cloud or On-premise apps. 

Process 

Purpose of processing 

Categories of processing 

Customer support 

Help users from the Controller's organization to resolve usage problems or error situations and thus contribute to the value of the app for the Controller and improvement of the apps and documentation. 

In customer support usage problems or error situations are reported by users from the Controller's organization via the mechanism described in Annex 2

 

In the course of the support process reporters might be asked to provide 

 

Confluence support zips including log files 

 

Templates used for exporting to different formats 

 

Page exports or space exports from Confluence 

 

JIRA support zips including log files 

 

Outlook log files 

Logs from the reporters browser console 

 

Data is provided through the support tool (Jira Service Management, see Annex 3), or in cases where the data provided is too large for that mechanism, we offer to use a data transfer service (Sharepoint, see Annex 3). Reporters can choose to provide their own mechanism of data transfer. 

 

The received data is then analyzed manually or automatically for causes or indicators of reported usage problems or error situations. 

Error tracking 

For error tracking data is transferred from the end user's browser to an error reporting service, which allows analysis of errors without users having to actively report them. This is used to improve the quality of the apps. 

Data describing the error context, like operations invoked, the user interface element clicked, technical context like browser, operating system values are transferred to the error reporting service (Sentry and LogRocket, see Annex 3). 

 

 

Atlassian license distribution 

The apps are only usable with valid licenses. Licenses; i.e. commercial, evaluation and community or academic licenses; are distributed through the Atlassian Marketplace 

All data attached to a license under my.atlassian.com is transferred to the Processor. 

 

The Processor will send informational email when evaluating or using a new app via sub-processor (Mailchimp, see Annex 3). 

 

The Processor might also send transactional email informing receivers about their licenses via sub-processor (Mailchimp, see Annex 3

Microsoft apps license distribution 

When installing any app through the Microsoft AppSource, basic licensing information is distributed. 

All data attached to this license is transferred to the Processor. 

 

The Processor might also send transactional email informing receivers about their licenses via sub-processor (Mailchimp, see Annex 3

 

On-premise & Cloud

The following table describes the data processing of all apps of the Processor. 

...

The Processing is hosted on cloud (AWS, see Annex 3). 

 

 

App 

Purposes of processing 

Categories of processing 

Categories of personal data 

Categories of data subjects 

Microsoft 365 for Jira

Outlook Email for Jira

Outlook Meetings for Jira

Microsoft Teams for Jira & JSM - Smart Connect

Microsoft To Do for Jira 

Connect Microsoft tools with Jira. Optimize Jira with Microsoft features and extend Microsoft tools with Jira functionalities.  

We only store content that has been explicitly created by our apps. The most common data we store are: 

 

  • User / instance settings 

 

  • Metadata mappings between Atlassian & Microsoft objects 

 

  • User login tokens retrieved by OAuth login 

We do not store Jira content (like Jira issues, comments, etc.) or Microsoft content (like email content) on our servers. 

Reports on the 

 

  • Name of the JIRA instance 

 

  • Atlassian account ID 

 

  • Microsoft account ID 

 

The app is unaware of the type of data supplied to it. Example categories of personal data are: 

 

  • Assignees, reporters, participants of issues 

 

  • Field values and changes on fields & comments made by users of JIRA 

 

The Controller must inform the Processor if he processes additional categories of personal data inside Jira or the app. 

Jira user 

 

Microsoft Users 

 

The Controller must inform the Processor if he processes additional categories of data subjects with this app. 

Outlook Calendars for Confluence 

Add configurable Outlook calendars to display Outlook and Jira data in Confluence. 

We only store content that has been explicitly created by our apps. The most common data we store are: 

 

  • User / instance settings 

 

  • Metadata mappings between Atlassian & Microsoft objects 

 

  • User login tokens retrieved by OAuth login 

 

 

Reports on the 

  • Name (URL) of the Confluence instance 

  • Atlassian account ID 

  • Microsoft account ID

The app is unaware of the type of data supplied to it.

Example categories of personal data are: 

 

  • project reports including project collaborators 

  • information on authors of or collaborators on Confluence content and Microsoft content 

 

The Controller must inform the Processor if he processes additional categories of personal data inside Confluence, Jira or the app. 

 

Confluence Users 

 

Microsoft Users 

 

The Controller must inform the Processor if he processes data of additional categories of data subjects inside Confluence, Jira or the app. 

 

 

Annex 2 - Authorized persons, entitled persons, Communication channel

...