QuantMatrix Intelligence

TeamGuard for Jira · privacy

TeamGuard for Jira — Privacy Policy

Last updated: 21 October 2026

Publisher: Rafael Barreto Haddad, an individual based in Brazil and using the QuantMatrix Intelligence brand.

Applies to: TeamGuard for Jira, the app's published documentation, and support requests about this app.

1. What the app does

TeamGuard is a Forge app for Jira Cloud that displays explainable project deadline and blocker indicators. A user must select a Jira project before issue data is requested. An authorized Jira administrator can save and restore inactive configuration drafts. The app does not edit Jira issues, activate draft rules or send automatic alerts.

2. Jira information accessed

When a user selects a project, TeamGuard reads the issue key, project key, issue summary, status, due date, labels, priority, and assignee display name and account ID, where present, through Jira APIs. Access is subject to the signed-in user's Jira permissions. Issue summaries may contain personal or confidential information entered by the customer.

The app does not request issue descriptions, comments or attachments. These issue fields are used to render the user's current view and are not intentionally stored in TeamGuard's Forge Key-Value Store. User Atlassian account context is used for authorization but the current production code does not deliberately store author IDs, assignee IDs, email addresses or issue content in its draft records.

3. Inactive draft storage

When an authorized administrator elects to save a configuration draft, TeamGuard stores a generated draft identifier, creation and expiry times, project keys, inactive rule proposals, and sometimes a reference to the prior draft. The administrator can review, restore as a new inactive draft or delete an existing inactive draft, subject to permissions. These drafts do not apply Jira settings or modify issues. The current KVS schema applies a retention limit of 365 days and stops displaying expired drafts. Atlassian's platform recovery or backups may retain deleted/expired information for its own recovery period.

4. Purposes and responsibility

Jira fields are processed to show the selected customer project's delivery signals and to provide the app at the Jira user's request. The customer controls its Jira projects, users, access rules, and the underlying business purposes for those records. For processing Jira customer content, TeamGuard operates in support of the customer's instructions within the published functionality; specific legal controller/processor roles are governed by the relevant law and customer agreement.

The publisher decides how to handle direct support inquiries, security reports and privacy requests and may process names, email addresses and details voluntarily supplied in that correspondence for troubleshooting, abuse prevention, responding to requests and applicable legal obligations. Applicable legal grounds may include performing a customer agreement, legitimate interests in safe operation, and legal obligations, depending on the activity and law. TeamGuard does not use Jira data for advertising, employee performance scoring, sale of personal data or external AI analysis.

5. Service providers and countries

The Jira APIs and the TeamGuard app's compute and Key-Value Store run on Atlassian Forge. Atlassian's published Forge data residency features make customer-directed regional hosting available for Forge KVS, including Australia, Canada, the European Union (Ireland/Germany), Germany, India, Japan, Singapore, South Korea, Switzerland, United Kingdom and the United States. Where a Jira site is not pinned, hosted data may be in Atlassian-selected supported regions. The exact site/data realm is managed through Atlassian's controls, not independently selected by TeamGuard.

This website's publicly available documentation is served using Cloudflare. Cloudflare may process connection metadata such as IP addresses and HTTP requests and may insert its Web Analytics beacon on pages to measure page usage, under its applicable service terms. This public-site telemetry is separate from Jira issue processing; it does not give Cloudflare access to data read inside Jira. The app manifest currently declares no remote backend, external analytics or third-party AI service for Jira issue data. No additional app-level external recipient is configured.

Atlassian data-residency details: https://developer.atlassian.com/platform/forge/data-residency/

6. Retention, deletion and security

Jira issue data remains controlled by the customer's Jira account; TeamGuard does not intentionally make persistent copies. Drafts have a maximum 365-day application retention schedule and may be deleted from active Forge storage sooner by an authorized Jira administrator. Copies inside Atlassian-managed backup or recovery systems follow Atlassian's policies.

Support and privacy correspondence is retained only for as long as reasonably necessary for the request, dispute or applicable legal obligations and can be reviewed for deletion on a verified request. TeamGuard's Jira access uses current-user permissions, and the app requests only Jira read and Forge storage scopes. No security outcome can be guaranteed against all threats.

7. Individual rights and requests

Depending on your location and the applicable law, you may request access, correction, deletion, restriction, objection or other rights concerning your personal data. For source issue data, contact your Jira site administrator or your organization's privacy officer. To request a TeamGuard draft deletion, provide the Jira site and draft ID to your administrator, who can use the app's deletion feature, or contact the publisher.

Contact for support, privacy and security concerns:

The support@quantmatrixintelligence.com and security@quantmatrixintelligence.com forwarding routes are not yet confirmed. Use the direct contact above for privacy requests and security reports until those routes are confirmed.

Do not send passwords, authentication codes, tokens, issue attachments or unnecessary personal data. The publisher may need to verify the requester's authority to disclose or delete customer-related information. Where a customer acts as data controller, requests may need to be handled through that customer.

8. Updates and questions

Material changes to the processing described here will be reflected in an updated policy with a new effective date, and notices will be provided where applicable law requires. To ask about this policy or a data-subject request, use the direct contact above.

This notice describes the TeamGuard production code deployed on 21 October 2026. It is a transparency statement about actual application data practices, not an independent legal certification or an amendment to Atlassian's terms.

Documentation · Support