Privacy notice

1 October 2026. Provider: Jon Ander Irazusta Iribar, trading as ProfitSignal Labs. Contact support@profitsignallabs.dev. See the legal notice and customer terms and DPA.

Source processing

Jira reads use the signed-in user: issue/project IDs, update times, saved-filter queries, strict query validation, search membership and project permissions. Names and query text may contain sensitive user data. No source issue description, comment or value snapshot is retained.

Stored data

Project-owned configuration includes slot/name, filter ID or literal query, reference issue IDs and expectations, optional count bounds, revision and save time. Previous revisions remain until explicit all-revisions erasure. There is no automatic configuration expiry.

Optional personal checks contain slot and suite revision, PASS/FAIL, exact visible count, query/filter hashes and check/save/expiry times. They are scoped by an account hash and expire logically after 30 days, with platform TTL. A separate account ID and oldest-data timestamp are reported only to Atlassian’s official account-reporting API. Registry and deletion markers use up to 31 days of retention. No query text or membership snapshot is stored in personal history.

Controls

Saved content and past counts require current source permission checks. A bounded hourly privacy process follows Atlassian’s reporting interval and erasure instructions, without scanning Jira. Overdue or failed reporting blocks personal history access/saving. Users may erase their own project history; administrators may erase configuration. Deletion uses watermarks and bounded confirmation. Source Jira data and exported copies remain customer-controlled.

Architecture and recipients

Atlassian Forge hosts the app and installation-scoped storage. No external runtime destinations, analytics, advertising or AI integration are declared. Data is not sold or used to train AI. Platform operations, logs, backups and subprocessors follow Atlassian policies. Forge storage is retained for 28 days after uninstall; reinstall does not automatically restore it. Immediate physical backup erasure is not promised.

Provider correspondence and rights

Contact details and sanitized correspondence are processed to answer enquiries, provide support, meet legal obligations and protect the service. Depending on purpose, the basis includes contractual steps, legitimate interests or legal obligations. Applicable rights include access, correction, erasure, restriction, portability and objection; contact support or the competent data-protection authority. Start requests with sanitized steps, not Jira exports, issue content, account identifiers, passwords or tokens. Agree a protected, DPA-covered channel before sharing customer records.