Security and support

Jira source reads use the requesting user on fixed documented routes. Project administrators alone change configuration. Saved queries, comparison, history and CSV require fresh source authorization. The backend uses trusted Forge identity/environment/license context; production requires an active entitlement. The browser cannot supply another actor or tenant.

Strict input bounds, immutable revision conflicts, duplicate-page checks, complete-search checks, source rechecks, query validation and time/request budgets prevent partial evidence from becoming a successful conclusion. On-screen evidence expires after one minute. These controls do not establish transactional consistency or independent security certification.

Permissions: read:jira-work, storage:app and report:personal-data. Only official Atlassian account reporting uses app authorization. There is no fallback to app-authorized Jira reads, source writes, external analytics or AI.

Validation uses automated tests and bounded synthetic cloud fixtures. No penetration test, full attack-matrix coverage, maximum-load SLA or paid customer installation is claimed.

Support

Contact support@profitsignallabs.dev or the support portal. Terms provide a response within 24 hours for requests Atlassian marks critical, and five business days for others. These are response deadlines, not resolution guarantees. No additional uptime percentage or paid bounty is promised. Send sanitized symptoms and approximate time; agree a safe covered channel before sending sensitive data or exploit details.