Privacy / Updated 31 August 2026

Your incident data stays in its workflow.

This notice describes AfterIncident, a Jira Cloud app provided by the Atlassian Marketplace partner TechnofyStore. Contact support@callsiq.com for privacy questions or requests.

What the app processes

The app reads Jira issue fields needed to display and reconcile actions: identifiers, project and issue type, summary, workflow status, assignee, due date, creation time, links, labels, components, configured service fields and evidence references. Source incident descriptions are not copied to app storage. A description entered when creating an action is sent to Jira as part of that native issue.

Forge stores project settings, issue identifiers and keys, action state, dates, evidence notes or references, review results and rationales, recurrence candidate references, idempotency records and audit events. Free text entered by users may contain personal data. Avoid entering credentials, secrets or unnecessary sensitive information.

People and accountability

Atlassian account IDs identify people who add or verify evidence, complete reviews or perform audited actions. Domain records refer to a separate identity record, allowing that identification to be erased while retaining an unattributed event. Current display names and assignees are retrieved from Jira; they are not persisted as a separate directory by AfterIncident.

The app periodically reports stored account identifiers to Atlassian's personal data reporting service and removes the identity link when Atlassian requests erasure or invalidation. Users can also use “Privacy and data retention → Erase my stored identity”. This does not remove text they supplied or native Jira records. New activity may create a new identity record.

Purpose and access

Processing supports the customer's corrective-action workflow, evidence, follow-up reviews and audit trail. Users access content subject to Jira permissions; project configuration requires administrator permission. Automated jobs use the app's Jira access to reconcile state and find candidates. Candidates are checked against the viewing user's Jira access before display.

Hosting and recipients

The application backend and metadata storage use Atlassian Forge, scoped to the installation. The app has no external application backend, AI service, advertising SDK or analytics tracker. It does not fetch external evidence URLs; a user opening a URL visits that destination under its own privacy terms.

Atlassian processes and hosts the application's data as part of Forge. See Atlassian's privacy policy. Product support correspondence is handled separately by TechnofyStore through its support email service. Do not email incident contents or credentials unless an appropriate secure process has been agreed.

Retention and deletion

Metadata is retained while installed unless removed using the app's controls or through a verified request. Project administrators can delete an action's app metadata, including its evidence records, reviews, signals and audit history, using its app record reference. Native Jira issues, comments, attachments and links remain in Jira.

Uninstallation removes app access but is not immediate physical deletion. Forge currently retains hosted app data for 28 days after uninstall; recovery is not automatic on reinstall. Platform backup and deletion handling are governed by Atlassian. See the Forge storage documentation.

Your choices and requests

The installing customer determines what information to enter and who can access it. Contact your Jira administrator for access or correction to Jira records and app metadata. You may also contact support to request access, correction, export, erasure or information about processing. We will verify identity and authority and coordinate with the customer where necessary. Applicable statutory rights, including the right to complain to a supervisory authority, are not limited by this notice.

This documentation website

This public website is hosted on Cloudflare and is separate from the Forge app. It does not receive Jira data and sets no application cookies or analytics trackers. Cloudflare necessarily processes connection information such as IP address and browser request metadata to deliver and secure the site. See Cloudflare's privacy policy.

Changes

Updates will be published here with an updated date. Material changes affecting the application will also be described in release information where applicable.