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:
Atlassian account IDs
Alert acknowledgement notes (free text entered by users)
Jira audit log change values (may include user and group names)
Saved timeline views: the owner's Atlassian account ID (owner_account_id), plus the view name and filters (free text the owner typed). Visible only to the owner. Kept until the owner deletes the view. Included in the daily personal data report. Pseudonymised when an account is closed.
New in 2.0.0: account IDs (or group ids) of work item security level members and of notification-scheme recipients are stored and included in the daily personal data report. Security level members keep only holder type and the reference, never a profile or e-mail. A fixed e-mail address notification recipient keeps its type only, never the address. Request type, queue and service project definitions hold no customer or account data; a queue JQL is stored as written. Audit remoteAddress is still dropped. No display names are cached.
For a closed account, ConfigRadar replaces that account ID with a one-way hash (pseudonymisation) in its change history, alerts, watchlist rules, baselines and saved timeline views. Account IDs inside stored space role, group, work item security level and notification scheme snapshots, in Jira audit change values and in alert acknowledgement notes are not rewritten; they are deleted by retention (90 days in Standard, 30 to 1,095 days in Advanced), except the current version of an object and versions pinned to a baseline, which are kept until the object changes or the baseline is deleted.
Retention: Standard 90 days; Advanced configurable 30-1095 days; saved timeline views stay until their owner deletes them; after uninstall Forge keeps the data for a period (a reinstall within 21 days can be relinked), then Atlassian deletes it.
List of out-of-scope End-User Data
App stores the following types of out-of-scope end-user data:
None. All in-scope End-User Data is stored in Forge hosted storage (Forge SQL and Forge KVS), which follows the customer's Atlassian data residency.
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
No
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
View application roles.
View audit logs.
View system and custom avatars.
Read custom field contextual configurations.
View field configuration schemes.
Read field configurations.
View fields.
View user groups.
View instance configurations.
View issue details.
View issue meta.
View issue security levels.
View issue security schemes.
Read issue type hierarchies.
View issue type screen schemes.
View issue types.
View issue changelogs.
View issue time trackings.
View issue votes.
View issues.
View notification schemes.
View permission schemes.
View permissions.
View priorities.
View project categories.
View project roles.
View project versions.
View project components.
View project properties.
View projects.
View queues.
Search and view request types.
View resolutions.
View screen schemes.
View screen tabs.
View screens.
View screenable fields.
Search and view service desks.
View statuses.
View users.
View workflow schemes.
View workflows.
Report user accounts that an app is storing personal data for.
Create and update issue attachments.
Create and update issue comment properties.
Create and update issue comments.
Create and update issues.
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
Alert acknowledgement notes (free text entered by users)
Jira audit log change values (may include user and group names)
Saved timeline views: the owner's Atlassian account ID (owner_account_id), plus the view name and filters (free text the owner typed). Visible only to the owner. Kept until the owner deletes the view. Included in the daily personal data report. Pseudonymised when an account is closed.
New in 2.0.0: account IDs (or group ids) of work item security level members and of notification-scheme recipients are stored and included in the daily personal data report. Security level members keep only holder type and the reference, never a profile or e-mail. A fixed e-mail address notification recipient keeps its type only, never the address. Request type, queue and service project definitions hold no customer or account data; a queue JQL is stored as written. Audit remoteAddress is still dropped. No display names are cached.
For a closed account, ConfigRadar replaces that account ID with a one-way hash (pseudonymisation) in its change history, alerts, watchlist rules, baselines and saved timeline views. Account IDs inside stored space role, group, work item security level and notification scheme snapshots, in Jira audit change values and in alert acknowledgement notes are not rewritten; they are deleted by retention (90 days in Standard, 30 to 1,095 days in Advanced), except the current version of an object and versions pinned to a baseline, which are kept until the object changes or the baseline is deleted.
Retention: Standard 90 days; Advanced configurable 30-1095 days; saved timeline views stay until their owner deletes them; after uninstall Forge keeps the data for a period (a reinstall within 21 days can be relinked), then Atlassian deletes it.
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
Alert acknowledgement notes (free text entered by users)
Jira audit log change values (may include user and group names)
Saved timeline views: the owner's Atlassian account ID (owner_account_id), plus the view name and filters (free text the owner typed). Visible only to the owner. Kept until the owner deletes the view. Included in the daily personal data report. Pseudonymised when an account is closed.
New in 2.0.0: account IDs (or group ids) of work item security level members and of notification-scheme recipients are stored and included in the daily personal data report. Security level members keep only holder type and the reference, never a profile or e-mail. A fixed e-mail address notification recipient keeps its type only, never the address. Request type, queue and service project definitions hold no customer or account data; a queue JQL is stored as written. Audit remoteAddress is still dropped. No display names are cached.
For a closed account, ConfigRadar replaces that account ID with a one-way hash (pseudonymisation) in its change history, alerts, watchlist rules, baselines and saved timeline views. Account IDs inside stored space role, group, work item security level and notification scheme snapshots, in Jira audit change values and in alert acknowledgement notes are not rewritten; they are deleted by retention (90 days in Standard, 30 to 1,095 days in Advanced), except the current version of an object and versions pinned to a baseline, which are kept until the object changes or the baseline is deleted.
Retention: Standard 90 days; Advanced configurable 30-1095 days; saved timeline views stay until their owner deletes them; after uninstall Forge keeps the data for a period (a reinstall within 21 days can be relinked), then Atlassian deletes it.
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.