OVERALL RATINGS
INSTALLS
2
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 processes but does not store the following types of End-User Data:
Jira issue identifiers, including issue key and issue ID
Jira project identifiers, including project key
Workflow transition data, including transition name, status changes, and timestamp
Atlassian user identifiers, including account ID and optionally display name
Jira issue content selected by administrators in custom webhook templates, such as summary, status, priority, assignee, reporter, and configured field values
Data residency for in-scope End-User Data
No.
App does not support data residency options.
App REST APIs
This app does not provide REST APIs.
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
Not applicable.
Marketplace app does not store End-User Data outside of Atlassian apps and services.
End-User Data accessed in logs
Yes
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
Not applicable, App neither stores End-User data nor supports data residency options.
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@adminshastra.comIntegration permissions with Atlassian apps
Take Jira administration actions (e.g. create projects and custom fields, view workflows, manage issue link types).
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.
View workflows.
Report user accounts that an app is storing personal data for.
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
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
Yes.
Company/Organization is a 'data controller' for the following types of End-User Data:
Marketplace customer and administrator business contact information
Support request content and contact details
Security and privacy correspondence
Customer account, subscription, and licensing relationship metadata
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 user display names
Jira issue and project identifiers
Workflow rule configuration and transition metadata
FlowGuard audit records
Jira issue field values and content processed by configured workflow rules
Administrator-configured webhook metadata and payload content
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
Yes
Anonymization of closed Atlassian account identifiers by replacing stored account IDs with deleted-user.
Data Processing Agreement (DPA) for customers
No
Did you find this information useful?
Atlassian will use this feedback to serve you better.