Attachment Policy Guard privacy

Where the app runs

Attachment Policy Guard is a Forge app. Its functions and storage run on Atlassian infrastructure provisioned for your Jira site. Atesen Software operates no server or database for the app.

What it connects to

The app calls your Jira site and Atlassian's Personal Data Reporting API. Its manifest declares no external egress permission, analytics or third-party code.

What it reads and stores

• For each new attachment event, it reads the attachment's filename, size, MIME type, project/work item identifiers and uploader account ID. It reads up to the first 4 KB of file content for type detection, using the content in memory only.
• Policy settings are stored in Atlassian Forge storage until changed or removed.
• For matching attachments, an audit record stores the timestamp, attachment ID, file name, size, MIME type, detected type and decision, project and work item IDs/key, uploader account ID, action and processing result.
• The attachment's file contents are not stored. Logs omit filenames, account IDs, work item keys and note text.

Retention and account requests

Audit records are written with a 90-day Forge storage TTL; processing locks store the attachment ID and expire after two days. A weekly task reports stored account IDs to Atlassian's Personal Data Reporting API and handles closed-account erasure. When the app is uninstalled, Atlassian handles removal of its Forge storage under the platform's retention process.

Data residency

The app uses Atlassian-hosted Forge storage associated with your Jira site. Atesen Software has no separate app database or server.