Support
Questions, problems or feedback about LeakRadar? We are here to help.
Last updated: 2026-10-19 · Version 1.0
Contact
Support hours
Monday to Friday, 09:00 to 17:00 CET/CEST (Central European Time).
Messages sent outside these hours are answered on the next business day.
Response target
We aim to send a first response within 1 business day. How fast a problem is resolved depends on what we need from you and on how complex it is.
Self-help
How to report a bug
- Check the docs, the FAQ and Troubleshooting. Many questions (scan scope, coverage, detectors, AI triage, masking, triage, redaction, version purge, policies, DSAR, reports and the Rovo agent) are answered there.
- Reproduce it and note the exact steps.
- Email marcin@radrly.com with the details below and a short subject, for example
[LeakRadar] short description. - We will confirm receipt, ask follow-up questions if needed, and keep you updated until it is resolved.
Security vulnerability? Please do not report it through the regular support channel. Follow Reporting a vulnerability.
What information to include
- Your site URL (for example
yourcompany.atlassian.net). - LeakRadar version and edition. Both are shown on the Manage apps page of your administration.
- The finding ID (never the value itself) and the product, space and item involved.
- The scan status and engine version shown on the Scans screen.
- What you did, step by step, what you expected and what happened.
- Screenshots or a short screen recording, including any error message and the time it occurred (with time zone).
- Browser and operating system, and whether you use the light or dark theme.
Please do not send passwords, API tokens or personal data that is not needed to reproduce the problem. Blur names in screenshots where you can. We will never ask for your Atlassian password.
Other resources
- Security, Privacy, Terms (EULA) and DPA
- Other Radrly apps for Jira: MarginRadar, AccessRadar, ConfigRadar, LimitRadar, CapRadar, LeakRadar