OVERALL RATINGS
INSTALLS
2
SUPPORT
- Partner Supported
TRUST SIGNALS
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.
List of in-scope End-User Data
App stores the following types of in-scope end-user data:
All End-User Data LimitRadar stores: Jira configuration snapshots, usage series, forecasts, cleanup candidates, plans, backups, approvals, the action log, settings and Atlassian account ids, held in Forge SQL and Forge KVS (Forge hosted storage). Work item limits (new SQL table work_item_usage): work item IDs, keys, space IDs and comment, worklog, attachment and link counts for the work items closest to those limits. No work item text, summaries, comments or field values. Each user sees only work items they can browse. These identifiers are not account IDs. Filter cleanup proposals: filter name, favourite count, last use as Jira reports it, and the owner's state as active, inactive or unknown. Never a name or account ID. Retention: Standard 90 days; Advanced configurable 30 to 2555 days (400 by default). Same daily purge as other snapshot data; the newest finished snapshot is kept. LimitRadar can expose 10 read-only tools through Atlassian's Rovo MCP service (Forge rovo:mcp module). The tools run inside the LimitRadar Forge app on Atlassian infrastructure and read only LimitRadar snapshot data already stored in Forge SQL on the customer's site. LimitRadar stores nothing new for these calls and sends no data outside Atlassian. The app has no egress and remains Runs on Atlassian.
List of out-of-scope End-User Data
App stores the following types of out-of-scope end-user data:
None. LimitRadar stores no End-User Data outside Forge hosted storage and has no egress.
Migration of in-scope End-User Data between data residency supported locations
Yes.
Marketplace app stores End-User Data exclusively within Atlassian apps and services which support data residency options, as outlined
here.End-User Data shared with third-party entities
Not applicable.
Marketplace app does not store End-User Data outside of Atlassian apps and services.
End-User Data accessed in logs
No
End-User Data processed and/or stored in logs outside of Atlassian apps and services
No
End-User Data in logs shared with third-party entities
No
End-User Data in logs shared with third party entities integral for app functionality
Response not provided by the partner
End-User Data stored after app is uninstalled
Yes.
Marketplace app stores End-User Data exclusively within Atlassian apps and services which support data residency options, as outlined
here.Custom retention period for End-User Data
Not applicable.
Marketplace app does not store End-User Data outside of Atlassian apps and services.
Supports customer-managed egress
No.
The app only accesses domains declared during installation.
Security and compliance
Contact for app security issues
App’s e-mail contact:
support@radrly.comIntegration permissions with Atlassian apps
Delete field options.
Delete fields.
Delete issue type schemes.
Delete issue type screen schemes.
Delete permission schemes.
Delete permissions.
Delete project roles.
Delete project versions.
Delete project components.
Delete screen schemes.
Delete workflow schemes.
Delete workflows.
View application roles.
View audit logs.
View system and custom avatars.
View the configuration, project features, filters, properties, and quick filters for a board.
View boards, issues on a board, issues from a backlog, reports, and versions.
Read custom field contextual configurations.
View dashboard properties.
View dashboards.
View field configuration schemes.
Read field configurations.
View field default values.
View field options.
View fields.
View filters.
View user groups.
View issue details.
View issue meta.
View issue security levels.
View issue security schemes.
Read issue type hierarchies.
View issue type schemes.
View issue type screen schemes.
View issue types.
View issues.
View JQL.
View labels.
View permission schemes.
View permissions.
View priority schemes, which are used to configure a space's default and available Work Item priorities.
View project categories.
View project roles.
View project versions.
View project components.
View project properties.
View projects.
View screen schemes.
View screen tabs.
View screens.
View screenable fields.
View statuses.
View users.
View workflow schemes.
View workflows.
Report user accounts that an app is storing personal data for.
Read and write to app storage service
Create and update field configuration schemes.
Save field configurations.
Create and update field options.
Create and update fields.
Create and update issue type schemes.
Create and update issue type screen schemes.
Create and update issues.
Create and update permission schemes.
Create and update permissions.
Create and update priority schemes, which are used to configure a space's default and available Work Item priorities.
Create and update project roles.
Create and update project versions.
Create and update project components.
Create and update projects.
Create and update screen schemes.
Create and update workflow schemes.
Create and update workflows.
More information on the justification of app’s integration permissions are shared by the app’s partner hereCompliance certifications
None.
Marketplace Security Bug Bounty Program participant
No
CAIQ Lite
CAIQ Lite Questionnaire has not been submitted
Security policy
Full disk encryption for data stored outside of Atlassian
Not applicable.
Marketplace app does not store End-User Data outside of Atlassian apps and services.
App accesses Atlassian Personal Access Tokens (PATs), user account passwords, or another type of shared secret
No
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 policyCompany/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.
Company/Organization is a 'business' under the California Consumer Privacy Act of 2018 (CCPA) with reference to this app
No
Company/Organization is a 'service provider' under the California Consumer Privacy Act of 2018 (CCPA) with reference to this app
Yes.
Company/Organization is a 'service provider' 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.
General Data Protection Regulation (GDPR) approved mechanism for transferring European Economic Area (EEA) residents’s End-User Data outside of the EEA
Not applicable.
Marketplace app does not process or store End-User Data outside of Atlassian apps and services.
Privacy enhancing technologies (PETs) used to protect End-User Data
Not applicable.
Marketplace app does not process or store End-User Data outside of Atlassian apps and services.
Data Processing Agreement (DPA) for customers
Yes,
DPA
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
How do these programs address app trust?
Marketplace programs help Marketplace partners achieve the highest consistent standards for application security and privacy.
About trust programsDid you find this information useful?
Atlassian will use this feedback to serve you better.