This policy describes how Completa Studio for Jira processes data when it is installed on a Jira Cloud site.

Who is responsible

BranchCreation S.L.U. provides the app. Your organization (the Jira site administrator who installs the app) is the customer.

Atlassian hosts the app on the Forge platform (compute and Forge SQL). The app does not send data to BranchCreation servers and does not have a vendor-side database.

This app is not a "Runs on Atlassian" app: while a reporter or agent types a description, Forge sends that draft to Jev (jevtypesafe.org) so Completa can score whether the text answers the questions your administrator configured. See Completa Studio for Jira - Subprocessors for the full disclosure.

What the app accesses

With the site administrator's consent at install time, the app uses these Jira scopes:

• read:jira-work and write:jira-work: read the issue's Description and context, and write the scored text back into Description — after create, on a workflow transition, and while a user is editing an existing issue. A user-triggered read or write first checks, as that signed-in user, that they can browse or edit the issue; automatic paths with no signed-in user (the create trigger, the workflow post-function, the workflow validator) act as the app.
• read:jira-user: identify the signed-in user, for rate limiting and to confirm Jira administration on the admin page.
• manage:jira-configuration: add the Completa field to company-managed create screens when an administrator enables a project.
• read:servicedesk-request and write:servicedesk-request: list JSM request types and place Completa on portal request forms.
• storage:app: small operational marks. Question catalogs and settings live in Forge SQL.

The app does not ask for Atlassian passwords or personal access tokens. Customers never see or configure the Jev API key; BranchCreation sets it as an encrypted Forge variable, one per Forge environment.

Personal data stored on Forge

Per installation, the app may store:

• Question catalogs an administrator wrote, per project, issue type, or JSM request type.
• Which projects Completa is enabled for — individually, or site-wide — and the coverage threshold.
• Completa field values on the Jira issue: the description text, coverage percentage, and whether the draft was ready when last scored. That is Jira data, not a BranchCreation database.

The app does not store Jira passwords. Native Description, once copied, stays in Jira like any other field.

Data that leaves Atlassian (Jev)

To score a draft, the Forge backend sends:

• the text currently being typed or edited
• the questions the administrator configured for that project, issue type, or request type

to https://jevtypesafe.org/api/v1/decide — at most once every 1.2 seconds of typing pause, and never for drafts under 40 characters. Jev returns a score per question. Completa does not send issue keys, comments, attachments, or other Jira fields.

See Completa Studio for Jira - Subprocessors for the full sub-processor disclosure.

How data is used

• Show administrators their question catalog and threshold.
• Score a draft against those questions while it is being written or edited.
• Block create — or a guarded workflow transition — until coverage meets the threshold.
• Copy the scored text into Jira's native Description field.

Data is not sold or used for advertising.

Retention and deletion

• Catalogs, project enablement, and the threshold remain until an administrator changes or deletes them, or the app is uninstalled (Forge then deletes app SQL for that installation).
• Completa field values and native Description remain in Jira until the customer deletes the issue.
• Uninstalling the app does not delete Jira issues.

Contact support@branchcreation.com for assistance with a deletion request the admin screens cannot cover.

International transfers

Forge-hosted data follows the customer's Jira / Forge residency. Scoring requests go to Jev and follow Jev's own infrastructure and regions.

Children

The app is for workplace use on Jira. It is not directed at children.

Changes

We may update this policy when the app or the law changes. Material changes will also be reflected on the Marketplace listing.

Contact

BranchCreation S.L.U. https://branchcreation.com Email: support@branchcreation.com