Firebreak data and security · Bushcraft Software

DRAFT. This page is pending legal review and isn't in effect yet. Our apps haven't launched.

Where it runs	Atlassian Forge. Firebreak runs on Atlassian's cloud infrastructure and is built to qualify for the Runs on Atlassian badge: no outside servers, no remote calls, no outside sign-in.
What it reads	Custom fields: name, type, when each was last used, how many screens and contexts use it, and whether it's locked Filters with their JQL and owners, including private filters where Jira lets an administrator see them Boards (estimation field and board filter), dashboards and gadget settings, screens, field contexts and workflows Projects, issue types, and the display names of the people who own filters, rules, boards and dashboards How many issues hold a value in a field, as a count. Firebreak doesn't read issue content. Your automation rules, only if you import the rules export. Jira doesn't let apps read rules directly.
What it changes	Nothing in the first release. Every Jira permission it asks for is read-only. A later version will move fields you choose to Jira's trash, where they can be restored. It needs two more permissions, so administrators approve it again when they upgrade.
What it stores	Scan results in Forge storage: each field, what uses it, how, and a short piece of evidence. Old scans are deleted after 30 days. From an automation import, only the rule ID, name, scope, component path and field for each reference, plus a fingerprint of the file. The export is read in your browser and never saved, including any webhook URLs, headers or secrets in it. Deletion simulation reports, kept as a record App settings
What leaves Atlassian	Nothing. Firebreak makes no calls to servers outside Atlassian.
Who at Bushcraft can see it	No one at Bushcraft Software can see your Jira data. We only see what you choose to send us in a support request.

Specific to Firebreak

Only Jira administrators can open Firebreak. It checks that you are an administrator on every request.
A deletion simulation lists who owns each affected item, so you know who to tell. Firebreak doesn't contact them.
Every simulation lists its blind spots: private filters it couldn't see, rules that pick a field at runtime, and other apps' configuration, which it can't scan.

Data residency

Firebreak keeps its data in Atlassian Forge storage, which Atlassian hosts. Where Atlassian supports data residency for Forge apps, that data follows the region of your Atlassian site.

Uninstalling

When you uninstall Firebreak, Atlassian deletes the data it stored in Forge storage, following Atlassian's Forge data retention rules. Firebreak leaves nothing behind in your Jira configuration that it didn't already find there.

Privacy policy and terms
How all our apps handle data
Questions: support@bushcraftsoftware.com

Last updated 2026-10-27

Firebreak: data and security

Specific to Firebreak

Data residency

Uninstalling

More