Filter & Dashboard Dependency Guard for Jira โ Privacy Policy
Last updated: 24 October 2026
1. Who is responsible
QuantMatrix Intelligence provides Filter & Dashboard Dependency Guard for Jira and is responsible for the processing of data carried out through the app and its support activities as described in this policy. For personal data contained in a customer's Jira environment, the customer determines the purposes of its use and QuantMatrix processes that data to provide the requested app functionality on the customer's behalf. QuantMatrix is responsible for determining the purposes of processing correspondence submitted directly to its support or security contacts. Atlassian operates Jira Cloud and the Forge platform under its own applicable terms and privacy documentation.
Privacy and support contact: support@quantmatrixintelligence.com. Security reports: security@quantmatrixintelligence.com.
2. Data processed by the app
The app performs an on-demand, read-only audit of dashboard and filter dependencies. It accesses Jira through Atlassian Forge using the permissions of the requesting user and the read:jira-work scope. Jira permissions and API availability limit what can be inspected.
The app processes dashboard identifiers and names, gadget identifiers and titles, visible filter identifiers, and accessible gadget property values associated with filters. Jira API responses may include additional metadata, including user-related information returned by Jira. Names, titles or property values may themselves contain personal information entered by customers. The report contains dependency findings, identifiers, warnings, counts and a generation timestamp. The app also checks the license context supplied by Forge to determine whether an active subscription or trial permits a production audit.
The app does not request issue descriptions, comments, attachments or worklogs as part of its audit. It does not modify Jira dashboards, filters or other Jira records.
3. Why data is processed
Data is processed to run the audit requested by a user, identify visible filter references and unresolved or uninspectable dependencies, display the report and its coverage limitations, and enforce subscription or trial access. An unresolved reference does not establish that a filter was deleted: it may be private or inaccessible.
If you contact us separately, we process your contact details and the information you choose to provide to answer the request, investigate a reported problem or security issue, and maintain the correspondence needed to resolve it. Please provide sanitized examples and do not send passwords, API tokens or unnecessary customer data.
4. Third parties and disclosure
Audit processing takes place within Atlassian Jira Cloud and Forge. The app does not configure external remotes or external network destinations for audit data, and does not send that data to QuantMatrix-hosted servers or external analytics services. The app does not sell audit data or use it for advertising.
Atlassian processes data as the provider of Jira and Forge, including platform operational records, under its applicable terms and policies. Correspondence that you send separately to support or security is handled outside the app and may be processed by the email or support service providers used to deliver and manage that correspondence. Access is limited to people and providers who need it for that purpose. Information may also be disclosed where required by applicable law or to respond to a lawful request. These support and legal disclosures are separate from the app's audit data flow.
5. Retention and uninstall behavior
The app does not persist audit results or Jira metadata in an application database or Forge app storage. Data is processed temporarily during a scan, and the result is held in the app page's in-memory state while that page remains open. Reloading or closing the page clears that displayed state; a new scan replaces the previous result. The app maintains no persistent audit history to delete on uninstall.
Uninstalling removes the app's access through that installation. It does not delete or change the customer's underlying Jira dashboards, filters, gadgets or other Jira records. Those records remain subject to the customer's Jira administration and Atlassian's applicable retention rules. Platform logs and operational records are subject to Atlassian's applicable retention and deletion controls; this policy does not promise their immediate deletion on uninstall. The app does not intentionally log audit content or access tokens.
Support and security correspondence is separate from the installation and is not automatically deleted when the app is uninstalled. It is retained only as long as needed to handle the request, maintain necessary resolution records, meet applicable legal obligations or establish, exercise or defend legal claims. You may request deletion using the contact below. Where retention is still necessary, we will explain the applicable reason and any limits on deletion.
6. Your privacy rights and how to exercise them
Depending on applicable law, you may request access to, correction of, deletion of or a copy of your personal data, and request restriction of or object to processing. Where processing relies on consent, you may withdraw it. You may also raise a concern with the competent data protection authority.
Send requests to support@quantmatrixintelligence.com with the subject "Privacy request โ Filter & Dashboard Dependency Guard for Jira". Describe the right you wish to exercise and provide enough information to locate the relevant support correspondence or Jira site. Do not include credentials or unnecessary sensitive information. We may request proportionate information to verify your identity or authority and will respond within the time required by applicable law.
For personal data in your organization's Jira records, contact your Jira administrator or the organization responsible for that site. We will assist or direct requests to the appropriate customer or Atlassian channel where the data is controlled by them. Because the app keeps no persistent audit database, QuantMatrix cannot retrieve a historical audit record from app storage. Customers can stop future app processing by uninstalling the app or managing its access through Jira.
7. Policy changes
We will update this page and its last-updated date when this policy changes. Changes to the app's data access, storage or external data flows will be reflected in this policy and the relevant app disclosures.