Native Timesheets for Jira, operated by ResiliaTech. Last updated 1 October 2026.
Native Timesheets 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 sends no data to ResiliaTech's servers or to any third party, and we cannot browse your timesheets.
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, as the signed-in user. This covers worklogs (dates, hours, comments, authors), issue keys, summaries and project names, and people's Atlassian account IDs and display names. The app only sees what that user can already see in Jira.
Worklogs the app writes. When you enter hours, the app creates, updates or deletes ordinary Jira worklogs as you.
The app's own records, kept in Atlassian Forge storage for your site:
settings: currency, approvers (account ID and display name), billable projects with rate and client name, and Xero export defaults;
each person's pinned timesheet rows (issue keys and summaries);
weekly submissions: status, submitter name, a snapshot of the week's hours per issue, approver notes and a short history of actions.
Reminder emails. If an admin turns reminders on, the app asks Jira to email people who logged time but didn't submit. Jira sends these emails through its own notification system.
The app has no advertising, and no analytics or tracking of any kind.
Where the data is stored
Worklogs stay in your Jira site, as normal Jira data.
The app's own records 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.
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 worklogs 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 an issue key 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
Worklogs are Jira data. They stay in Jira until your users or admins delete them, including after the app is uninstalled.
The app's own records are deleted by Atlassian after the app is uninstalled from your site, in line with Atlassian's Forge data retention policy.
The app runs inside Atlassian's infrastructure. It uses the minimum Jira permissions needed:
read and write Jira work, for worklogs and issues;
read users, to pick approvers;
app storage.
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.