TeamGuard for Jira · security
Security information
A concise description of the security boundaries visible in the current TeamGuard Forge build.
Architecture and access
- The app runs on Atlassian Forge and accesses Jira through Atlassian APIs.
- The current manifest requests
read:jira-workandstorage:app; it does not request Jira write scopes. - Jira permissions of the signed-in user remain authoritative. Project access is checked before project data is used.
- The app requires explicit project selection before reading issues.
Data handling
Issue fields used for the current view are not persisted by TeamGuard. Forge KVS holds inactive configuration drafts with a maximum 365-day expiry. The app does not use external remotes or third-party analytics in the inspected manifest. Atlassian platform storage and retention controls apply.
Current product limits
TeamGuard does not write to Jira issues, enable automation rules or send notifications. Draft deletion removes the record from active app storage; Atlassian may retain platform-side recoverable data under its lifecycle policies.
Report a security issue
Email security@quantmatrixintelligence.com with the affected app/version, steps to reproduce and relevant technical details. Do not include credentials, tokens, one-time codes or unnecessary customer data. Reports are reviewed by the publisher; no response-time commitment is published on this page.