OVERALL RATINGS
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:
ticket draft text
admin question catalog
The app stores the following types of End-User Data:
Content posted by end-users
Data residency for in-scope End-User Data
Yes.
Marketplace app stores End-User Data exclusively within Atlassian apps and services which support data residency options, as outlined
here.App 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:
Admin question catalogs and site threshold (Forge SQL)
Completa custom field values: description text, coverage, ready (Jira)
Enabled project and request-type configuration (Forge SQL)
Native issue Description copied from Completa (Jira)
List of out-of-scope End-User Data
App stores the following types of out-of-scope end-user data:
Draft description text sent to Jev (jevtypesafe.org) for scoring; processed, not stored by Completa
Forge function logs (draft/ticket id, call count, status, token counts)
Migration of in-scope End-User Data between data residency supported locations
Yes.
Marketplace app stores End-User Data exclusively within Atlassian apps and services which support data residency options, as outlined
here.End-User Data shared with third-party entities
Jev / TypeSafe
Link:
https://jevtypesafe.org
Location:
🇺🇲
United States of America
Purpose:
Score whether the draft answers the admin questions
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
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@branchcreation.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.
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.
Create and edit customer requests, including add comments and attachments, approve, share (add request participants), subscribe, and transition.
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
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:
Admin question catalogs and threshold
Completa field description text, coverage, and ready flag
Enabled project and request-type configuration
Draft description text processed by Jev for scoring
Atlassian account id used for rate limiting (in memory)
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:
Admin question catalogs and threshold
Completa field description text, coverage, and ready flag
Enabled project and request-type configuration
Draft description text processed by Jev for scoring
Atlassian account id used for rate limiting (in memory)
General Data Protection Regulation (GDPR) approved mechanism for transferring European Economic Area (EEA) residents’s End-User Data outside of the EEA
Yes,
Standard Contractual Clauses (SCCs)
Privacy enhancing technologies (PETs) used to protect End-User Data
Yes
Encrypted Forge environment variable for the Jev API key; never sent to the browser
Draft text and Jev error bodies are not written to logs
Jira browse/edit permission check before writing issue Description
Data Processing Agreement (DPA) for customers
No
Did you find this information useful?
Atlassian will use this feedback to serve you better.