...
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) |
...
Cloud
The following table describes the data processing of all apps of the Processor.
The General processes that also apply to On-premise and Cloud apps are described above.
The If not stated otherwise, the Processing is hosted on cloud (AWS, see Annex 3).
...
E-Mail to support@lovebyte.codes or request via service desk.
Annex 3 - Sub-processors
A current list of all sub-processors can be accessed under the following link: Trust Center - yasoon. The customer ("Controller") can set up automatic notification of sub-processors changes via e-mail through the "Subscribe to updates" functionIf not stated otherwise, these are the general subprocessors used by lovebyte.codes:
Amazon Web Services | Web hosting
Cloud service, infrastructureGoogle | Customer communication
General communication (mail, chat, web conferences), file storage, uses contact detailsAtlassian Jira | Support, Project Management
Support management, contact detailsHubspot | Newsletters
Marketing, uses contact details after opt-in.
Annex 4 - Region-Specific Terms
...