OVERALL RATINGS
INSTALLS
3
SUPPORT
- Partner Supported
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 app does not process but stores the following types of End-User Data:
Audit and activity log data (per-issue sync history and operational sync metadata)
App Configuration
Data residency for in-scope End-User Data
No.
App does not support data residency options.
App REST APIs
This app provides custom REST APIs for integration with external tools. These APIs are not hosted on the Forge platform.
The Forge webtrigger exposes HTTP endpoints (POST /, /create, /update, /close, /delete, /ping, plus GET/HEAD health checks) for SAP Cloud ALM webhook integration.
List of in-scope End-User Data
No.
App does not support data residency options.
List of out-of-scope End-User Data
No.
App does not support data residency options.
Migration of in-scope End-User Data between data residency supported locations
No.
App does not support data residency options.
End-User Data shared with third-party entities
SAP SE (SAP Cloud ALM)
Link:
https://www.sap.com
Location:
🇩🇪
Germany
🇳🇱
Netherlands
🇨🇭
Switzerland
Purpose:
The app transmit the id of Jira work items to SAP Cloud ALM's Alerts API in order to close alerts that have been created.
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
No
Custom retention period for End-User Data
No
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@crossalm.comIntegration permissions with Atlassian apps
Read Assets objects, their attributes values and details.
View user information in Jira that the user has access to, including usernames, email addresses, and avatars.
Read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs.
Read customer request data, including approvals, attachments, comments, request participants, and status/transitions. Read service desk and request types, including searching for request types and reading request type fields, properties and groups.
Read and write to app storage service
Create and edit issues in Jira, post comments as the user, create worklogs, and delete 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
Response not provided by the partner
Full disk encryption for data stored outside of Atlassian
No
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:
Jira issue identifiers (issue key, issue id, browse URL)
Jira issue content (summary, description, comments, attachments, status, project, issue type), as configured in field mappings
Jira user identifiers (account id; assignee display name returned to SAP on ping)
SAP Cloud ALM alert / event-situation identifiers and payload content (id, subject, body, rating, state, and other mapped fields)
Sync metadata linking SAP entity ids to Jira issues (stored in Forge SQL)
App configuration and credentials entered by admins (profiles, mappings, SAP OAuth, optional webhook Basic Auth)
Operational logs of webhook and API calls (may include issue keys and mapped field values)
Company/Organization is a 'business' under the California Consumer Privacy Act of 2018 (CCPA) with reference to this app
Not applicable.
Company/Organization is not subject to the CCPA.
Company/Organization is a 'service provider' under the California Consumer Privacy Act of 2018 (CCPA) with reference to this app
Not applicable.
Company/Organization is not subject to the CCPA.
General Data Protection Regulation (GDPR) approved mechanism for transferring European Economic Area (EEA) residents’s End-User Data outside of the EEA
No
Privacy enhancing technologies (PETs) used to protect End-User Data
No
Data Processing Agreement (DPA) for customers
No
Did you find this information useful?
Atlassian will use this feedback to serve you better.