Bulk Attach uploads your files directly to your own Jira site. We never see them. This page explains exactly what the app touches, in plain terms, matched line-for-line to the code that ships.
01Where your files go
When you select a file to attach, it travels from your browser to Atlassian's own Forge platform, then to the Jira REST API, then onto the Jira issue you targeted — on your own site. There is no server operated by us anywhere in that path. The app's backend function set is empty: it does not exist in the deployed app at all, which we verified by removing it, redeploying, and confirming a real upload still completed successfully.
This is not a policy promise layered on top of a different architecture — it is a description of the only architecture that exists.
02What we collect
Nothing. There is no analytics library, no telemetry call, and no logging endpoint in this app that sends data anywhere. We do not know which files you upload, how many, their names, or their contents. We do not know which Jira issues you use the app on.
03Permissions we request
The app asks for two Jira scopes at install. Both are used only to act as you — the currently signed-in user — never with any elevated or administrative access.
| Scope | What it's used for |
|---|---|
read:jira-work |
Reading issues, projects, statuses, and issue types so you can browse and search what to attach to. |
write:jira-work |
The single write operation the app performs —
POST /issue/{key}/attachments — plus removing
an attachment the app itself just created, if you use Undo. |
04Storage & retention
We retain nothing, because nothing passes through infrastructure we control. Forge Storage is not used by this app for file content or metadata. The only place your upload history exists is inside your own Jira site's attachment records, governed by your own Jira administrator's retention settings — not by us.
05Third parties
None. No analytics platform, no error-tracking service, no third-party API of any kind is called by this app. The only network calls it makes are to Atlassian's own Jira REST API, via Atlassian's own Forge bridge.
06What this app does not do
To be unambiguous, Bulk Attach does not:
- Operate a server that your files pass through
- Store file content in Forge Storage or anywhere else we control
- Log file contents, filenames, or FormData bodies
- Delete attachments it did not itself just create
- Read or export data from your Jira site beyond what's shown to you in the app
07Your control
Uninstalling the app (Jira → Apps → Manage apps) removes its access immediately. Attachments it already created remain on your issues as ordinary Jira attachments — indistinguishable from any other — governed entirely by your Jira site from that point on. "Undo This Batch," used before uninstalling, removes exactly the attachments a completed batch created, identified by their exact Jira-assigned IDs, and nothing else.
08Changes to this policy
This is a beta-stage policy. If the app's architecture changes in a way that affects any statement above, this page will be updated to match before that change ships — not after.
09Contact
Questions about this policy or how the app handles your data: abuzarmirza918@gmail.com.