Heartbeats for JSM: privacy policy and terms
Last updated: November 16, 2026
Heartbeats for Jira Service Management (“Heartbeats”) is an Atlassian Forge app made by Zeustable (“we”, “us”). It watches scheduled jobs and raises a Jira Service Management alert when a job stops checking in. This policy explains what data Heartbeats collects, why, where it is stored, how long it is kept, who it is shared with and how to contact us. How we protect that data is described in the separate security policy.
1. Data Heartbeats collects and why
| Data | Source | Why it is needed |
|---|---|---|
| Heartbeat settings: name, description or runbook note, expected interval, grace period, alert priority, paused state | Entered by your Jira admins | To know which jobs to watch, when they are late and how to word the alert |
| A random ID and secret ping token for each heartbeat | Generated by the app | To accept check-ins only from your own jobs |
| Status: time of the last ping, up/down state, whether an alert is open, last alert time, last error | Recorded by the app | To detect missed check-ins and show status on the settings page |
| Your Jira Service Management API integration key | Entered by your Jira admins | To open and close alerts in your own Jira Service Management site |
Heartbeats does not collect personal data about your users: no names, email addresses, Atlassian account IDs, IP addresses or issue content are stored. Pings carry no payload; the app reads only the heartbeat ID and token and records the time the ping arrived. Please don't put personal data in heartbeat names or descriptions. Heartbeats uses no cookies, analytics or tracking.
2. How data is used
Data is used only to provide the app's function: checking every five minutes whether each heartbeat is late, opening one alert in your Jira Service Management site when it is, closing that alert when the job checks in again, and showing status to your admins. We do not sell data, use it for advertising or use it to train AI models.
3. Where data is stored
All data is stored in Atlassian Forge storage on Atlassian's infrastructure, in the data residency region of your Atlassian site, and is encrypted at rest by Atlassian. The integration key is kept in Forge's secret storage. Heartbeats has no developer-hosted servers or databases, and we (the developer) have no access to the data stored by your installation.
4. Sharing, third parties and subprocessors
- Atlassian (hosting, storage and compute through the Forge platform). Atlassian's handling of data is covered by your agreement with Atlassian and the Atlassian Privacy Policy.
- Your own Jira Service Management site. When a job is late, the app sends the heartbeat name, description, interval, last ping time and priority to your site's alert API at api.atlassian.com, so the alert appears for your on-call team. This is the app's only outbound connection.
We use no other subprocessors and share no data with any other third party. We would disclose data only if required by law, and since we cannot access customer data stored in Forge, we would refer such requests to Atlassian or to you.
5. Retention and deletion
A heartbeat and its status are kept until an admin deletes it in the app. An admin can remove the integration key at any time by clearing it in settings. When Heartbeats is uninstalled, Atlassian deletes the app's Forge storage for that site, including the integration key, under Atlassian's Forge data retention rules. Alerts already created live in your Jira Service Management site and follow its own retention settings.
6. Your rights and GDPR
Heartbeats processes no end-user personal data. Your admins can view, change and delete everything the app stores directly from its settings page. For any privacy request or question, including access, correction or deletion requests under the GDPR or similar laws, contact us below and we will respond within 30 days.
7. Website
This documentation page is a separate website hosted by Render. It receives no data from the Heartbeats app and uses no analytics cookies. Like any web host, Render may keep standard request logs (such as IP address and browser type) for security and operations.
8. Changes to this policy
We will update the “Last updated” date when this policy changes, and will notify customers through the Marketplace listing or by email before any change that expands the data the app collects.
9. 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.
10. Privacy contact
Zeustable, privacy and support: support@norynta.com. We usually reply within one business day. To report a security issue, see the security policy.