Data Processing Summary
This page summarizes the data categories processed by Project Overview & Status Hub for Jira.
Purpose of processing
To generate and refresh project overviews, project radar signals and portfolio views; store saved overviews, settings, access rules, refresh state and usage counters; show people, ownership, links, dates, status and freshness information to authorized users; and support troubleshooting, security and product improvement.
Categories of data
- Jira project metadata.
- Jira issue metadata and selected issue content needed for summaries and signals.
- Jira user display names and Atlassian account identifiers.
- Generated overview text, suggested people, suggested links, risk signals and portfolio snapshots.
- App configuration, access rules, refresh settings and usage counters.
- Sanitized product analytics events, if analytics is configured.
Storage locations
Saved overviews, settings, access policies, refresh state, AI usage counters and temporary generation job records may be stored in Atlassian Forge app storage for the customer's Jira site.
External transmission
The app is designed without a separate vendor-hosted product database for project overview content. Product analytics metadata may be sent to Google Analytics if configured, but analytics payloads are designed not to include Atlassian End User Data.
Data minimization
The app is intended to organize project context and signals rather than duplicate full Jira project history. Customers should avoid placing secrets, credentials or highly sensitive regulated information in Jira fields or comments for the purpose of processing it with the app.
Deletion
App data can be overwritten by normal app use or removed by uninstalling the app according to Atlassian platform behavior. Customers needing a specific deletion request should contact Mederak Apps Service Desk.