Delete & Append Actions for Assets in Jira — Security Policy

Security

What this policy covers

This is the security policy for Delete & Append Actions for Assets in Jira, a Forge app that adds delete and append actions for Jira Service Management Assets to the Automation rule editor. It covers the first listed version and every later version published under the same app key, ua.pp.maxpetrov.assets-automation-actions.

The app is written and maintained by one person, Max Petrov. There is no second office, no subcontractor and no sub-processor: the whole of it is the Forge app you install.

Where the app runs, and what leaves your site

The app runs entirely inside Atlassian Forge, on Atlassian's own infrastructure. Its manifest declares no permissions.external block and no remotes entry: every call is requestJira, which Forge excludes from the egress quota, so no data of yours leaves Atlassian.

There is no vendor server to breach, no vendor database to leak and no vendor log to subpoena, because none of the three exists. Authentication is Forge's own; the app holds no credential, no API token and no secret of its own, and it asks you for none.

What the app stores

Nothing, in this version. Forge app storage (storage:app) is declared so a later version could remember a setting without a new permission prompt; no Assets object, no attribute value and no work item content is written anywhere by this version.

What the app can reach, and why

Seven scopes, each the narrowest one that does the job, including three Assets scopes and one delete scope — deletion is this app's stated purpose, not an incidental grant.

How this app is secured

Reporting a vulnerability

Email support@maxpetrov.pp.ua with the words SECURITY REPORT in the subject. The report reaches the person who wrote the code; nobody else reads that mailbox.

One person reads that mailbox — the one who wrote the app — and every request gets a first reply within two business days, Monday to Friday. That is the window a part-time maintainer can hold every week rather than on a good one; most replies land sooner.

Please include the app version, the Jira site you saw it on and the steps to reproduce. A confirmed vulnerability ships as a new Forge version; Atlassian upgrades Forge apps on Cloud itself, so there is no patch for you to install and no action for your administrators to take.

Related documents

The privacy policy covers what the app does and does not process, and the documentation page covers how to use it. Both are linked from the app's Marketplace listing.