Summary: The App runs entirely on Atlassian’s Forge platform and makes no network requests outside Atlassian. It does not send your data to Berkly or to any third party. It does read and store some personal data inside your own Atlassian environment — assignee names and Atlassian account IDs — and it complies with Atlassian’s Personal Data Reporting requirements for that data.
Provider: Berk Karabacak / Berkly (“Berkly”, “we”, “us”) — individual developer
Contact: info@berkly.nl
This policy explains what data the SLA for Jira Software app (the “App”) processes and how. The App is an Atlassian Forge Cloud app installed into your Jira Cloud site by a Jira administrator. It applies only to this App. Berkly’s general privacy page is at berkly.nl/privacy; where the two differ, this page governs the App.
Using the Jira scopes shown at install (read:jira-work, write:jira-work, read:jira-user) and the Atlassian privacy scope report:personal-data, the App reads, for projects that have an SLA policy:
The App does not read attachments, issue descriptions, comment bodies, or user email addresses.
The App stores the following in Atlassian Forge SQL, a database Atlassian provisions per installation and hosts in the region Atlassian assigns to your site — never on Berkly’s own servers:
The App also writes to your Jira site as part of its function: an issue entity property named sla on tracked issues (SLA state, used for JQL search and the issue panel), and — only if you enable them in a policy — a comment when an SLA breaches and a label (sla-breached by default).
The App declares no external network access, has no web-triggers and no third-party integrations. Your data does not leave Atlassian’s infrastructure, and Berkly cannot see your Jira data.
We do not receive, sell, or share your data. Atlassian hosts the Forge platform and Forge SQL as the infrastructure sub-processor; its handling is governed by the Atlassian Trust Center and your Atlassian agreement.
sla issue entity properties, any breach comments and any sla-breached labels remain on your issues until you delete them. A Jira administrator can remove them with Jira’s own tools.The App uses Atlassian Forge’s security model: a sandboxed runtime and Atlassian-managed authentication and storage. Actions that change configuration or a timer require project administrator permission, and this is checked in the App’s backend on every call. We hold no credentials to your site and no copy of your data.
The App stores personal data as defined by the GDPR: assignee display names and Atlassian account IDs. It complies with Atlassian’s Personal Data Reporting requirements: at least every seven days the App reports the account IDs it stores to Atlassian, and deletes or refreshes its copy for accounts that Atlassian reports as closed or changed. Deleted data is replaced in place — the SLA clock and its history are kept, but the person attached to them is not (an assignee becomes “Unassigned”; an actor in the activity log becomes “erased”).
Requests to access, correct or delete personal data can be sent to info@berkly.nl, or fulfilled by uninstalling the App (section 5). For GDPR purposes you (the customer) are the data controller and Berkly acts as a data processor, as described in the Data Processing Addendum.
We may update this policy; material changes will be reflected by a new effective date at the top. Continued use of the App after an update constitutes acceptance.