Skip to:

Marketplace

LimitRadar: Limits & Unused Custom Field Cleanup for Jira

by Radrly
works with Jira Cloud

OVERALL RATINGS

INSTALLS

2

SUPPORT

  • Partner Supported

TRUST SIGNALS

Showing details for Cloud

Privacy and Security details

The Atlassian Marketplace partner is responsible for the accuracy of the information provided below. Details with a verified status are confirmed by Atlassian. For any further queries, contact the partner.

Data storage and management

  • End-User Data processed and/or stored outside of Atlassian apps and services (excluding process/storage of End-User Data in logs)

    The Marketplace app does not process or store End-User Data outside of Atlassian apps and services.

  • Data residency for in-scope End-User Data

    Yes.

     

    Marketplace app stores End-User Data exclusively within Atlassian apps and services which support data residency options, as outlined

    here.
  • App REST APIs

    This app does not provide REST APIs.

Security and compliance

  • Contact for app security issues

    App’s e-mail contact:

    support@radrly.com
  • Integration permissions with Atlassian apps

    • Delete field options.

    • Delete fields.

    • Delete issue type schemes.


    More information on the justification of app’s integration permissions are shared by the app’s partner here
  • Compliance certifications

    None.

Privacy

  • Privacy policy

    Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

    Partner privacy policy
  • Company/Organization is a 'data controller' under the General Data Protection Regulation (GDPR) with reference to this app

    No

  • Company/Organization is a 'data processor' under the General Data Protection Regulation (GDPR) with reference to this app

    Yes.

    Company/Organization is a 'data processor' for the following types of End-User Data:

    • Atlassian account ids and Jira configuration metadata. Atlassian account IDs only. LimitRadar does not store display names, email addresses, avatars or IP addresses. Names are resolved from Jira when a screen is rendered. Account IDs are stored for field authors (from the audit log), plan authors, action executors, approval requesters and approvers, people who acknowledge alerts, report signers, the person who imports an Automation export, inactive role actors and suspended grant holders that a cleanup plan can target, accounts seen while scanning role actors (until the next snapshot replaces them), and a user grant holder kept in an action snapshot so undo can restore the grant. The Rovo MCP tools return no account ids, names or email addresses. Each call runs as the signed-in user; LimitRadar logs only the action key, the row count, the duration and, when needed, the licence source, never account or site ids.

Atlassian trust programs
RUNS ON ATLASSIAN

This app runs on Atlassian infrastructure to meet enterprise needs.

Hosted on Atlassian

Data stored within Atlassian

Data residency compliant

More details
How do these programs address app trust?

Marketplace programs help Marketplace partners achieve the highest consistent standards for application security and privacy.

About trust programs
Did you find this information useful?

Atlassian will use this feedback to serve you better.

Learn and explore

  • What’s Marketplace
  • App installation
  • About Atlassian
  • Atlassian resources
  • Search and ranking
  • Atlassian events
  • Atlassian foundation

Follow