PRIVACY & SECURITY · 31 AUGUST 2026
Your data, explained.
This notice describes CustomerChase for Jira Service Management Cloud, published by TechnofyStore.
What the app stores
The app stores project and issue identifiers, policy settings and steps, business calendars, administrator-authored templates, cycle timestamps and status, action results, comment and transition identifiers, diagnostic codes and audit history. Configuration snapshots preserve the sequence of existing cycles.
What it reads temporarily
Jira issue summaries, reporter and assignee display names, request participants, public comments, status, request type, priority, labels and organizations are read when needed for permission checks, policy matching, reply detection or reminder rendering. The app does not persist ticket descriptions, customer comment bodies, email addresses or external access tokens in its own storage.
Rendered reminders are public Jira comments. They can include values selected through template variables, and remain subject to Jira/JSM access, notification and retention settings.
Where processing happens
The application runtime and its application data use Atlassian Forge. The app declares no third-party runtime egress. Forge scopes storage to each installation. This documentation website is separate from the Forge app and does not receive Jira data.
Persistent Forge storage inherits the Jira site’s supported data residency location and migrations. This does not promise that all transient compute or operational logs remain in that location. See Forge data residency.
Operational logs
Forge logs record event names, installation, project, issue and cycle identifiers, action results, diagnostic codes and aggregate scanner counts. Customer comment bodies and user profile records are not intentionally logged. Logs are not exported to a third-party logging service.
Access and permissions
Project administrators manage configuration. JSM agents can use operational controls only where their Jira access permits. Issue-security checks use the signed-in caller’s Jira permissions.
| Permission | Purpose |
|---|---|
| Jira work and user read | Project/issue metadata, permissions, workflows and app-actor identity. |
| Jira/JSM write and request read | Request checks, public reminders and configured customer transitions. |
| Forge storage | Configuration, follow-up state, diagnostics and audit history. |
Retention and uninstall
Application configuration and follow-up history are retained while the installation operates. Uninstall stops its operation. Atlassian’s hosted storage currently retains uninstalled app data for 28 days; reinstalling does not automatically restore it. Recovery requires customer consent and a support request within the platform’s recovery window. See Atlassian’s storage reference.
Uninstalling CustomerChase does not delete comments already posted to Jira. Your Jira administrators control those records.
Support information and requests
If you email support, TechnofyStore receives the contact details and information you choose to send, outside the Forge app. Send only information needed to resolve the request, and redact sensitive material. Contact support@callsiq.com for questions about access, correction, retention or deletion of support information and app data. We may need to verify the requester’s authority and coordinate with the site administrator or Atlassian.
This website
This documentation site has no CustomerChase analytics, advertising integrations or Jira-data collection forms. Cloudflare hosts this public website and may process connection and service-operation information, such as IP addresses and request metadata, when serving these pages. Cloudflare does not receive Jira issue data from the Forge app.
Our Data Processing Addendum describes the processing terms for customers who use the app.
Changes
Material changes to this notice will be reflected here with an updated date. This notice does not claim an independent security certification or replace the terms and privacy information supplied by Atlassian for its platform.