Privacy policy

Last updated: 18 September 2026

Statuswatch is a Forge app for Jira. It shows how long a work item spent in each status, counted in the project's own working hours rather than around the clock. This policy describes what the app accesses, what it stores, and where that data goes.

Who provides this app#

Statuswatch is developed by Michael Klotz. For questions about this policy or about data handling, contact support@status-watch.io.

What the app accesses#

When someone opens a work item, the app reads that item's creation date, current status, due date, work type, components and labels, together with its status change history. The history request is filtered to status changes, and the app uses only the timestamps and the status values in it. To show current status names and categories it reads the list of statuses the project's workflows can reach.

On the project settings page it reads the project's work types, components and labels so that an administrator can pick from them instead of typing them, and it checks whether the person making a change is permitted to administer the project.

Every one of these calls is made as the signed-in user, never as the app. Statuswatch can therefore only ever read what that person was already permitted to read.

What the app stores#

One configuration record per project: the working-hours calendars an administrator has set up — working days, start and end times, an optional break, a list of holidays, and a time zone. It is held in Atlassian's Forge storage on the site itself.

That record contains no personal data: no names, no account identifiers, no work item content. Nothing else is stored. The durations shown on a work item are recalculated each time the panel opens and are not kept.

Where data goes#

Nowhere outside Atlassian. The app runs entirely on Atlassian's Forge platform and makes no requests to servers outside it. No data is sent to the developer, to analytics services, or to any third party. The app qualifies for Atlassian's Runs on Atlassian programme, which requires exactly this.

Retention and deletion#

The configuration record stays until an administrator changes it or the app is uninstalled; uninstalling the app removes it from the site. Because nothing else is stored, there is nothing further to retain or delete.

Changes to this policy#

Material changes will be reflected on this page, along with an updated date at the top.