What the app reads, what it keeps, and what it never does.

The app reads the following from your Jira Cloud site, using only the read-only permissions granted at installation:

• User directory data: account ID, active status and account type while a scan runs; display name and email address (where the user's Atlassian profile makes it visible to apps) only when a report is displayed or exported. None of these except the account ID are written to storage.
• Application role and group membership: which product licensing groups each user belongs to, and Atlassian's per-product seat counts.
• Issue activity metadata: for recently-updated issues, the author and timestamp of changelog entries, comments and work logs, and the creator and reporter. The app reads this to determine who was active and when. It does not read issue descriptions, comment text, attachments or custom field values.

The app stores, in Forge's Atlassian-hosted storage within your site's data residency region:

• Scan progress (cursors, counters, timestamps).
• For each dormant user: the Atlassian account ID, product membership, and a dormancy band derived by the app. Display names and email addresses are not stored; they are read from Jira each time you open or export the report.

The app never stores issue content, comment text, work log descriptions, attachments, or any text authored by your users. Every stored value is regenerated by each scan and is deleted when the app is uninstalled.

• It does not deactivate, modify or delete users, and holds no permission that could.
• It does not change any setting, issue, or configuration on your site.
• It does not use your data for any purpose other than producing the report you request.
• It does not sell, share, or transmit your data to any third party.