Privacy Policy

Last updated: 28 October 2026

This policy explains what the Heartbeat Monitor for JSM app and the backfillab.com website ("we", "us") access, why, and where that information is kept. Backfillab is operated by Maxyme Tuffery. Our Google Sheets add-on Issuegrid has its own policy at issuegrid.app/privacy.html.

Summary

• Heartbeat Monitor for JSM runs on Atlassian Forge. Its data is stored in Forge storage on Atlassian's infrastructure. We do not run our own servers or database for it.
• Ping payloads are not stored, except a short optional status note (200 characters max).
• The Opsgenie API key used for import is used once and never stored.
• We do not sell your data, show ads, use analytics or tracking, or use your data to train AI models.

Jira permissions the app requests

• read:jira-work: to list the projects, issue types and priorities you can choose for incidents, and to read the status and workflow transitions of incidents the app created.
• write:jira-work: to create incidents, comment on them when a job recovers, resolve them when you turn automatic resolution on, and send Jira notifications to the people you pick.
• storage:app: to store monitor settings and events in Forge storage.
• report:personal-data: to report the Atlassian account IDs the app stores to Atlassian's personal data reporting API, so that we learn when an account is deleted and can erase it.

The app also checks that the person using its admin page is a Jira administrator.

Information the app stores, and where

All of the following is stored in Atlassian Forge storage, on Atlassian's infrastructure, for your Jira site only:

• Monitor settings: name, expected interval, grace period, target Jira project, issue type and priority, the Atlassian account IDs of the people to notify, whether automatic resolution is on, and the creation date.
• Monitor status: the secret token of the monitor's ping URL, the time and status (ok, fail or start) of the last ping, the key of the open incident, and the last error message if creating or updating an incident failed.
• Event log: the last 50 events per monitor (pings, late, down, incident created, recovered, errors), each with an optional short note of up to 200 characters taken from the ping.

The app does not store the rest of a ping's body, its headers or the caller's IP address. Incidents and comments the app creates are stored in your Jira site like any other issue.

Atlassian account IDs

The only personal data the app stores is the Atlassian account IDs of the people you choose to notify. It does not store their names, email addresses or avatars; Jira shows those when needed. Account IDs are sent to Jira only to send its notifications for an incident.

As Atlassian requires, the app reports the account IDs it stores to Atlassian's personal data reporting API once per reporting cycle (7 days by default). When Atlassian reports that an account has been closed, the app removes that account ID from every monitor.

Opsgenie import

When you use the Opsgenie import (beta), the API key you paste is sent once from Forge to Opsgenie (api.opsgenie.com or api.eu.opsgenie.com, depending on the region you choose) to list your heartbeats. The key is not stored or logged. Only the heartbeat names, intervals and enabled states are used, to create monitors. These Opsgenie domains are the only external services the app contacts.

Operational logs

To troubleshoot, the app writes short operational logs through Atlassian's Forge logging: monitor IDs, state changes, Jira issue keys and error messages. Logs never contain ping URLs, tokens, ping payloads or Opsgenie keys. They are kept by Atlassian according to Forge's log retention.

How information is used

Information is used only to provide the features you ask for: watching your jobs' check-ins, creating, commenting on and resolving Jira incidents, notifying the people you choose, and meeting Atlassian's personal data reporting requirements. We do not use it for advertising, profiling or AI model training, and we do not sell or share it with third parties.

The backfillab.com website

The website sets no cookies and uses no analytics. It is hosted by Netlify, which may keep standard server logs (such as IP address and pages requested) to operate and secure the service. If you email us, we use your email only to answer you.

Third parties

• Atlassian runs the app on Forge and stores the data described above, under Atlassian's Privacy Policy. Licences are sold through the Atlassian Marketplace.
• Opsgenie (an Atlassian product) is contacted only when you run the import.
• Netlify hosts the backfillab.com website.

Deleting your data

• Deleting a monitor in the app deletes its settings and event log.
• Uninstalling the app removes its stored data from Forge storage, according to Atlassian's Forge data handling. Incidents already created in Jira stay in Jira until you delete them.
• To ask about or delete any other information, email support@backfillab.com.

Your rights

Depending on where you live, including in the European Union, you may have the right to access, correct or delete personal data about you, and to object to or restrict its use. Email us to exercise these rights. You can also complain to your data protection authority.

Security

Each ping URL carries its own secret token, compared in constant time; a wrong token returns a plain 404. You can regenerate a monitor's token at any time in the app. All traffic to Atlassian and Opsgenie uses HTTPS.

Children

Our apps are business tools and are not directed at children under 16.

Changes

If we change this policy, we will update the date at the top of this page. Significant changes will be announced on backfillab.com.

Contact

Operator: Maxyme Tuffery (Backfillab)
Email: support@backfillab.com