Privacy Policy

This Privacy Policy explains how Project Overview & Status Hub for Jira handles data when it is installed on a Jira Cloud site.

Who provides the app

Project Overview & Status Hub for Jira is provided by Piotr Mederak, ul. Magnolii 1K/2, 05-500 Nowa Wola, Poland. Privacy, security and support questions can be submitted through Mederak Apps Service Desk.

Scope of this policy

This policy covers the app experience inside Jira Cloud and the related public product pages operated by Mederak Apps. It does not replace Atlassian's privacy documentation for Jira Cloud, Atlassian Marketplace, Atlassian accounts or Atlassian Forge infrastructure.

Customers decide which Jira projects, users and groups can use the app through their Atlassian site administration, Jira permissions and app access configuration. If a privacy request concerns Jira content controlled by a customer organization, we may need to coordinate with that organization's Jira administrator.

How the app uses Jira data

The app reads Jira data that the installed app and the current user are allowed to access. It uses that data to generate and maintain project overviews, project pulse information, project radar signals, ownership suggestions, important links, freshness indicators and portfolio views.

The app does not move Jira issues, change Jira issue statuses or make project decisions. Generated summaries and AI-assisted text are intended to be reviewed by authorized users before they are treated as official project context.

Jira data the app may access

• Project metadata, including project identifiers, project keys, names, types, leads and category information.
• Issue metadata and selected issue content needed for overview generation, such as issue keys, summaries, issue types, statuses, status categories, dates, due dates, links and recent activity.
• User information needed for ownership and context, such as display names and Atlassian account identifiers for project leads, roles, assignees, reporters, commenters or last-updated-by information.
• Project roles, project permissions and app-specific global permissions used to decide who can view, generate, refresh or manage overviews.
• Links discovered from Jira activity or saved by users, such as documentation, dashboards, repositories, team channels, environments or support links.

App records stored in Forge

The app may store generated and edited project overviews, suggested people and links, project pulse data, project radar signals, portfolio snapshots, freshness state, access rules, settings, AI usage counters and temporary generation job records in Atlassian Forge app storage for the customer's Jira site.

These records support product functionality, including opening saved project overviews, showing portfolio status, applying access rules, refreshing stale overviews and respecting configured usage limits.

AI-assisted features

The app may use Atlassian-hosted Forge LLM capabilities to help write editable project purpose suggestions and readable radar narratives. The app does not call a vendor-hosted AI provider for these app features.

AI output can be incomplete or inaccurate. The app presents AI-assisted text as a draft, suggestion or summary that should be reviewed by users before it is saved, shared or relied on.

Product analytics

When analytics is configured for the production environment, the app may send sanitized product analytics events to Google Analytics. Analytics events are intended to measure product usage patterns, reliability and feature adoption.

Analytics payloads are designed not to include Jira issue text, issue keys, project names, user display names, email addresses, comments, customer links or saved overview text. Product analytics is separate from the generated project overview content stored in Forge.

Website analytics

This public marketing website may use Google Analytics and Google Ads measurement through the Google tag. Website analytics helps understand visits to public product, documentation, privacy, security and support pages. It does not give Mederak Apps access to customer Jira content or app data inside Jira Cloud.

Retention and deletion

App records are retained while they are needed to provide product functionality, show saved overviews, support portfolio views, keep refresh settings available and troubleshoot customer support requests.

Records may be overwritten by normal app use, removed when the app is uninstalled according to Atlassian platform behavior, or deleted after a support request where technically feasible. Because app records are associated with a customer's Atlassian site, some requests may need confirmation or coordination from the customer's Jira administrator.

Sharing and subprocessors

We do not sell personal data. The app relies on Atlassian to provide Jira Cloud, Forge app hosting, Forge app storage, Forge permissions, Marketplace installation and related platform services. If analytics is configured, Google Analytics may process sanitized telemetry and website measurement data.

See the Subprocessors page for the current subprocessor summary.

Security

The app is designed around Atlassian Forge hosting, Jira authentication, permission-aware access and data minimization. More details are available on the Security Practices and Data Processing Summary pages.

Privacy rights and requests

Depending on applicable law and context, users may have rights to request access, correction, deletion or information about personal data. For privacy questions or requests, contact Mederak Apps Service Desk.

Please include enough context to identify the relevant Atlassian site and app records, but do not send passwords, API tokens, confidential Jira exports or unnecessary customer data in the request.