Customer & Organization Export for JSM (the “App”) is an Atlassian Forge app for Jira Service Management Cloud. It lets you export a project’s Customers and Organizations to a CSV file. This policy explains, plainly, what personal data the App touches, how it processes it, and — importantly — that it does not store that data anywhere.
In short: the App has no server, no database, and no backend function of its own. When you click Export, your own browser calls Jira’s REST API directly, using your own Jira session, and builds the CSV file locally on your device. The App does process personal data (Customer names, email addresses, and Organization membership) in order to build that CSV — but it never stores that data, never sends it to any server operated by the vendor, and never sends it anywhere except back to your own computer as a downloaded file.
The App adds one screen inside Jira: choose a Jira Service Management project, click Export CSV, and receive a file containing that project’s Customers and Organizations, with columns Customer Name, Email, Organization Name, and Organization ID. A Customer who belongs to more than one Organization appears once per Organization, so no membership is lost; a Customer with no Organization still appears, with those two columns left blank.
To build the CSV, the App reads, for the project you select:
This is personal data, and the App does process it — it is read from Jira, held briefly in your browser’s memory while the CSV is assembled, and written into the file your browser saves to your own device. We are explicit about this: the App does not avoid handling personal data, it avoids storing it anywhere outside your own browser and your own downloaded file.
@forge/bridge library) using your own logged-in session. No request passes through infrastructure operated by the vendor.All processing happens in two places: (1) Atlassian’s own Jira Service Management REST API, which you are already a customer of, and (2) your own web browser, running on your own device. The vendor operates no server, so there is no separate infrastructure to introduce a different data residency than your own Atlassian Cloud site already has.
| Scope | Purpose |
|---|---|
read:servicedesk-request | List the Jira Service Management projects (service desks) available to you. |
manage:servicedesk-customer | Read a project’s Customers and Organizations. This scope is required by Atlassian’s own Customer/Organization REST API for this read operation; there is no narrower scope available for it. |
These are the only scopes the App requests. Both are used solely to read the data you asked to export; the App cannot create, edit, or delete anything in Jira.
None. The App integrates no third-party service, analytics vendor, email provider, or storage provider of its own. The only infrastructure involved is Atlassian’s own Forge platform and Jira REST API, already covered by Atlassian’s own privacy and security commitments to you.
Because the App stores nothing after your browser tab is closed, there is no App-held personal data for us to access, export, or delete on your behalf. The Customer and Organization data that ends up in a downloaded CSV file is retained only on your own device, under your own organization’s existing data-handling policies — the same as if you had exported it by any other means. If you believe the App has behaved differently from what this policy describes, contact us using the details below and we will investigate promptly.
If this policy changes in a way that affects how the App handles data, we will update the effective date above and, for material changes, note it in the App’s Atlassian Marketplace listing.
Questions about this policy or the App’s data handling: support@asunoki.jp.