Skip to main content

Data & Security

Secure File Exchange moves files across your organization's edge, so this page answers what security and compliance teams ask first: where the files are, who can reach them, and when they are gone.

Where your data is​

  • In your organization's Atlassian cloud. Files, link details and the audit log are kept in storage that Atlassian hosts for the app, separate from every other installation.
  • No servers of ours. The app has no servers of its own and sends no data to any outside service: no analytics, no tracking, no outside fonts or content networks.
  • Files travel directly between the outside person's browser and Atlassian's storage.
  • In Jira, the app only comments. It writes nothing to your work items except its comments about received files and locked links.
  • A link can't be guessed. Each link carries a long secret key. The app does not store the key, so it cannot leak from the app's data, and it is kept out of server logs.
  • Nothing to probe. A link that never existed and a link with a wrong key look the same.
  • Not in search engines. The link's page tells search engines not to index it.
  • Limits you choose: an expiry date, an optional password that locks the link after 10 wrong tries, and a download limit per file.
  • Revoking works at once. The outside person loses access the moment someone clicks Revoke link.

Who can reach files​

  • On the work item: anyone who can see the work item sees the panel and its files, as with attachments.
  • Creating, revoking and unlocking links: the people your admin allows, checked on every action. See Who Can Create Links.
  • Through a link: whoever has the link, and the password if it has one, while the link works.
  • The admin pages: Jira administrators only.

Files from outside​

  • Request links can be limited to documents and images, and every link to a largest file size and a number of files. A storage limit caps the total. See Policies.
  • Files always download as files. They never open or run in the browser, on the link's page or in the panel.
  • Files are not scanned for viruses. Treat files from outside people as you would email attachments, and keep your usual endpoint protection in place.

Privacy​

  • Data is kept only as long as needed. Files are deleted after the retention period your admin sets, and audit events after theirs. There is no option to keep either forever.
  • IP addresses are shortened in the audit log: the app never records an outside person's full address.
  • The link's page shows no Jira data beyond the work item's key.
  • Passwords are kept only in a form that cannot be turned back into the password. Nobody can read them later.

Automatic clean-up​

Every hour, the app tidies up according to the policy. It deletes the files of links that ended longer ago than the retention period, deletes audit events older than their retention, removes uploads that were started but never finished, and forgets old links once they have no files left and their audit events are gone.

It also follows what happens in Jira:

In JiraWhat the app does
A work item is deleted, subtasks includedIts links are revoked at once, and its files are deleted within the hour.
A project is moved to the trashIts links are revoked at once. Files stay until the project is deleted for good or retention ends.
A project is deleted for goodIts files are deleted within the hour.
A project is restored from the trashIts links stay revoked. Files already received are still in the panel.
A work item is moved to another projectIts links move with it, and count toward the new project on the Usage page.

What the app asks for when you install it​

  • Read Jira data, to check people's permissions and that work items and projects exist.
  • Write to Jira, only to add its comments about received files and locked links.
  • Read user details, to show names and avatars in the audit log.
  • Store app data: the policy, links, the audit log and the files, all in the storage Atlassian hosts for the app.