...
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 Google Workspace 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 (Google Drive, 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 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).
|
Usage Analysis | Data is transfered from the end user’s browser to an usage analysis/metrics service, which allows monitoring the usage of our apps and features. This is used to improve the quality of and implement new features. | Data describing the usage context, like specific page sections, button presses, technical context like browser and operating system. A token is generated to identify an unique user than can not be decrypted back to the actual user (Mixpanel, 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. |
Google license distribution | When installing any app through the Google Workspace Marketplace, basic licensing information is distributed. | All data attached to this license is transferred to the Processor. |
...