/
Data Security and Privacy Policy - Field Radar

Data Security and Privacy Policy - Field Radar

Effective Date: May 5, 2026

Scope and Applicability

This policy applies to the Field Radar app, a Forge-based application available on the Atlassian Marketplace for Jira Cloud. It is intended for administrators, security reviewers, and compliance teams evaluating the app's data handling practices.

Privacy

Field Radar does not collect or process any personal user data. The app only stores configuration metadata necessary for its functionality. No personal information — such as names, emails, or browsing behavior — is collected, tracked, or transmitted.

Data Storage and Location

What data we collect and for what purposes

The app stores the following configuration data exclusively to deliver its core functionality:

  • Project ID → Used to determine in which projects the configuration will be visible.

  • Issue Type ID → Used to determine in which issue types the configuration will be visible.

  • Project Role ID → Used to determine for which users in specific project roles the configuration will be visible.

  • Group ID → Used to determine for which users in specific groups the configuration will be visible.

  • JQL → Used to determine which related issues should be displayed in the configuration.

  • Issue Link Type ID → Used in the linked issues configuration to determine which issues linked with a specific issue link type should be displayed.

  • Field ID → Used to determine which field values of related issues should be displayed in the configuration.

How that data is stored, used, and shared

  • The data is stored via Custom Entity Storage, a storage mechanism provided by the Atlassian Forge platform.

  • We use the stored data only within the Forge platform, i.e., on Atlassian Cloud infrastructure.

  • We do not share or use the stored data outside the Forge app or with any third parties.

Data Residency

Field Radar is built on Atlassian Forge and uses Custom Entity Storage. All data is stored and processed entirely within Atlassian's Cloud infrastructure. No data leaves the Forge environment or is transferred to external servers. For details on Forge data residency, see Atlassian's Forge Data Residency documentation.

Security Measures

  • All data in transit is encrypted via HTTPS/TLS.

  • Data at rest is managed by the Atlassian Forge infrastructure and subject to Atlassian's security controls.

  • The app makes no external network calls and does not transfer data to any outside service.

  • Forge's built-in sandboxing and permission model ensures the app operates within a secure, isolated environment.

Data Retention

  • Configuration data is retained only as long as the app is installed and the configuration is active.

  • No data is retained beyond what is strictly necessary for the app's functionality.

  • Upon uninstallation, see the App Removal section below for retention and recovery details.

Backups

For customer-owned disaster recovery, Atlassian provides a dedicated Atlassian Cloud Backup and Restore add-on for Jira and Confluence, supporting app data within a 30-day retention window. Please consult Atlassian's current documentation to confirm whether Forge app data (including Field Radar data) is included in backup and restore operations at the time of your review.

App Removal

If chosen, the app can be safely removed. Upon uninstallation:

  • All app data will be permanently deleted after 28 days.

  • App data can be recovered if the app is reinstalled within 21 days of uninstallation. To initiate recovery, create a request on Developer and Marketplace Support.

  • Contact us at apps@almbase.com for further instructions.

User and Customer Rights

In accordance with applicable data protection regulations (including GDPR):

  • Customers may request an export or deletion of any data stored by the app.

  • Requests can be submitted by contacting us at apps@almbase.com.

  • We will respond to all data-related requests within 30 days.

Third Parties and Sub-Processors

No third parties or sub-processors are involved in any aspect of the app's data collection, storage, or processing.

Changes to This Policy

We may update this policy from time to time. Changes will be reflected on this page with an updated Effective Date. We encourage customers to review this policy periodically. For material changes, we will make reasonable efforts to notify affected customers via the Atlassian Marketplace listing.

Contact