Burnwise privacy policy
Last updated 7 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).
| Data | Purpose |
|---|---|
| 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 rates | Financial settings entered by your administrators |
| Atlassian account ids (no names are stored) | Who logged time, who manages what, the audit log |
| Audit log | Who changed financial settings, when, and the old and new values |
| In-app notifications | Budget and margin alerts, timesheet approvals |
| Alert email address (only for people who turn on “Email me alerts”) | Sending email copies of alerts |
| Invoice details (company name, address, email, tax ID, payment terms, notes, logo) and client billing addresses | Printing PDF invoices |
| Billed invoice records (lines, totals, reference, and when they were put in an accounting file) | Not billing anything twice |
| Slack and Teams webhook URLs (Forge secret storage), and what each channel gets | Posting alerts to the channels an administrator chose |
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 these to Transactful’s email server, Broadcast:
Before any alert goes to an address, Burnwise emails a 6-digit code to it (through Broadcast, as below), and the person must enter that code in Burnwise. A new or changed address needs a new code. Burnwise keeps only a hash of the code.
- that person’s email address, the project name and the alert text (for example the budget, the amount spent, the expected cost and the margin);
- the work of the last 7 days: issue and Epic keys and titles, hours, and their cost where that person may see it;
- the project’s billing totals: earned, invoiced, not invoiced yet, and the last invoice;
- the areas of concern (for example, spending ahead of the work done).
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.
- The rates of individual people are never included. Cost is left out wherever it could reveal one person’s rate to someone who may not see rates.
- Each person can turn email alerts off at any time. The emails stop at once.
Slack and Microsoft Teams alerts (optional)
Nothing is posted unless a finance administrator adds a channel webhook, in Settings → Slack & Teams. Then, when a budget, expected-cost or margin alert fires, Burnwise posts the project name, the alert text, the areas of concern and the hours of the last 7 days (with the name of the Epic that took the most time) to that channel. The administrator chooses one message per project each day, or one message per alert.
- Billing totals (earned, invoiced, not invoiced yet, last invoice) are posted only if the administrator turns them on for that channel.
- A channel never gets the cost of single issues or Epics, or the rates of individual people.
- The webhook URL is kept in Forge secret storage and is never shown again in full.
Xero and QuickBooks Online files
Burnwise does not connect to Xero or QuickBooks. A finance administrator can download an invoice as a CSV file and import it into their accounting system. The file is made in your Jira site and goes only to the person who downloads it.
What Burnwise does not do
- No other data leaves Atlassian. The only external calls are email alerts and the optional Slack and Teams alerts above.
- No third-party analytics, tracking or advertising.
- Transactful staff cannot access the data in your site’s Forge storage. Transactful can see the alert emails that Broadcast sent.
Subprocessors
- Atlassian: Hosting: Burnwise is built on Atlassian Forge, and its data is stored in Forge storage.
- Amazon Web Services: Email delivery for email alerts, through Amazon SES in us-west-2 (United States).
Chosen by you, and used only when an administrator turns them on: Slack and Microsoft (Teams and Power Automate). They act for you, not for Transactful.
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.