π‘οΈ Security Policy β Issue Delivery Report
Built with security-first principles β powered by Atlassian Forge.
π§± Forge Sandbox Architecture
Issue Delivery Report is built entirely on Atlassian Forge, which guarantees:
π Code isolation per app and per site
π Data residency within Atlassianβs secure cloud infrastructure
π§Ύ Strict API scope enforcement declared via the Forge manifest
π« No external servers, databases, or custom backends
All logic runs inside Atlassianβs serverless runtime. We never host or execute code outside of the Forge environment.
π Permission Scopes
We only request minimal scopes required for functionality β nothing more.
π Scope | Why Itβs Needed |
|---|---|
| To load issue metadata and full status history |
| To display |
| (optional) Reserved for future internal settings |
π No write:jira-work or issue mutation occurs in this app β we never modify issues or fields.
ποΈ Data Residency
All runtime operations and temporary data handling occur inside Atlassianβs platform.
No part of the app transmits or stores data outside Jira
No external analytics, telemetry, or storage are involved
Exports (CSV, JSON, MD, TXT) are generated in the userβs browser, not sent anywhere.
π No Secrets Stored
Issue Delivery Report does not use:
β Environment variables
β Secret tokens
β User credentials
β External endpoints
All logic is performed in a secure session scoped to the current issue.
π₯ User Data Access
We only access:
displayNameof the user who changed issue statuses (for audit clarity)
We do not access:
Email addresses
Full user profiles
Jira internal account IDs
π§ͺ Secure Development Process
We follow strict practices during development:
β Mandatory code reviews for all changes
β Scope-based testing in sandbox environments
β Static analysis using ESLint + Forge validators
β Manual verification via
forge tunnelbefore deployment
β Atlassian-Backed Security
As a Forge app, Issue Delivery Report inherits Atlassianβs platform-level protections:
β SSO authentication with your Jira Cloud instance
β OAuth2-secured API calls via
requestJira()β Per-tenant data isolation
β Enforced runtime boundaries
β Aligned with ISO/IEC 27001, SOC 2, GDPR, and CCPA
π§© Questions about security or compliance?
Reach out to: support@typeswitch.net β weβre happy to provide clarification or assist with vendor risk assessments.