...
Additional information for Annex 1
App:
...
Assets Owner for Jira
Purposes of processing | Categories of processing | Categories of personal data | Categories of data subjects |
Import Objects/Assets from Microsoft Azure AD/Entra ID into Connecting Jira Servicemanagement Assets with the Profile Menu of each user. | We store Microsoft Azure AD/Entra IDs Tenant ID, Client ID and Client Secret Jira Servicemanagement administrator email, api token, as well as a encryption string and visibility settings, exclusively in the Atlassian Storage API. We do not store any data on our servers.App Properties and in a AWS DynamoDB instance. We process Data from Microsoft Azure AD/Entra IDJira Servicemanagement:
We do not store this data after processing and importing the data, except this data into the Jira Servicemanagement Assetsfrom the Visibility Settings. | The App does not store any Assets or Information (except into the Atlassian Storage API, the Tenant ID, Client ID and Client SecretApp Properties and in a AWS DynamoDB instance, a email, api token, encryption string and visibility settings). The App processes Data, such as Users, Groups, Devices and their relations. Microsoft Azure AD/Entra ID… …User …Groups …Devices Assets, Asset-Schemas and Asset-Object-Types. The Controller must inform the Processor if he processes additional categories of personal data inside Jira or the app. |
The Controller must inform the Processor if he processes additional categories of personal data inside Jira or the app. |