Heartbeats for JSM: privacy policy and terms

Last updated: October 27, 2026

Heartbeats for Jira Service Management (“Heartbeats”, “we”) is an Atlassian Forge app that watches scheduled jobs and raises a Jira Service Management alert when a job stops checking in. This page explains what data Heartbeats handles and the terms of use.

1. Data Heartbeats stores

• Heartbeat definitions your admins create: name, expected interval, grace period, alert priority, runbook note, the secret ping token, last ping time and current status.
• The Jira Service Management API integration key your admin enters, kept in Forge secret storage.

Heartbeats does not store end-user personal data: no names, email addresses, account IDs or issue content. Pings carry no payload; only their arrival time is recorded.

2. Where data lives

All data is stored in Atlassian Forge storage on Atlassian's infrastructure, in the data residency region of your Atlassian site. Heartbeats runs entirely on Atlassian (“Runs on Atlassian”). The only calls it makes are to your own site's Jira Service Management alert API, to open and close alerts. We (the developer) have no access to your data.

3. Retention and deletion

A heartbeat stays until an admin deletes it in the app. When an admin uninstalls Heartbeats, Atlassian deletes the app's Forge storage for that site, including the integration key, according to Atlassian's Forge data retention rules.

4. Personal data and GDPR

Heartbeats processes no end-user personal data. Alerts it creates live in your Jira Service Management site and are governed by your Atlassian agreement. For any request, contact us below.

5. Terms of use

Use of Heartbeats is governed by the Atlassian Marketplace End User Agreement. Heartbeats is provided “as is”, without warranties beyond those in that agreement.

6. Contact and support

Email getsurfaced@proton.me. We usually reply within one business day.