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.
Security and trust
ReleaseProof uses a read-only Jira permission model, deterministic rules, minimized frontend results, and fail-closed processing.
Security posture
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.
storage:app stores ReleaseProof project configuration plus non-personal technical schema-version metadata within the Forge app context.
The readiness engine uses code-based deterministic rules. It does not send Jira data to an LLM.
Full descriptions and acceptance text sources are excluded from the public analysis value.
Incomplete pagination, malformed pages, or unsafe issue mappings abort the analysis.
ReleaseProof presents evidence. It neither changes Jira nor makes the release decision.
Data handling
Assurance boundaries
Hosting and processing boundary
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.
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.
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 securityEmail us to request architecture, permission, and data-flow details relevant to your evaluation.