Security and support

Source reads run as the current Jira user. Project administrators alone change policies. Each paid resolver checks production entitlement server-side. App storage is installation-scoped; personal reviews are additionally scoped to the trusted actor and source issue. Direct payloads cannot replace actor, installation or license context.

Immutable policy revisions reject conflicting updates. Source approvals, fields and policy version are rechecked before releasing results. Repeated, partial, late or oversized source pages cannot produce a complete all-clear. Reports expire after one minute. Erasure uses a deletion watermark to prevent stale query results from reappearing.

Permissions: read:jira-work, read:servicedesk-request, storage:app and report:personal-data. Only Atlassian privacy reporting uses app authorization; Jira reads never fall back to app access. There are no issue-write scopes or external network destinations.

Validation uses synthetic development fixtures, automated tests and bounded cloud checks. No independent penetration test, certification, universal attack coverage or load SLA is claimed.

Support

Contact support@profitsignallabs.dev or the support portal. Response commitments in the customer terms are 24 hours for requests identified by Atlassian as critical, and five business days for other requests. Response is not guaranteed resolution; no additional uptime percentage is offered.

Start with sanitized steps, time, app version and error code. Do not send credentials or Jira exports. Request a covered secure channel before disclosing sensitive details. No public bug-bounty payment commitment is offered.