App: Attachment Policy Guard for Jira
Publisher: Atesen Software (independent developer, Türkiye)
Contact: support@atesensoftware.com
Last updated: 3 October 2026
The app runs inside your Atlassian Cloud site on the Atlassian Forge platform. When a file is attached to a work item in a project where your policy is on, Jira notifies the app and the app processes:
.pdf). File contents are never stored.When an administrator uses Test a file on the settings page, the browser sends the first 4 KB of the chosen local file to the app so it can show the result. That data is not stored and is not uploaded to Jira.
The app does not read descriptions, comments or other work item fields. It looks up a work item only to show its key in the audit log.
In report mode (the default after installation) the app changes nothing; it only records policy matches. In enforce mode the app removes attachments that break the policy and, if you choose, adds a note to the work item. Removed attachments are deleted by Jira; the app keeps no copy.
All processing and storage happen on Atlassian's Forge platform, inside Atlassian's cloud infrastructure. The app has no servers of its own and sends no data to Atesen Software or to any third party. It makes no outbound network calls. There are no analytics services, no advertising networks, no AI services and no sub-processors.
| Data | Kept for |
|---|---|
| Audit log entries (only for files that matched the policy; allowed files are not recorded) | Deleted automatically 90 days after they are created |
| Processing locks (attachment ID only, to avoid handling the same file twice) | Deleted automatically after 2 days |
| Policy settings | Until you change them or uninstall the app |
| File contents | Never stored |
Uninstalling the app removes the app's storage according to Atlassian's Forge data retention policies.
Once a week the app reports the Atlassian account IDs it stores to Atlassian's personal data reporting API. When Atlassian reports that an account has been closed, the app removes that account ID from its audit log and settings. The app stores no names, email addresses or other profile data.
The app writes application logs for troubleshooting. These logs contain the event type, the decision (allowed or blocked), the action taken and error types. They never contain file names, account IDs, work item keys or note text. Forge logs are stored by Atlassian and are visible to the publisher only through Atlassian's developer tooling, with Atlassian's own retention limits.
For the data processed by this app, your organization is the controller. Atesen Software acts as a processor to the limited extent the app runs on your site. Atlassian is the infrastructure provider; see Atlassian's own privacy policy for how they process data in your cloud site.
To ask about data handled by this app, or to request deletion of app data on your site, write to support@atesensoftware.com.
The app requests only the Atlassian scopes it needs: reading work items and attachments, removing attachments and adding notes, app storage, and personal data reporting. The settings page is a Jira administration page, visible only to Jira administrators.
Material changes to this policy are announced in the app's release notes on the Atlassian Marketplace listing.