Free app
OVERALL RATINGS
INSTALLS
5
SUPPORT
- Unsupported
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
Not applicable.
Marketplace app stores End-User Data exclusively within Atlassian apps and services, which don't support data residency options yet due to Atlassian’s current roadmap
App REST APIs
This app provides custom REST APIs for integration with external tools. These APIs are not hosted on the Forge platform.
The app exposes three HTTPS endpoints, all implemented as Atlassian Forge web triggers. They run on Forge infrastructure (*.hello.atlassian-dev.net); the vendor operates no server and hosts nothing. 1. Repository webhook receiver. Receives webhook deliveries from the customer's own Forgejo instance: push, branch create/delete, pull request, repository, and Forgejo Actions run events. The app maps them to Jira development information. 2. CI status receiver. Receives deployment, build and feature flag reports posted by a step in the customer's own Forgejo Actions workflow. Forgejo has no equivalent data to read for deployments or feature flags, so they can only be reported by the customer's pipeline. 3. OAuth callback. The redirect target for Forgejo's OAuth 2.0 authorization code flow, used once per connection to obtain an access token. All three are ingestion-only. None returns Atlassian data, end-user data, or app-stored data to the caller; responses are a status code and a short status message. Authentication. Endpoints 1 and 2 require a valid X-Forgejo-Signature header: - HMAC-SHA256 computed over the raw request body using a 256-bit secret generated per installation and stored encrypted. Digests are compared in constant time. - Each URL carries a connection identifier that selects which stored secret to verify against; a request naming no connection, or an unknown one, is rejected before the body is parsed. Verification is mandatory and fails closed, so an unsigned or wrongly signed request is refused with 401. Endpoint 3 is protected by a single-use state value (deleted on read, 10 minute expiry) and PKCE with the S256 method, and trusts nothing else in its own URL. The URLs are unguessable, generated per installation by Forge, and are shown only to Jira administrators on the app's admin page.
List of in-scope End-User Data
Not applicable.
Marketplace app stores End-User Data exclusively within Atlassian apps and services, which don't support data residency options yet due to Atlassian’s current roadmap
List of out-of-scope End-User Data
Not applicable.
Marketplace app stores End-User Data exclusively within Atlassian apps and services, which don't support data residency options yet due to Atlassian’s current roadmap
Migration of in-scope End-User Data between data residency supported locations
Not applicable.
Marketplace app stores End-User Data exclusively within Atlassian apps and services, which don't support data residency options yet due to Atlassian’s current roadmap
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:
security@iamroon.pkIntegration permissions with Atlassian apps
Allows the app to delete development information (commits, branches, pull-requests)
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
Allows the app to write build information
Allows the app to write deployment information
Allows the app to write development information (commits, branches, pull-requests)
Allows the app to write feature-flag information
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
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
No
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
No
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
Not applicable.
Company/Organization is neither a ‘data processor’ under GDPR nor a ‘service provider’ under CCPA.
Did you find this information useful?
Atlassian will use this feedback to serve you better.