Privacy Policy
Delete & Append Actions for Assets adds three actions to the Jira Automation rule editor: delete one or more Assets objects, append values to an Assets attribute, and append Assets objects to a work item's Assets field. The app runs only when a rule you built calls one of these actions. Questions about this policy go to support@maxpetrov.pp.ua, read by the person who wrote the app.
The app runs entirely on Atlassian's own infrastructure using Atlassian Forge. Its manifest declares no permissions.external block and no remote hostname: every call the app makes is requestJira, routed by Forge itself to your own Jira and Assets REST API. Nothing the app reads or writes leaves Atlassian's infrastructure, and the vendor operates no server any of your data passes through.
The app stores no personal data, and in this version it stores nothing at all. Each run reads and writes only the Assets objects, attributes and work-item fields the rule names, for the length of that single automation run; nothing is kept afterwards. The app declares Forge app storage (storage:app) so a later version could remember a setting without your administrator approving a new permission; the current version writes nothing to it.
The app performs no analytics, telemetry or tracking of any kind.
Scope | What it is used for |
|---|---|
| Reads the work item an append-field action targets, and Jira's field list, so a field name can be matched to its id. |
| Writes the merged list of Assets objects back onto a work item's Assets field when the append-field action adds one or more objects. |
| Looks up the site's Assets workspace id at the start of every run. |
| Resolves Assets objects by key or by an AQL query you wrote, and reads an object's current attributes before any delete or append. |
| Writes the merged value list back onto an Assets attribute when the append-attribute action adds one or more values. |
| Deletes the Assets objects the delete action names. This is that action's whole purpose. |
| Declared for a later version; the current version writes nothing. |
The app reads no user directory and asks for no user-profile scope: it holds no account id, no display name and no email address of anyone on your site, beyond the identity of the person who connected the rule, which Forge itself manages.
Every call is made as the person who connected the rule to the app, through their own Jira and Assets permissions. The app can reach only an object, attribute or work item that person could already reach, and a call Jira or Assets refuses is shown as that refusal — a named error in the rule's audit log — rather than worked around.
The app deletes and writes Assets data, and writes to a work item's Assets field: that is its stated purpose. It deletes only the objects a rule's delete action names, it appends only to the attribute or field a rule's append action names, and every one of those changes is written as a plain-language line, naming the objects and counts involved, to that rule's audit log. The app edits no other Jira or Assets content, and ships no create action: it only deletes and appends to what the rule points it at.
The vendor shares nothing with anybody, because the vendor receives nothing: every read and write happens between your site and Atlassian's own Assets and Jira REST API, inside a single automation run. There are no sub-processors, no third-party services, no advertising and no data sale. Nothing is retained after a run completes. Uninstalling the app removes its installation and the three actions from the rule editor.
Because the app stores no personal data, there is nothing to export, rectify or erase on request. A request under GDPR, UK GDPR or CCPA can be sent to the address below and will be answered with this same statement and with whatever evidence the requester asks for.
Report a suspected vulnerability to support@maxpetrov.pp.ua with the words SECURITY REPORT in the subject. Reports are acknowledged and triaged by the person who wrote the code. A fix ships as a new Forge version; Forge apps on Atlassian cloud are upgraded by Atlassian, so there is no customer-side patch step. The security policy is a separate page linked from the app's Marketplace listing.
Max Petrov — support@maxpetrov.pp.ua. One address, read by the person who wrote the app.