SolveroX
Metrics Reporter by SolveroX

Privacy Policy for Metrics Reporter

Last updated: 9 September 2026

1. Overview

Metrics Reporter by SolveroX ("the App") is a Jira reporting application built on Atlassian Forge. This Privacy Policy explains how data is accessed, processed, and stored when you use the App. By installing or using the App, you agree to this Privacy Policy.

2. Data We Access and Process

The App processes Jira data that the person running a report is permitted to access through Atlassian Jira APIs. This may include:

  • Jira issues and report-relevant metadata, such as status, timestamps, resolution data, SLA results, satisfaction ratings, request types, priorities, assignees, and selected custom-field values;
  • status-transition history needed to calculate status duration, re-open, and Done-related metrics;
  • the oldest page of issue comments only when needed for the limited first-response-time fallback described in the App; comment content and detailed author information are reduced and are not delivered as report data;
  • project, status, resolution, SLA-field, and custom-field configuration needed to calculate the selected reports; and
  • account identifiers and limited project-role or group-membership metadata when needed to determine whether a comment author is an agent for that first-response fallback.

The App does not retrieve a general Jira user list, unless requested by an authenticated user to generate a specific report. It does not intentionally access passwords, authentication secrets, payment-card data, private authentication tokens, or credentials.

The App does not intentionally perform any "write" operation against your work items or Jira configuration.

3. Personal Data

Some data processed by the App may qualify as personal data, personal identifiers, or personal information under applicable privacy or data-protection laws. This can include Atlassian account identifiers, user-linked issue activity, assignments, comments, satisfaction data, user names, and other Jira data connected to identifiable individuals.

The App relies on the data, permissions, and identifiers made available by Atlassian and your Jira configuration and does not seek to identify people beyond what is needed for reporting and related operational controls.

4. Data Storage and Retention

The App's backend storage is within Atlassian Forge. Completed report rows are delivered to, and retained in memory by, the reporting user's browser for that page session; the App does not create a long-term server-side archive of report results.

To operate the App, Forge storage may retain the following data:

  • tenant field configuration and Jira status-catalogue caches for up to 24 hours;
  • compact report-job state and a per-user active-report lease for up to 75 minutes;
  • per-tenant and per-user usage to keep track of usage quotas for up to 38 days;
  • persistent installation metadata, including application-version and installation/update timing information;
  • limited operational logs, subject to Atlassian's normal operational-log retention. These logs contain bounded operational details and pseudonymous audit references, not report rows, issue keys, JQL, tokens, or raw session identifiers. The logs can be turned off by Jira administrators;
  • Any personal data shown in reports disappears when the browser session ends, unless saved/exported by the user on another medium.

Atlassian Forge and its underlying services may apply their own storage, backup, deletion, and uninstall-retention practices. Those platform-controlled practices can affect how long data remains available after the App's logical retention period. The App does not perform its own archival or external backup of Jira report data.

5. Data Sharing and Transfers

  • The App processes Jira data through Atlassian Jira and Atlassian Forge; it does not intentionally transfer Jira report data to SolveroX-controlled systems or other third parties.
  • The App does not sell or use Jira data for advertising.
  • Atlassian acts as the platform provider for Jira and Forge. Its processing of data is governed by the applicable Atlassian terms and privacy documentation.

6. Security

The App runs entirely on Atlassian Forge and inherits Atlassian's security controls and authentication/authorization.

The App uses the reporting user's Jira permissions when it reads Jira data. A user who can access the App can report on Jira or Jira Service Management work items that their Jira identity is permitted to browse. The App does not add a separate JSM-agent, launch-project, project-type, or customer-organization access restriction; customers should configure Jira project permissions and issue security to enforce any such restriction.

7. Unauthorized Access and Data Exposure Risk

The App is designed to access and process Jira data only as required for authorized reporting functionality and only through Atlassian APIs, Atlassian permissions, Jira configuration, and App functionality.

However, no software, integration, permission model, reporting system, caching system, export process, logging process, cloud service, or API-based application can be guaranteed to be completely free from defects, misconfigurations, vulnerabilities, unauthorized access, over-collection, overexposure, misrouting, data loss, data corruption, or security incidents.

Potential risks may include accidental or unintended access to Jira/work item data, processing of more data than expected, incorrect permission handling, report-generation errors, export errors, caching errors, logging errors, cross-project exposure, cross-user exposure, public disclosure, or other unauthorized disclosure.

SolveroX uses reasonable technical and organizational measures intended to reduce these risks, but SolveroX does not guarantee that such risks can be completely eliminated.

You are responsible for configuring Jira permissions, project access, issue security, user roles, groups, exports, reports, dashboards, and App access controls to reduce the risk of unauthorized access or disclosure, and you accept the risks associated with using the App.

8. Customer Responsibilities

Customers are responsible for ensuring they have the right to process the data made available to the App and for complying with internal policies and applicable laws when using the App.

Jira instances may contain personal data, confidential business information, customer information, operational information, commercially sensitive information, trade secrets, employment-related information, or other sensitive data. You are solely responsible for determining whether the App is appropriate for the type, sensitivity, confidentiality, and regulatory status of the data in your Jira instance before installing, enabling, accessing, or using the App.

The App is not designed for Jira instances that carry sensitive, specially regulated or restricted data unless you have independently determined that such use is lawful, appropriate, authorized, and compatible with your obligations.

You are responsible for configuring Jira permissions, project access, issue security, user roles, groups, exports, reports, dashboards, and App access controls to prevent unauthorized access to confidential, sensitive, personal, regulated, or restricted data.

SolveroX is not responsible for your decision to store confidential, sensitive, personal, regulated, restricted, commercial, or trade-secret data in Jira, or for your decision to make such data available to the App.

9. Changes to This Policy

This Privacy Policy may be updated from time to time. Continued use of the App constitutes acceptance of the updated policy.

10. Contact

For privacy-related questions, contact [email protected].