Blocker Radar for Jira

Data Processing Agreement

Data processing terms for customers using Blocker Radar for Jira.

Last updated: October 2026

This Data Processing Agreement ("DPA") forms part of the agreement between the customer ("Customer") and Guardian Apps concerning the use of Blocker Radar for Jira ("Blocker Radar", "the App").

This DPA applies where Guardian Apps processes personal data on behalf of the Customer in connection with the App.

1. Roles of the parties

For personal data processed through Blocker Radar on behalf of the Customer, the Customer acts as the data controller and Guardian Apps acts as the data processor, to the extent those terms apply under applicable data protection law.

The Customer determines the purposes for which Jira is used and is responsible for the Jira data made available to the App.

2. Processing activities

Blocker Radar processes Jira information required to identify and display active blocking relationships.

The processing may include:

  • retrieving Jira issues and issue-link relationships
  • evaluating issue status and priority
  • displaying project and issue information
  • displaying an assignee's Atlassian user display name
  • filtering and ordering active blocker relationships

3. Categories of personal data

The current version of Blocker Radar may process the following personal data where it is present in Jira:

  • Atlassian user display name associated with an issue assignee

Blocker Radar is not designed to retrieve or persist user passwords, Atlassian Personal Access Tokens, authentication credentials or customer payment information.

4. Categories of data subjects

Data subjects may include Atlassian users whose display names appear as assignees on Jira issues processed by Blocker Radar.

5. Purpose and duration of processing

Personal data is processed only as necessary to provide the Blocker Radar functionality requested by the Customer.

The current version of Blocker Radar retrieves Jira information when the App is used and does not maintain its own persistent external database of Jira issues, blocker relationships or Atlassian user profiles.

Processing continues for the duration of the Customer's use of the App.

6. Customer instructions

Guardian Apps will process personal data only as necessary to provide Blocker Radar and in accordance with the Customer's documented instructions, including the Customer's use and configuration of Jira and the App, unless otherwise required by applicable law.

7. Confidentiality

Guardian Apps will take reasonable measures to ensure that persons authorized to process personal data are subject to appropriate confidentiality obligations.

8. Security

Blocker Radar is built on Atlassian Forge and uses Atlassian-hosted infrastructure for its core functionality.

Guardian Apps implements reasonable technical and organizational measures appropriate to the nature of the App and the data processed.

Further information is available in the Blocker Radar Security Policy.

9. Subprocessors

Blocker Radar relies on Atlassian services, including Atlassian Jira Cloud and Atlassian Forge, to provide its functionality.

The current version of the App does not use an external application server, external database, third-party advertising service or external analytics provider for processing Jira End-User Data as part of its core functionality.

10. International data transfers

Blocker Radar does not independently transfer Jira End-User Data to external infrastructure operated by Guardian Apps.

Processing performed by Atlassian services remains subject to the applicable Atlassian terms, privacy commitments and infrastructure arrangements.

11. Assistance to the Customer

Taking into account the nature of the processing, Guardian Apps will provide reasonable assistance to the Customer with requests relating to applicable data protection obligations where the request relates to processing performed by Blocker Radar.

12. Security incidents

Guardian Apps will take reasonable steps to investigate confirmed security incidents affecting personal data processed by Blocker Radar and will notify affected Customers where required by applicable law.

Security concerns can be reported to security@guardianapps.ch .

13. Return and deletion of data

The current version of Blocker Radar does not maintain a separate persistent Guardian Apps database containing Jira issues, blocker relationships or Atlassian user profiles.

Upon termination or uninstall of the App, Guardian Apps does not retain such data in a separate external customer database.

14. Information and audits

Guardian Apps will make available reasonable information necessary to demonstrate compliance with this DPA, taking into account the nature and scale of the App and the security and confidentiality obligations applicable to Guardian Apps and Atlassian-hosted infrastructure.

15. Customer responsibilities

The Customer is responsible for ensuring that:

  • its use of Jira and Blocker Radar complies with applicable law
  • it has a lawful basis for personal data processed through Jira
  • Jira permissions are configured appropriately
  • only authorized users have access to relevant Jira information

16. Relationship to other terms

This DPA supplements the Blocker Radar Terms of Service.

If there is a conflict between this DPA and the Terms of Service regarding the processing of personal data, this DPA will control to the extent of that conflict.

17. Changes

Guardian Apps may update this DPA to reflect changes in the App, applicable law or data processing practices. The current version will remain available at this URL.

18. Contact

Questions about this DPA can be submitted through the Blocker Radar Support page.