QuantMatrix Intelligence

Privacy: Cost-to-Serve Signals for Jira Service Management

This notice explains what information the Cost-to-Serve application processes and which data it uses when a Jira user requests analysis.

Information processed

When a user initiates a scan, the app reads a bounded set of Jira issues visible to that user. This can include issue key, summary, issue type, priority, timestamps, labels and timespent. Issue summaries may contain personal or confidential customer content.

Purpose

Display recorded hours and incomplete time-entry coverage by Jira issue type; provide optional arithmetic estimates of recorded-labor costs based only on hours visible in Jira and an hourly rate entered for that scan. It does not infer missing worklogs.

Data transfers and storage

The application uses the Jira read:jira-work permission, calls Jira asUser, has no configured remotes or vendor-side database, and does not send customer data to third-party AI or analytics destinations. The hourly rate is not saved by app code. Atlassian platform services may operate logs under their own policies. The app does not write to Jira issues.

Retention and deletion

The application does not contain a code path that stores the fetched Jira issue contents or user rate in an app database. Results remain in the current client session; CSV exports are downloaded by the user and thereafter follow the customer's local data-retention rules. The customer controls original Jira data using Jira permissions and Atlassian policies.

Security practices

Server-side validation of JSM project type and permission-aware Jira API requests, input checking, avoidance of external requests, defensive CSV escaping and automated dependency vulnerability checks are implemented in the app implementation.

Privacy or security requests

support@quantmatrixintelligence.com · security@quantmatrixintelligence.com.