Native Billing Export for Jira, operated by ResiliaTech. Last updated 10 October 2026.
Native Billing Export for Jira ("the app") is an app for Atlassian Jira Cloud. This policy explains what the app processes, where that data lives, and what we, ResiliaTech, can and cannot see.
In short: the app runs entirely on Atlassian's Forge platform, inside your Atlassian site. It reads worklogs with the signed-in user's own Jira permissions, never writes to Jira, and never connects to your accounting system. Invoice files are built in your browser. The app stores Atlassian account IDs only (billing users, per-person rates and who finalised a run), no names or emails, and sends nothing to ResiliaTech's servers or to any third party.
Who we are
ResiliaTech (Resilia Tech (Private) Limited), 14885 Pleasant Valley Road, Tynwald South, Harare, Zimbabwe. Contact: support@resiliatech.com.
For the data described below, your organisation, the Atlassian customer, is the controller. ResiliaTech provides the app, which processes the data on your organisation's behalf.
Data the app works with
Jira data read through Atlassian's APIs. Issues and their worklogs in the period you choose (author, date, time spent, issue key and summary), the projects and issue types used in settings, and the signed-in user's permissions. All reads run as the signed-in user, so the app only sees what that user can already see in Jira. The app has no permission to write Jira data.
People lookups. When an admin adds a billing user or a per-person rate, the app searches Jira users by name. When a page renders, it looks up display names for the account IDs it holds. Names are never stored.
The app's own records, kept in Atlassian Forge storage for your site:
settings: billing users (account IDs), invoice numbering, run defaults;
finalised runs: period, invoice numbers and totals, the IDs of the worklogs invoiced, and the account ID of who finalised or voided the run. No worklog text, names or emails.
Exported files are built in your browser from the data above and downloaded to your computer. They are not stored by the app.
Personal data. The app stores Atlassian account IDs as described above. Each week it reports those IDs to Atlassian's personal-data reporting service, as Atlassian requires of apps that store account IDs. When Atlassian reports an account as closed, the app removes that person from billing users and per-person rates, and replaces their ID in run history with a placeholder.
The app has no advertising, and no analytics or tracking of any kind.
Where the data is stored
Settings, clients and runs are kept in Atlassian Forge storage, which Atlassian hosts and isolates per site, under Atlassian's terms and privacy policy. Data residency follows Atlassian's Forge data residency rules for your site.
Exported files exist only on your computer, where you download them.
The app makes no calls to servers outside Atlassian ("no egress"). It is eligible for Atlassian's Runs on Atlassian programme.
What ResiliaTech can see
We cannot browse your site's Jira content or the app's records. Atlassian gives us operational logs and metrics for the app, such as error messages and how often features are used. These can contain technical identifiers, for example a page or issue ID in an error. We use them only to keep the app working and to resolve support requests. If you send us information in a support request, we use it only to help you, and delete it when it is no longer needed.
Sub-processors
Atlassian, which hosts the app on its Forge platform and runs Jira. We use no other sub-processors for app data.
Retention and deletion
Settings, clients and runs are deleted by Atlassian after the app is uninstalled from your site, in line with Atlassian's Forge data retention policy. Voiding a run deletes its worklog records; the run's summary is kept for audit.
When an Atlassian account is closed, the app removes that account ID from its records in the next weekly personal-data cycle, as described above.
The app runs inside Atlassian's infrastructure. It uses the minimum Jira permissions needed:
read Jira work, for issues and worklogs;
read Jira users, to search people when configuring rates and billing users, and to show names;
app storage, for settings, clients and runs;
report personal data, for Atlassian's weekly personal-data reporting.
All traffic is encrypted by Atlassian.
Your rights
Because your organisation controls this data, requests to access, correct or delete personal information should go to your Jira administrator first. We will help them fulfil any request. You can also contact us at support@resiliatech.com.
Changes
If we change this policy, we will update the date above. For significant changes, we will tell customers through the Marketplace listing.