Privacy Policy — Cross-Project Reports for Jira

This Privacy Policy describes how the Atlassian Marketplace app Cross-Project Reports for Jira (the “App”), published by Midgaard, handles data when you install and use it on a Jira Cloud site. The App is built on Atlassian Forge, which fundamentally shapes what data we process and where it lives.

Summary

• The App runs entirely on Atlassian-hosted infrastructure (Forge runtime and Forge Storage). No application data is sent to, processed by, or stored on any Midgaard-controlled server.
• We do not collect, transmit, log, or analyze any personal data outside your Atlassian instance.
• The App reads issue and project data from your Jira instance using the permissions you grant at install. It does this on your behalf (asUser), so it can only see what you can see.
• Saved report configurations are stored in Atlassian’s per-tenant Forge Storage, scoped to your account, and are deleted when you uninstall the App.

What data the App accesses

To produce reports, the App reads the following from your Jira Cloud site through official Atlassian APIs:

• Projects you have permission to view, and their metadata (key, name, avatar).
• Issues returned by your selected projects and filters: key, summary, status, assignee, reporter, issue type, priority, sprint, story-point estimate, created/updated timestamps, and labels.
• Issue types, statuses, labels, and sprints available in your selected projects.
• Users (display name, avatar, Atlassian account ID) returned by the user-search endpoint when you use the assignee or reporter filter.
• Your own Atlassian account ID (used as the storage key for your saved reports).

All access uses your current user’s permissions (Forge’s asUser mechanism). The App cannot read data you cannot read.

What data the App stores

The App stores saved report configurations in Forge Storage. Each stored record contains:

• A unique id and the name you chose for the report.
• The configuration of the report: project keys, filter values (issue types, statuses, labels, sprint ids, assignee/reporter Atlassian account IDs, date range), chart type, group-by dimension, table column selection, and metric (count or story points).
• The creation timestamp.

Saved reports are stored under a key that includes your Atlassian account ID, so only you can see, load, and delete your own saved reports. Forge Storage is operated by Atlassian, is logically isolated per tenant, and lives within your Atlassian instance’s data boundary.

We do not store issue contents, user profiles, audit logs, or any analytics data.

What data the App does not do

• The App does not send data to Midgaard or any third party. There is no backend operated by Midgaard that the App talks to.
• The App does not place tracking pixels, analytics scripts, or cookies in the iframe.
• The App does not contact external services for advertising or marketing.
• The App does not cache data outside of Atlassian Forge’s own runtime.

Security & data protection

• Hosting & isolation. The App runs on Atlassian Forge, a managed platform on Atlassian-hosted infrastructure. There is no Midgaard-operated server, database, or network. App data lives in Forge Storage, logically isolated per Atlassian tenant.
• Encryption. All communication uses TLS (HTTPS). Data at rest in Forge Storage is encrypted by Atlassian. Midgaard never holds a separate copy of your data.
• Access control & least privilege. Every Jira call is made with the requesting user’s own permissions (Forge’s asUser), so the App can never reach data the user couldn’t. The App requests read-only Jira scopes plus app storage; it cannot create, modify, or delete any Jira data.
• No data egress. The App makes no outbound calls to any non-Atlassian host. No third party receives your data.
• Secure development. Every change is gated in CI by type checking, automated tests, dependency vulnerability scanning (SCA), and static analysis (SAST); a CycloneDX software bill of materials is produced per build. Credentials, tokens, and personal data are never written to logs.
• Vulnerability management & incident response. Report security issues to piotr@midgaard.software. We triage with CVSS and remediate within the timelines of Atlassian’s Marketplace Security Bug Fix Policy, notifying affected customers and Atlassian for critical issues per Atlassian’s guidelines.

Data retention

Saved reports persist in Forge Storage until you delete them or until the App is uninstalled. When the App is uninstalled, Atlassian removes all of its Forge Storage records as part of the uninstall lifecycle.

Transient query results (e.g. the issues returned by a report run) are held only in your browser for the duration of the session and are not persisted by the App.

CSV export

When you click Export CSV, the App generates the file in your browser from data already returned by the report query and triggers a download. The file does not pass through any Midgaard infrastructure. What you do with the downloaded file is governed by your organization’s own data-handling policies.

Sub-processors

The App relies on Atlassian as the sole sub-processor: the runtime, storage, and all data access are provided by Atlassian Forge. See Atlassian’s Privacy Policy for details on how they process data on your behalf.

GDPR and Atlassian data residency

Because data is not transmitted outside Atlassian, the App inherits whatever data residency and GDPR-related controls Atlassian provides for your instance. The App itself introduces no additional cross-border data flow.

Permissions requested at install

• read:jira-work, read:jira-user, read:project:jira, read:board-scope:jira-software, read:sprint:jira-software — to fetch the projects, issues, users, boards, and sprints needed to compose the report.
• storage:app — to persist your saved report configurations in Forge Storage.

The App requests no write scopes on Jira. It cannot create, modify, or delete any of your Jira issues, projects, sprints, or users.

Your rights

Because the App does not control or store data outside Atlassian, requests related to access, correction, or deletion of personal data are best directed to Atlassian (for underlying Jira data) or handled by deleting saved reports / uninstalling the App for App-stored data. For any question that requires our involvement, contact us at the address below and we will respond within a reasonable time.

Changes to this policy

We may update this Privacy Policy as the App evolves. Changes will be posted at this URL with a revised effective date. Continued use of the App after changes constitutes acceptance.

Contact

Questions about this Privacy Policy or the App’s data handling:
piotr@midgaard.software