Privacy Policy

Summary

• LimitRadar runs entirely on Atlassian Forge. Its data is stored in Atlassian Forge hosted storage and never leaves Atlassian.
• Radrly receives no customer data, and the app sends no telemetry.
• The customer is the controller; Radrly is the processor; Atlassian is the only sub-processor.

Who we are

LimitRadar is developed and operated by Radrly Sp. z o.o., Poland (registered office: ul. Tarczyńska 68, 05-831 Krakowiany, Poland; KRS 0001215510, NIP 5342706013, REGON 543658680) (“Radrly”, “we”). This policy covers the LimitRadar app. “Customer” means the organisation that installs LimitRadar on its Atlassian Cloud site. “Users” means the people on the Customer's site.

Data we process

LimitRadar stores:

• configuration snapshots and daily usage series per limit and scope
• forecasts, cleanup candidates and their evidence
• plans, approvals, the actions log with before states and undo handles, and pre-execution backups
• alerts, settings and the imported Automation export metadata used by the reference scan
• Atlassian account IDs of field authors (from the audit log), plan authors, executors, approvers, people who acknowledge alerts and report signers

Not stored: Display names and email addresses (resolved when a page is shown), IP addresses, work item content. Field values copied during a merge are written to Jira and not stored by LimitRadar.

We do not use this data for advertising, profiling or sale, and we do not combine it with other data.

Where data is stored

All LimitRadar data is stored in Atlassian Forge hosted storage on Atlassian's infrastructure. It follows the data residency location of the Customer's site. Radrly runs no servers that hold customer data.

No egress, no sub-processors

LimitRadar declares no remote hosts, uses no Forge Remote and no Connect, and calls no external APIs. We do not share data with third parties. Atlassian provides the hosting platform under its own terms and, for GDPR purposes, is a sub-processor. Other than Atlassian, we use no sub-processors.

AI

LimitRadar does not use Forge LLMs. The optional Rovo agent runs in Atlassian Rovo and reads LimitRadar data through Forge actions inside Atlassian.

Writes to Atlassian products

LimitRadar writes to Jira only when an administrator runs a cleanup action or confirms a Rovo action, and when it creates the alert, digest, report or approval work items you configured.

Permissions (scopes)

The scopes LimitRadar requests are listed on the Security page and shown when the app is installed.

Retention and deletion

Snapshots, logs and reports are kept for the default retention period while the app is installed; in the Advanced edition an administrator can configure retention. Undo data is kept for as long as undo is possible.

Personal data reporting: the app reports stored Atlassian account IDs to Atlassian's personal data reporting API. When Atlassian reports an account as closed, LimitRadar removes or pseudonymises that account ID.

After uninstall: the Forge platform deletes the app's data according to Atlassian's policy for Forge hosted storage. Radrly keeps no copy.

Logs

The app writes operational status and error messages, without personal data, to the Forge developer console. Logs stay in Atlassian's environment.

GDPR

Roles. For personal data in LimitRadar, the Customer is the controller and Radrly is a processor acting on the Customer's documented instructions. A Data Processing Agreement is available.

Your rights. If your data is in a Customer's LimitRadar, you have rights of access, rectification, erasure, restriction, portability and objection under the GDPR. Please contact the organisation that runs your site first. We will support the Customer in answering such requests. You can also complain to a supervisory authority (in Poland: the President of the Personal Data Protection Office, UODO).

International transfers

Radrly does not transfer data itself. Data is hosted by Atlassian in the location set by the Customer's data residency choice, and Atlassian's own transfer mechanisms apply.

CCPA

Radrly does not sell personal information.

This website

This site is static. It uses no cookies, no analytics, no trackers and no third-party scripts, fonts or CDNs. Our web server keeps standard access logs (IP address, time, requested page) for security and operations for a short period.

Changes

We will update this page when the app's data handling changes and show the date at the top. For material changes we will notify customers, for example through Atlassian Marketplace.

Contact

Privacy questions and data requests: marcin@radrly.com.