Security and trust

Designed to minimize access and data exposure.

ReleaseProof uses a read-only Jira permission model, deterministic rules, minimized frontend results, and fail-closed processing.

Security posture

Designed around explicit boundaries.

01

Read-only Jira scope

read:jira-work permits retrieval of required Jira data through Jira user context. Project-configuration changes require server-side project-admin authorization. The app does not request Jira write permissions.

02

App-owned configuration

storage:app stores ReleaseProof project configuration plus non-personal technical schema-version metadata within the Forge app context.

03

No generative AI path

The readiness engine uses code-based deterministic rules. It does not send Jira data to an LLM.

04

Minimized Custom UI result

Full descriptions and acceptance text sources are excluded from the public analysis value.

05

Fail-closed collection

Incomplete pagination, malformed pages, or unsafe issue mappings abort the analysis.

06

Human decision boundary

ReleaseProof presents evidence. It neither changes Jira nor makes the release decision.

Data handling

Only signals required for the workflow.

Jira issue signalsProcessed during analysisDetermine explicit rule outcomes
Project configuration + schema metadataForge app storageKeep project-level scope, supported field choice, and technical schema version
Analysis outputReturned to Custom UIDisplay score, findings, and minimized evidence
Email correspondenceDirect emailRespond to an explicit contact, early-access request or security report

Assurance boundaries

Claims we do not make.

  • No claim of SOC 2, ISO 27001, or other certification
  • No autonomous approval or compliance determination
  • No promise of zero risk or complete defect detection
  • No substitute for customer validation, access governance, or retention policy
A bounded analysis path
  1. Jira scopeRead required issue signals through Forge
  2. Deterministic rulesEvaluate seven explicit conditions
  3. Minimized resultReturn score, findings, and display data
  4. Human gateReview evidence and make the decision

Hosting and processing boundary

The Jira app and public website are separate systems.

The Atlassian-hosted application architecture runs release analysis inside Atlassian Forge. The public ReleaseProof website is hosted separately on a DigitalOcean Droplet in Frankfurt, Germany. Jira release-analysis data is not processed by the marketing website.

External services and subprocessors

The current Jira analysis path declares no external Forge remotes or external product runtime hosts and does not use an external product database, generative AI provider, or marketing-site service. DigitalOcean supplies only the public website's hosting infrastructure. Email correspondence is separate from Jira-product processing and is documented in the privacy notice.

Responsible disclosure

Report a suspected security issue by email using the contact on our security-reporting page. Do not include passwords, API tokens, credentials, production Jira content or unnecessary personal data in the initial message.

Contact security

Need a focused security review?

Email us to request architecture, permission, and data-flow details relevant to your evaluation.