Privacy Policy — Backlog Ranking for Jira Automation

Last updated: 29 October 2026

This policy explains how Backlog Ranking for Jira Automation ("the app") and its developer handle personal data. The app is published on the Atlassian Marketplace under the acty.dev developer identity by Pavel Krieger ("we", "us"), 89 Rothschild St., Petah Tikva 4933301, Israel. Contact: [email protected].

Who is responsible for what

• When the app runs on your Jira site, it processes data on behalf of your organization. For that processing your organization is the controller and we are the processor. Atlassian hosts the app on its Forge platform as our sub-processor. Our Data Processing Addendum applies to this processing.
• We are the controller of the support requests you send us and of the subscription contact details that Atlassian shares with us.
• We, and not Atlassian, are responsible for our processing of End User Data. Atlassian's own processing is governed by the Atlassian Privacy Policy.

What the app does

The app adds two actions to Jira Automation: "Rank issue at top of backlog" and "Rank issue at bottom of backlog". When a rule runs one of them, the app moves the rule's current work item to the top or the bottom of the backlog of the board set in the action.

What the app processes when a rule runs

Atlassian's Forge platform passes the app:

• the board ID entered by the person who configured the rule;
• the key of the rule's current work item;
• the app's license status on your site;
• the identity of the user who connected the action: Jira Automation runs the action as that user, and Forge may pass the app that user's Atlassian account ID. The app's code does not read, store or log it.

The app then calls Jira's REST APIs as that user, with that user's Jira permissions, to:

• read the board configuration to find the board's rank field;
• check that the work item is in the board backlog;
• read the key of the first or the last work item in the backlog;
• change the rank of the work item;
• read the backlog again to confirm the result.

Of work items, the app requests only their keys; from the board configuration it uses only the ID of the board's rank field. It does not read summaries, descriptions, comments, attachments, other field values or user profiles, and it never sees that user's credentials: Atlassian handles authorization.

Where the app runs and what it stores

The app runs only on Atlassian's Forge platform. It has no servers of its own, sends no requests outside Atlassian and uses no third-party services, analytics, cookies, advertising or AI. It has no database or storage: board IDs, work item keys and Jira responses exist only in memory while an action runs (at most 55 seconds) and are discarded afterwards. Forge aims to run the app in the same location as your Jira site.

Logs

The app writes short fixed lines to Atlassian's Forge logs: that an action started, the HTTP status or error category of each Jira request and whether it was retried (for example "getBacklog 200"), and the result (for example "ranked" or "error LICENSE_INACTIVE"). These lines contain no work item keys, board IDs, names, email addresses or other content from your site. With each line, Atlassian's developer console also shows us platform details such as the site name, invocation ID, app version, environment, license type and edition. We can see these logs for 30 days and only for sites that share app logs with developers; a site admin can turn sharing off in Atlassian Administration. We use logs only to find and fix problems.

Messages in your audit log

If the action cannot finish, it returns a fixed English message that Jira shows in the rule's audit log. These messages contain no data from your site.

Support requests

When you email [email protected], we receive your name, your email address, your message and any attachments. We use them only to answer you and to fix the problem you report. Our email is hosted by Zoho Mail (Zoho Corporation) in the United States. We keep support emails for up to 24 months after the request is closed and then delete them. Please do not send confidential data or screenshots that show personal data.

Information from the Atlassian Marketplace

When your organization starts a trial or a subscription, Atlassian gives us licensing information and may give us the names and email addresses of your site's technical and billing contacts. We use them only to administer the license, and we contact those people only where the law requires it or where they agreed to it or asked us to. We view this information in Atlassian's partner tools and do not copy it to other systems.

Legal bases

Processing on behalf of your organization follows its instructions under the Data Processing Addendum. We handle support requests and Marketplace contact details because we need them to provide the app you subscribed to and because we have a legitimate interest in supporting it (GDPR Article 6(1)(b) and (f)).

Where data is stored

• Data processed by the app: only on Atlassian's platform; nothing is stored.
• Forge logs: on Atlassian's platform, for 30 days.
• Support emails: Zoho Mail, United States.

We work from Israel.

Sharing and sale

We do not sell personal data. We share it only with Atlassian, which hosts the app and runs the Marketplace, with Zoho, which hosts our email, and where the law requires it.

Your rights

Depending on where you live, you can ask us for access to your personal data, its correction or deletion, restriction of or objection to its processing, or a copy in a portable format, and you can complain to a data protection authority. For data the app processes on your Jira site, please contact your organization first: it is the controller, and we help it answer. For support emails and Marketplace contact details, email [email protected]; we answer within one month.

Security

The app asks only for the Jira permissions it needs, works with the permissions of the user who connected the action, keeps no data or credentials, and runs on Atlassian's Forge infrastructure. To report a security issue, email [email protected].

Changes

We update this page when the app's handling of information changes and show the new date at the top.