Legal

Privacy Policy

Easy Workflows for Jira · Effective date: 8 September 2026

Summary: The App runs entirely on Atlassian’s Forge platform and has no external data egress. It does not send your data to Berkly or to any third party, and it stores data only inside your own Atlassian environment. Berkly cannot see your workflow data.

Provider: Berk Karabacak / Berkly (“Berkly”, “we”, “us”) — individual developer
Contact: info@berkly.nl

This policy explains what data the Easy Workflows for Jira 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.

1. Data the App accesses

To do its job, the App reads and (for paid actions you explicitly trigger) writes the following within your Jira site, using the Atlassian-granted scopes shown at install:

• Workflows, workflow schemes, statuses, and their rules — to export, validate, import, compare, snapshot and restore them.
• Projects and issue types — to list targets and to create or assign a scheme when you use “Apply to a project”.
• The acting administrator’s Atlassian account ID — recorded in the History (audit) log to attribute each action.
• Your Jira permissions — checked so that only Jira admins can use administrative functions.

The App does not access issue content, comments, attachments, user emails, or any personal data beyond the acting admin’s account ID used for audit attribution.

2. Data the App stores

The App stores the following in Atlassian Forge app storage (hosted by Atlassian within your instance’s region), never on our own servers:

• Workflow snapshots (point-in-time backup copies of workflow definitions you or the schedule create).
• An audit log (History) of actions the App performed, including timestamp, action type, target, and the acting admin’s account ID.
• App configuration (for example whether daily backups are enabled, and the last run summary).

3. Data egress — none

The App has no web-trigger, no outbound network requests, and no third-party integrations. Workflow definitions, snapshots and audit records never leave Atlassian’s infrastructure. Exporting a bundle to move it to another site is done by you copying the JSON shown on screen — the App itself transmits nothing externally. The App is eligible for Atlassian’s Runs on Atlassian program.

4. Sharing and sub-processors

We do not receive, sell, or share your data. Atlassian hosts the Forge platform and app storage as the infrastructure sub-processor; their handling is governed by the Atlassian Trust Center and your Atlassian agreement.

5. Retention and deletion

• Snapshots are retained until deleted by an admin or aged out by the per-workflow retention cap (newest N kept).
• Audit-log and configuration data persist for the life of the installation.
• Uninstalling the App removes its Forge app storage, deleting snapshots, audit records and configuration.

6. Security

Access to administrative functions is restricted to Jira administrators and enforced server-side on every action. The App follows Atlassian Forge’s security model (sandboxed runtime, Atlassian-managed storage and authentication). We hold no credentials or copies of your data.

7. Your rights

Because your data stays within your Atlassian instance and under your administrators’ control, requests to access, export, or delete data are fulfilled through your own Jira admin tools (and, for full removal, by uninstalling the App). For questions, contact info@berkly.nl.

8. Changes

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.