Blocker Triage for Jira privacy notice

Effective date: 24 October 2026

This notice explains how Blocker Triage for Jira handles information. Blocker Triage is provided by Hendrik Bonthuys trading as Kitawolf Studios, a sole trader based in Scotland ("Kitawolf Studios", "we", "us").

Information the app processes

When you open or refresh Blocker Triage, the app reads the current Jira project context, available issue-link types and the visible issue details required to calculate the requested queue. These can include issue identifiers and summaries, work types, statuses and status categories, assignee display names and account identifiers, priority labels and identifiers, creation/update timestamps, and issue-link identifiers and directions. The app also uses the Forge environment and active-license state to determine whether this view may load.

The app uses this information to display visible one-hop blocker relationships and their ownership, priority, status and issue ages. It does not determine when an issue link was created or how long work has been blocked. Scans are bounded and may show only a disclosed subset.

Storage, logging and transfers

Blocker Triage does not operate an external application server or customer database. It does not persist Jira issue content in app-owned storage, send customer data to third-party analytics, use issue data for advertising, or process issue data with AI/ML services. The manifest declares no external data-egress domains.

Current queue and linked-detail results are held in memory, with an absolute 15-minute validity limit from the start of a scan. Filters and relationship changes do not extend that limit. The app clears expired queue state and cached linked details when its timer executes; it also refuses expired results on resumed renders, user actions and request completion. A new scan is required rather than automatically refreshing in the background. A browser or device can suspend JavaScript and retain its memory until execution resumes, so this is not a guarantee of physical erasure during suspension. The app code does not intentionally write issue content, credentials or access tokens to application logs. Jira and Forge may process platform/operational information under Atlassian's agreements and privacy documentation.

Permissions and access

The app requests read:jira-work. Requests run as the signed-in user. Jira browse permissions and issue security determine the project issues and linked details returned; missing linked details are omitted rather than exposed from an embedded reference. The app grants no additional Jira permission and does not edit Jira data.

Retention and deletion

The app stores no app-owned Jira dataset to retain or delete when it is uninstalled. Jira-hosted data remains governed by the customer's Atlassian agreement, source content and settings. Closing/reloading the page clears the app's in-memory view; this is not a deletion of the customer's Jira records.

Support correspondence

If you contact support, we process your contact details and the information you choose to send to answer and investigate your request. Do not send passwords, API tokens, session cookies, identity documents or unnecessary confidential Jira content.

Support records are kept while a request is open, and afterwards only as needed to investigate recurring issues, record support commitments, handle complaints/security incidents, establish or defend legal claims or meet legal obligations. Closed correspondence is reviewed against those purposes and deleted when no longer needed.

Roles and purposes

Your organisation determines why its Jira work-item data is collected and used. Blocker Triage processes data made available through your request to provide the queue and does not create a separate customer database. Your organisation's privacy information explains its lawful basis for Jira data.

Hendrik Bonthuys trading as Kitawolf Studios is the controller for personal information supplied directly in support correspondence. The reasons for using it are our legitimate interests in answering enquiries, providing/securing the app and resolving problems; contractual necessity where you personally are a party to the contract; and legal obligations where information must be retained or disclosed by law.

You choose what to send to support. We may be unable to investigate without necessary information. Support correspondence is not used for unsolicited marketing, sale of personal information or automated decisions with legal or similarly significant effects.

Support provider and international processing

Our support mailbox uses Namecheap Private Email. Support messages and attachments are processed by that service separately from the Jira app. Namecheap identifies US hosting for Private Email and publishes a Data Processing Addendum. Support correspondence may therefore be processed outside the UK or EEA. Please avoid sending credentials, identity documents or unnecessary confidential Jira content. The app's lack of external egress does not mean separately sent support email stays within Atlassian, the UK or the EEA.

Information may also be disclosed where necessary for professional advice, legal claims, lawful public-authority requests or security-incident investigation with Atlassian, limited to the relevant purpose.

Your choices and rights

Your Jira administrator controls installation and Jira access. Direct Jira-hosted data requests to your organisation's administrator. For information supplied directly to Kitawolf Studios through support, contact us below. Depending on the circumstances and applicable law, rights may include access, correction, deletion, restriction, portability and objection to processing based on legitimate interests. Where processing relies on consent, withdrawal does not affect earlier lawful processing. Applicable conditions/exemptions may apply.

You may complain to the Information Commissioner's Office or another competent authority. We welcome an opportunity to address concerns first.

Changes and contact

We may revise this notice when the app, law or Marketplace requirements change. The public page will show its effective date and any additional notice required.

Email: support@kitawolfstudios.com

Provider and notices address:

Hendrik Bonthuys trading as Kitawolf Studios
75 Fairfield Road
Inverness, Highlands IV3 5LJ
United Kingdom