Privacy policy: Project Export for Jira

Last updated 10 November 2026

This policy covers Project Export, an app for Jira Cloud sold on the Atlassian Marketplace. The app is made by Tran Quang Hieu, a sole proprietor in Vietnam, trading as Ops Fixes (opsfixes.com). Contact: support@opsfixes.com. The policy for the opsfixes.com website itself is at opsfixes.com/privacy.

The short version

• The app runs entirely on Atlassian's Forge platform and is eligible for Atlassian's "Runs on Atlassian" programme. It has no servers of its own and no permission to send data outside Atlassian.
• We, the developer, can't see your work items, attachments or export files. They stay in your Jira site and in the app's storage on Atlassian, in the same data residency location as your site.
• Export files are deleted 7 days after an export finishes, or earlier when an admin clicks Delete.

What the app reads

When a project admin clicks Export project, the app reads that one project through Jira's REST API, acting as that admin (it can only read what the admin can read): work items with their fields, history, comments, worklogs, watchers and attachments, and the project's setup (components, versions, statuses, fields, custom field options, workflows, link types, boards and sprints). This can include personal data that is in your Jira, such as the names of people who wrote comments. It reads nothing from other projects.

What the app stores, where, and for how long

Data	Where	Kept
The export file (zip parts) with the project's data	Forge Object Store, on Atlassian	7 days after the export finishes, or until an admin deletes it. Atlassian keeps deleted objects recoverable for up to 30 days for disaster recovery.
Export records: project key, dates, counts, sizes, status, and short error notes	Forge key-value storage, on Atlassian	While the app is installed (the page lists the last 10 per project)
The Atlassian account ID of the admin who started an export (needed to run the export as that person)	Same export record	Removed when the export's files expire, or as soon as Atlassian reports the account closed. Names are looked up live and never stored.

When the app is uninstalled, Atlassian deletes the app's storage on its schedule for Forge apps (data can be recovered for a short period in case the app is reinstalled).

Logs

Forge keeps the app's technical logs: job IDs, counts, timings, sizes and error messages. They don't contain work item content, attachments or credentials; an error message may name a work item key. Your site admin controls whether these logs are shared with us.

Who can access the data

• Only people with the Administer Projects permission for that project, or Jira admins, can start, see, download or delete its exports.
• Download links are short-lived (1 hour) links issued by Atlassian to the signed-in admin.
• We don't have access to your site or to the app's storage, and we don't use sub-processors besides Atlassian. We don't sell or share data, and the app has no analytics or tracking.

Roles under data protection law

For the data in your Jira site and in your exports, your organisation is the controller. The app processes it only to make the export you ask for, on Atlassian's infrastructure. To ask about or exercise data protection rights, write to support@opsfixes.com; for data held in Jira itself, contact your Jira admin or Atlassian.

Changes

If the app starts handling data differently, we'll update this page before that version ships, and changes that need new permissions are shown to your admin by Atlassian before they take effect.