Burnwise

Burnwise privacy policy

Last updated 4 October 2026

This policy covers Burnwise, the Jira Cloud app. It is published by Transactful, a company incorporated in Canada. For the transactful.com website itself, see the site privacy policy.

What Burnwise stores

Burnwise is built on Atlassian Forge. Its data is stored in your Atlassian site’s Forge storage (Forge SQL) and stays in the same region as your Jira data (data residency).

DataPurpose
Jira worklogs (id, issue, author account id, start, duration, description)Calculate cost and billable work
Jira issue facts (id, key, summary, project, parent or Epic, remaining estimate, status category, story points)Which work belongs to a project, work done, reports
Rates, roles, budgets, expenses, clients, teams, schedules, holidays, exchange ratesFinancial settings entered by your administrators
Atlassian account ids (no names are stored)Who logged time, who manages what, the audit log
Audit logWho changed financial settings, when, and the old and new values
In-app notificationsBudget and margin alerts, timesheet approvals
Alert email address (only for people who turn on “Email me alerts”)Sending email copies of alerts

Display names are fetched from Jira when they are shown and are not stored. Email addresses from Jira are looked up during a CSV rate import (to match rows to Atlassian accounts) and to suggest an alert address, and are not stored. The only stored email address is the one a person enters for their own email alerts.

Email alerts

Alerts always appear in Burnwise under Notifications. Email alerts are off unless a person turns them on, in Notifications → Email me alerts. Only budget, expected-cost and margin alerts are emailed. When an alert fires, Burnwise sends that person’s email address, the project name and the alert text (for example the share of the budget spent, or the expected cost) to Transactful’s email server, Broadcast. Broadcast sends the email through Amazon SES in the us-west-2 region, in the United States, and keeps a copy of each email for delivery records.

What Burnwise does not do

Subprocessors

Retention and deletion

Data stays while Burnwise is installed. When you uninstall, Atlassian’s Forge data lifecycle applies: data is kept for the platform’s retention period and then deleted. Administrators can export reports and worklogs as CSV at any time.

Contact

Questions or requests: [email protected]. For help with the app, see Support.