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 processes and stores the following types of End-User Data:
Issue titles, open/closed status, labels and optional plain-text descriptions. Optional explicit assignee mappings process Jira account IDs and GitHub logins. If enabled, new comments after linking include text and author display names. Applies to manually linked pairs and issues matching an administrator's automatic-creation rule. Restricted/internal Jira comments and pull-request comments are excluded. No attachments, worklogs or arbitrary custom fields are copied.
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.
A public Forge POST web trigger receives GitHub issues and issue_comment events. It requires a project-scoped enabled connection and verifies HMAC-SHA256 before parsing, filters supported issue events, deduplicates delivery IDs and queues work. It returns no End-User Data. Project-admin-only Forge resolvers provide connection diagnostics and webhook repair; repair reuses the saved signing secret when available and preserves mappings, pairs and the auto-create boundary.
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
GitHub
Link:
https://github.com
Location:
🇺🇲
United States of America
Purpose:
Customer-selected integration destination for reading and writing explicitly linked issue fields and managing the repository webhook.
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:
0 days
Maximum storage period post un-install:
28 days
Custom retention period for End-User Data
No
Supports customer-managed egress
Yes.
The app lets customers set and manage egress to additional locations after installation.
Security and compliance
Contact for app security issues
App’s e-mail contact:
support@keelcroft.comIntegration permissions with Atlassian apps
Read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs.
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
Yes
App accesses Atlassian Personal Access Tokens (PATs), user account passwords, or another type of shared secret
Yes
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:
Issue titles, open/closed status, labels and optional plain-text descriptions. Optional explicit assignee mappings process Jira account IDs and GitHub logins. If enabled, new comments after linking include text and author display names. Applies to manually linked pairs and issues matching an administrator's automatic-creation rule. Restricted/internal Jira comments and pull-request comments are excluded. No attachments, worklogs or arbitrary custom fields are copied.
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:
Issue titles, open/closed status, labels and optional plain-text descriptions. Optional explicit assignee mappings process Jira account IDs and GitHub logins. If enabled, new comments after linking include text and author display names. Applies to manually linked pairs and issues matching an administrator's automatic-creation rule. Restricted/internal Jira comments and pull-request comments are excluded. No attachments, worklogs or arbitrary custom fields are copied.
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
SHA-256 content digests are stored instead of raw issue field values in link records; event journal entries exclude issue content.
Data Processing Agreement (DPA) for customers
No
Did you find this information useful?
Atlassian will use this feedback to serve you better.