Privacy Policy

Summary

• LeakRadar 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

LeakRadar 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 LeakRadar app. “Customer” means the organisation that installs LeakRadar on its Atlassian Cloud site. “Users” means the people on the Customer's site.

Data we process

LeakRadar stores:

• masked snippets and masked item titles, keyed hashes (HMAC-SHA256 with a per-installation secret) and locations of findings
• AI labels, confidence and short reasons, which never quote the value, and monthly AI usage counters
• statuses, severity overrides, owners, due dates and the decision history, including free-text triage notes that users type, which LeakRadar masks before storing
• suppressions, saved views, in-app notifications, sensitivity labels with undo data for restrictions, auto-remediation policies and their runs, custom detectors, delegated role grants and settings
• erasure records (counts, locations and hashes, no values), reports, report hashes and the audit log of settings changes, scans and exports
• Atlassian account IDs of owners, actors in the decision history and audit log, LeakRadar team members, people with delegated roles, policy approvers and people who request an erasure

Not stored: Raw secret or personal data values, rendered page or work item content, AI prompts and responses, IP addresses, email addresses of users and cached display names. Content, including attachment text, is processed in memory during a scan and discarded.

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 LeakRadar 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

LeakRadar 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

LeakRadar uses Forge LLMs, Atlassian-hosted models available to Forge apps, to triage ambiguous candidates. AI triage is on by default when LeakRadar is installed, and a Jira administrator can switch it off in Settings. Requests contain masked context with the candidate replaced by a shape description. Prompts and responses are not stored.

Writes to Atlassian products

LeakRadar writes to Jira or Confluence only for actions a user confirms (redaction, version purge, attachment actions, restrictions, labels, markers), which run as that user; for auto-remediation policies a Jira administrator approved, which run as that administrator after a 7-day dry run; and for the remediation, alert and evidence work items you configured.

Permissions (scopes)

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

Retention and deletion

Open, confirmed and accepted risk findings are kept while they stay in that state. Resolved and false positive findings are kept for 13 months by default; a Jira administrator can change this period in Settings (90 days to 24 months). The audit log is kept for 13 months and signed report hashes for 7 years, so earlier evidence can still be verified.

Personal data reporting: the app reports stored Atlassian account IDs to Atlassian's personal data reporting API. When Atlassian reports an account as closed, LeakRadar 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 LeakRadar, 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 LeakRadar, 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.