AdminData, export and uninstalling

Data, export and uninstalling

The short version: your time data lives inside your own Jira site, we can’t see it, and if you uninstall the app it goes with it. Export before you do that.

Where your data lives

Calibro Track is built on Atlassian Forge. Time entries, approvals and saved reports are stored in Forge storage attached to your site, and all processing happens inside Atlassian’s infrastructure. There is no Calibro server holding a copy, and no data egress for your security review to assess.

Custom field values shown in reports are read from Jira through Atlassian’s own APIs when a report runs, and cached briefly for performance. They aren’t copied anywhere else.

Getting your data out

Any report exports to CSV, one row per time entry. To export everything, build a report with a date range covering all your history, no filters, grouped by user, and export that — it gives you every entry with its issue, date, duration, description and approval status.

Uninstalling deletes your time data

When a Forge app is uninstalled it loses access to its storage, and the data is removed. We can’t recover it for you afterwards, because we never had it. Export a full CSV before you uninstall, even if you’re only trialling something else — reinstalling later gives you an empty app, not your history back.

Every report exports to CSV from here — one row per time entry, not the summary.

What happens to Jira’s own worklogs

Nothing. Calibro Track keeps its own time entries and doesn’t modify Jira’s native worklog field, so uninstalling doesn’t change anything on your issues.

Retention

We don’t delete old entries. Everything you log stays until you delete it or uninstall the app.