Privacy

The short version

Calibro Track is an Atlassian Forge app. The time entries, approvals and reports it creates are stored inside your own Jira site’s infrastructure, not on a server of ours. We hold no copy of them and we cannot read them.

This website collects no analytics and sets no cookies.

The app

What it stores

Calibro Track keeps its own records in Forge SQL, a database Atlassian provisions and runs for the app inside your site’s environment. Those records are:

• Time entries — the issue and project the work was against, the Atlassian account ID of the person who logged it, the date, the number of minutes, an optional description, and whether it is draft, submitted or approved.
• Approvals — the account ID of the approver, the decision, an optional reason, and when it was made.
• Project approvers — which account IDs may approve time for which projects.
• Saved reports — the report name, the owner’s account ID, and the grouping and filters that define it. Computed results are cached alongside for speed.
• Jira field metadata — the names and types of fields available to group a report by, cached so building a report does not re-enumerate them every time.
• Preferences and team settings — week start, date and duration format, weekly target, and whether approved time is locked.

The description on a time entry is free text you write. It is the one field in the app that holds something because a person typed it rather than because Jira already knew it, so treat it the way you would treat a Jira comment.

What it reads from Jira

The app holds three permissions and no others:

• read:jira-work — issues, projects and field values, so that a report can group by them.
• read:jira-user — resolving account IDs to display names, so a timesheet shows people rather than identifiers.
• storage:app — the app’s own database, described above.

Nothing in the app writes to Jira. Everything it reads is bounded by the Jira permissions of whoever is asking: a report covers only the projects that person can already browse.

Where it goes

Nowhere. The app declares no external egress at all — there is no address it is permitted to send anything to, and that is enforced by the Forge platform rather than promised by us. Your data is processed in the region Atlassian hosts your Jira site in and stays inside Atlassian’s infrastructure for the whole of its life.

We have no production access to it. If you report a bug, we can see what you choose to tell us and nothing else.

Roles

For data the app handles, your organisation is the controller and Calibro Software is a processor acting on your instructions. Atlassian is a sub-processor, and in practice the only one: it provides the compute and the storage the app runs on, and its own privacy commitments cover that layer.

Deletion

Uninstalling the app removes its database and everything in it. There is no separate deletion request to file with us, because there is no copy for us to delete. Individual entries can be deleted from inside the app at any time.

Changes

When this policy changes in a way that matters, the date at the top changes and the change is noted in the changelog like anything else we ship. We will not quietly broaden what we collect.