Privacy policy

Last updated: 29 September 2026

Statuswatch is a Forge app for Jira, with an optional part for Confluence. It shows how long a work item, or a Confluence page, 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, and what this website records about its visitors.

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. Jira returns the item's change history as a whole, because a filter on the request would leave out status changes that came in through an import or a migration. The app picks the status changes out of it and uses only their timestamps and status values; the rest is discarded as it is read and is neither stored nor shown. To show current status names and categories it reads the list of statuses the project's workflows can reach.

On the project page it also reads the display name of each work item's assignee, to show typical stays per person. The name is shown to the person looking at the page, who could already see it in Jira, and is neither stored nor sent anywhere.

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.

A Statuswatch step in a Jira Automation rule reads the work type, components, labels and project of the work item the step names, to choose the calendar to count in. It reads them as the person who connected the step in the rule builder.

Atlassian tells the app whether the site's licence is active. The app uses that to decide whether to measure, and does not store it.

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

What the app does with nobody signed in#

Three things run in the background, as the app, because there is no person to run them as. Each happens only where an administrator has switched it on, or, for Confluence, where the app has been installed on Confluence.

• Report fields. Where a project administrator has switched on the report fields, the app reads the status history of that project's work items every hour and writes figures onto them: the minutes spent in the current status, when that was counted, and, for fields a Jira admin created for it, the minutes spent in one chosen status.
• Alerts. Where a project administrator has set up alerts, the same hourly run checks that project's open work items against the limits and asks Jira to email the assignee of one that is past its limit. The app does not read who the assignee is; Jira fills in the person and sends the email.
• Confluence. When Confluence reports that a page was created or changed, the app reads that page's status and when it was set, and records a change of status.

In these three the app reads the same fields as above and nothing more. In Confluence it also reads, as the signed-in user, the pages of a space by status, the titles of pages it has recorded (through a search), the names of the spaces it has recorded pages in, and whether that user may administer the space before a setting is saved. The app writes nothing to Confluence. See In Confluence.

What the app stores#

Everything the app stores is held in Atlassian's Forge storage, on Atlassian's platform, for your site alone. None of it contains personal data: no names, no account identifiers, no email addresses, no work item or page content.

• Per Jira project, one settings record: the working-hours calendars (working days, hours, an optional break, holidays, a time zone), which work types, components or labels each calendar applies to, whether report fields are switched on, and the alert limits (a status name and a number of hours each).
• Per Jira project with alerts: the ids of the work items an email has been sent about and the time their current stay began, so that each email is sent once. Entries disappear when the work item moves on.
• Per "Time in status" field a Jira admin created: the field's id and the name of the status it counts.
• Per Confluence page that has had a status: the names of its statuses and the moments they changed. No title and no author.
• Per Confluence space with a setting: which Jira project's working hours the space counts in.

Where report fields are switched on, the figures themselves are kept on the work items, in Jira's own fields: numbers of minutes and a date. The durations shown on a work item, on the project page or on a Confluence page are recalculated each time and are not kept.

What the developer receives from Atlassian#

Separately from the app, Atlassian Marketplace gives every vendor a record of the sites that try or buy its apps: the organisation's name and site address, the licence's size, dates and status, and the names and email addresses of the technical and billing contacts the organisation gave Atlassian. We receive this from Atlassian, not through the app, and the app itself still sends us nothing.

We use it to answer support requests, to tell a site's admins about a change that affects their installation, and to keep the accounts the law requires. We do not use it for advertising and do not pass it on. It is kept for as long as the licence runs and for the period tax law requires afterwards. To see, correct or delete what we hold about you, write to privacy@status-watch.io.

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#

What the app stores stays until an administrator changes it or the app is uninstalled; uninstalling the app removes all of it. The figures in the app's two built-in report fields stay on the work items while the app is installed; switching the report fields off stops the counting and leaves the figures already written, with their date. A "Time in status" field that a Jira admin created is a Jira field of yours: it stays, with its values, until a Jira admin deletes it. Because nothing else is stored, there is nothing further to retain or delete.

This website

This website, status-watch.io, counts its page views with Cloudflare Web Analytics. On every page a small script from Cloudflare reports the address of the page, the address of the page the visitor came from, the browser, operating system and type of device, the country, and how quickly the page loaded. Query strings are not recorded. Cloudflare states that Web Analytics uses no cookies and no other storage in the browser, and does not fingerprint visitors by their IP address, their browser or anything else.

We see totals only: how often each page was read, and from which countries and websites people arrived. We use them to learn which parts of the documentation are read, and for nothing else. Cloudflare, Inc. processes this data for us as the host of this website; see Cloudflare's privacy policy. The legal basis is our legitimate interest in knowing whether the documentation is used, Article 6(1)(f) GDPR.

This concerns the website only. The app uses no analytics of any kind and sends nothing outside Atlassian, as described above.

Changes to this policy#

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