Privacy Policy
This policy explains what data the ConfigRadar app for Jira Cloud processes, where it lives, why, and what you can do about it.
Last updated: 2026-10-10 · Version 1.1
Summary
- ConfigRadar is a Forge app that Runs on Atlassian. All app data is stored in Atlassian's Forge hosted storage (Forge SQL and Key-Value Store), and it follows your Jira site's data residency.
- ConfigRadar makes no calls to servers outside Atlassian, and Radrly receives none of your Jira data.
- Atlassian is the only sub-processor (hosting). No external AI or LLM service is used.
- The app never changes your Jira configuration. Its only write to Jira is creating alert issues in a project an admin chooses, in the Advanced edition.
- Audit entries are stored without IP addresses. Display names are not stored.
- Radrly acts as a data processor for the personal data in the app, and your organisation is the controller.
Who we are
ConfigRadar is developed and operated by Radrly Sp. z o.o., a company established in Poland (“Radrly”, “we”). Registered office: ul. Tarczyńska 68, 05-831 Krakowiany, Poland. KRS 0001215510, NIP 5342706013, REGON 543658680.
This policy covers the ConfigRadar app. “Customer” means the organisation that installs ConfigRadar on its Jira Cloud site. “Users” means the people in the Customer's Jira site.
Data we process
ConfigRadar processes only the data needed to record configuration changes, show diffs, raise alerts and produce exports.
| Data | Examples | Purpose |
|---|---|---|
| Atlassian account IDs | IDs of the people who made configuration changes, acknowledged alerts or created baselines | Show who changed what |
| Audit log entries | Time, category, object, summary and changed values of Jira audit records. IP addresses are discarded. User-management records are skipped. | Change history and timeline |
| Configuration snapshots | Content of workflows, workflow schemes, custom fields and contexts, screens, permission schemes and project settings | Before/after diffs, baseline and drift |
| Alerts and watchlist | Watched objects, alert records, keys of alert issues created in Jira (Advanced) | Notify admins about changes |
| App settings | Retention period, alert project and issue type, digest schedule, enabled object types | Configure the app |
| Export artefacts | CSV content, and PDF compliance evidence in Advanced, generated for download | Audits and change reviews |
Display names are not stored; they are looked up from Jira when a page is shown or an export is generated. Email addresses and IP addresses are not stored. The app does not store issue content, comments or attachments.
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 ConfigRadar data is stored in Atlassian Forge hosted storage: Forge SQL and the Forge Key-Value Store, on Atlassian's infrastructure. ConfigRadar stores no End-User Data outside Atlassian products and services, and does not process it outside Atlassian or the user's browser.
Data residency. Forge SQL and Key-Value Store support data residency. The app's data is kept in the location chosen for your Jira site and moves with it if you migrate between residency locations. Radrly does not run any servers that hold your data.
No egress, no sub-processors
ConfigRadar declares no remote hosts, uses no Forge Remote and no Connect, and does not call external APIs. It exposes no public REST API of its own.
We do not share End-User Data with third parties. Atlassian provides the hosting platform (Forge and Jira) under its own terms and, for GDPR purposes, is a sub-processor. Other than Atlassian, we use no sub-processors.
AI
ConfigRadar does not call any external AI or LLM service. Diffs, drift and alerts are deterministic calculations inside Forge. The Advanced edition (coming soon) will include a Rovo agent: Rovo is Atlassian's own AI, and the agent will run inside Atlassian under Atlassian's terms and answer from ConfigRadar data on your site. ConfigRadar sends no data outside Atlassian for it.
Permissions (scopes)
Jira asks you to approve the following scopes when the app is installed. The list matches the app manifest as of 10 October 2026. No manage:* or admin write scopes are requested, so the app cannot change your configuration.
| Scopes | Why ConfigRadar needs them |
|---|---|
read:audit-log:jira | Read the Jira audit log (30-day backfill, then hourly). |
read:workflow:jira, read:workflow-scheme:jira, read:field:jira, read:field-configuration:jira, read:custom-field-contextual-configuration:jira, read:screen:jira, read:screen-tab:jira, read:screenable-field:jira, read:screen-scheme:jira, read:issue-type-screen-scheme:jira, read:permission-scheme:jira, read:permission:jira, read:project-role:jira, read:project:jira, read:project.property:jira, read:project-category:jira, read:project-version:jira, read:project.component:jira, read:issue-type:jira, read:issue-type-hierarchy:jira, read:instance-configuration:jira, read:issue.time-tracking:jira, read:issue-meta:jira | Take daily snapshots and compute diffs. |
read:user:jira, read:group:jira, read:avatar:jira, read:application-role:jira | Show names of change authors and of groups referenced by configuration, without storing them. |
write:issue:jira, write:comment:jira, write:comment.property:jira, write:attachment:jira, read:issue:jira | Advanced only: create alert issues in the project an admin chooses. Granted at install in both editions (Forge scopes cannot differ by edition) but used only by Advanced, and only to create issues. |
report:personal-data | Report stored Atlassian account IDs to Atlassian's personal data reporting API daily and anonymise them when Atlassian reports an account closed. |
See Security for more detail.
Retention and deletion
- While installed: change history and snapshots are kept for 90 days in Standard and for the period an admin sets in Settings, up to 3 years, in Advanced. A daily job deletes older records, except current versions and versions used by a baseline.
- After uninstall: the Forge platform soft-deletes the app's data and destroys it at the end of the retention period described in Atlassian's SOC 2 report. A reinstall within 21 days can be relinked to the old data. This period is set by Atlassian. Radrly itself keeps no copy.
- Personal data reporting: once a day the app reports stored Atlassian account IDs to Atlassian's personal data reporting API. If Atlassian reports an account as closed, ConfigRadar replaces that account ID with an irreversible pseudonym in all its records.
Logs
The app writes operational status and error messages to the Forge developer console. Logs stay in Atlassian's environment and are not sent to Radrly.
GDPR
Roles. For the personal data in ConfigRadar (account IDs of change authors and of admins who use the app, and personal data that may appear in audit records), the Customer is the controller and Radrly is a processor acting on the Customer's documented instructions. A Data Processing Agreement is available.
Legal basis. The Customer decides the legal basis for recording changes made by its administrators (for example legitimate interests in change control and security). Radrly does not decide the purposes of the processing.
Your rights. If you are a person whose data is in a Customer's ConfigRadar, you have rights of access, rectification, erasure, restriction, portability and objection under the GDPR. Please contact the organisation that runs your Jira site first. We will support the Customer in answering such requests. You also have the right to complain to a supervisory authority (in Poland: the President of the Personal Data Protection Office, UODO).
Security. See Security.
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. Radrly is an EU company; any California consumer personal information processed through the app is handled only within Atlassian's platform under Atlassian's terms.
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. The logs are rotated daily and kept for 14 days.
Changes
We will update this page when the app's data handling changes and show the date of the latest update at the top. For material changes we will notify customers, for example through Atlassian Marketplace.
Contact
Privacy questions and data requests: marcin@radrly.com. Security contact: marcin@radrly.com. We have not appointed a Data Protection Officer; privacy questions go to the contact above.