GDPR and Access to Personal Information by WorklogPRO

WorklogPRO for Jira Cloud is an Atlassian Forge app. This has a significant importance regarding to security for a Jira Cloud app. Old cloud apps run on vendors' own servers and store data in their own databases. However, Forge apps are more secure and don't require vendors to use their own servers. We don't have direct access to your worklogs or other Jira data.

When you install "WorklogPRO for Jira Cloud," Jira will request permissions before sharing any data with WorklogPRO. On the consent screen, you'll see that the app can access user and issue information and share data with some external domains. Each permission and external domains we will be explained below. We only use issue and user data to display timesheet reports and we don't have access to this data outside of the app.

While the app is running, we may log issue IDs, user IDs, and worklog IDs or IDs for any related entities (which we don't consider personal data). We don’t log worklog content, issue content, or user information. You have full control over our log access, and you can disable our log access in the administration section of your Jira. You can also view the log content yourself.

The only reason this app doesn't have "Runs on Atlassian" badge is because of the GraphQL API provided. To provide this functionality we are using a webtrigger which allows data to be retrieved to external apps. This endpoint is for your own integration purposes and not active until you create your API Token and use it to integrate your 3rd party apps. Even in this scenario, you are the only one who knows the token and can access the data. We can't access you data using this GraphQL or in any other way.

We are collecting some analytics information and you can turn this off whenever you want. We don't collect any personal information or any data which belongs to you. You can find more information about analytics data collection and how to disable it as explained here.