OVERALL RATINGS
INSTALLS
35
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 the following types of End-User Data:
Jira issues (id, key, assignee, created, parent, issue type, status, summary, assignee, priority, sprint, story points, epic Link, time original estimate, time estimate, time spent, issue changelog, other issue numerical custom fields)
Jira agile boards (including configuration, quick-filters, board features or sprints)
Jira filters (id, name and JQL)
Jira custom fields, workflow statuses and status categories, issue types, projects (id, name, key), instance info (base url, deployment type, etc)
Jira users (account id, avatar url, display name)
The app stores the following types of End-User Data:
To speed up the performance of gadgets, some data resulting after processing is saved in the database cache and reused the next time the gadget is loaded. This cache mainly consists of numbers (values resulting from processing), but can also contain issue ids, sprint ids, status names, assignee account ids, project keys, etc. The data is stored in an encoded format.
The application stores identifying information about the Jira instance (such as the base URL) necessary to be able to communicate and work with it.
Data residency for in-scope End-User Data
Marketplace app supports data residency and stores End-User Data independently outside of Atlassian apps and services in the following locations:
🇦🇺
Australia
🇮🇳
India
🇺🇲
United States of America
🇮🇪
Ireland
More information on the Marketplace app’s data residency policy can be found in app’s product documentation or please contact the respective Marketplace app partner at
support@stonikbyte.comApp 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:
Location depends on how you configured data residency in the app settings. Data mainly consists of numbers (values resulting from processing), but can also contain issue ids, sprint ids, status names, assignee account ids, project keys, etc.
List of out-of-scope End-User Data
App stores the following types of out-of-scope end-user data:
Jira Cloud instance identification data such as Jira Base URL or installation ID.
Migration of in-scope End-User Data between data residency supported locations
No
End-User Data shared with third-party entities
Amazon Web Services (AWS)
Link:
https://aws.amazon.com
Location:
🇦🇺
Australia
🇮🇳
India
🇮🇪
Ireland
🇺🇲
United States of America
Purpose:
AWS hosts the app servers and infrastructure, including the databases that store the app data: info about Jira instance and cached data resulting from processing (in form of numbers, but can also contain issue ids, sprint ids, status names, assignee account ids, project keys, etc). This is needed for the app functions, to speed up the app performance, and to reduce the load on Jira. Location of the data storage can be configurable via Data Residency settings of the app.
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
Minimum storage period post un-install:
1 day
Maximum storage period post un-install:
90 days
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@stonikbyte.comIntegration permissions with Atlassian apps
Access and interact with your data from outside of Atlassian.
Access and interact with your data as the logged-in user from outside of Atlassian.
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 Assets objects, their attributes values and details.
View and search for epics, and issues related to an epic.
View issue 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.
View JQL.
View projects.
View sprints and sprint related issues and properties.
View workflows.
Read and write to app storage service
More information on the justification of app’s integration permissions are shared by the app’s partner hereCompliance certifications
ISO27K
SOC2
Cyber Security Audit & Pentest
Marketplace Security Bug Bounty Program participant
Yes.
App is a participant in Marketplace Security Bug Bounty Program.
CAIQ Lite
CAIQ Lite Questionnaire has not been submitted
Security policy
Full disk encryption for data stored outside of Atlassian
Yes
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:
Email address and, optionally, full name (if and as provided by data subject) consented by an end user in the context of app improvement process (app feedback, feature requests, bug reports, support requests etc.)
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 issues (ID, key, summary, status, changelog, issue default fields, issue custom fields), Jira users (account ID, avatar URL, display name), Jira configuration (boards, sprints, filters, custom fields, statuses, projects, teams), Jira instance info, Cached metrics (issue IDs, sprint IDs, project keys, numeric values, account IDs)
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. App does not transfer EEA residents' data outside of the EEA.
Privacy enhancing technologies (PETs) used to protect End-User Data
No
Data Processing Agreement (DPA) for customers
Yes,
DPA
Atlassian trust programs
MARKETPLACE BUG BOUNTY PARTICIPATION
This app offers verified security through:
Participation in the Marketplace Bug Bounty program
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.