Label Cleanup for Jira - Privacy Policy
Effective date: 11/11/2026 · Last updated: 11/11/2026
This policy explains how Label Cleanup for Jira ("the app"), published by Taskhooker Pty Ltd ("we", "us"), handles data. The app is an Atlassian Marketplace app built on Atlassian Forge and Runs on Atlassian.
Summary
- Nothing leaves Atlassian. The app has no external servers, makes no outbound network calls, and uses no analytics, tracking or third-party services.
- We never receive your data. Everything the app stores lives in Atlassian-hosted Forge storage on your own Jira site. Taskhooker cannot read it.
- The app does store some data on your site - job records and label usage counts - described in full below.
1. Data the app reads
Through Atlassian's APIs, on your Jira site only:
- The list of labels on the site.
- The Labels field and key of work items, to count label usage and to apply a change you confirmed.
- Whether the current user holds the Administer Jira permission.
The app does not read work item summaries, descriptions, comments, attachments or any other field.
2. Data the app stores (Forge storage on your site)
| Data | Why | Kept for |
|---|---|---|
| Job records: action (rename, merge, delete or scan), label names, counts, status and timestamps | Show progress and job history | Last 50 jobs; older jobs are removed automatically |
| Atlassian account ID of the administrator who started a job | Record who started each job | With the job record (last 50 jobs) |
| Work item keys targeted by an active change job | Apply the change to exactly the work items you previewed | Removed when the job finishes, is cancelled, or its preview expires |
| Up to 50 failed work item keys per job with Jira's error message | Show you what could not be changed | With the job record (last 50 jobs) |
| Label usage counts from the latest scan | Show exact counts per label | Until the next scan replaces them |
Forge storage is hosted and encrypted at rest by Atlassian and follows your site's Atlassian data residency.
3. Changes the app makes
The app only changes the Labels field, only on work items listed in a preview that a Jira administrator confirmed. Each change appears in the work item's normal history. Watcher notifications are off unless the administrator turns them on.
4. Sharing
None. No data is sold, shared or sent to any third party or to Taskhooker.
5. Personal data and your rights
The only personal data stored is the Atlassian account ID of the administrator who started a job. It stays on your site and rolls off with the job history (last 50 jobs). Uninstalling the app removes all of its stored data per Atlassian's Forge data lifecycle. For access or erasure requests, or any privacy question, contact us through the Taskhooker support portal or at support@taskhooker.com; we will help you remove specific records.
6. Cookies and tracking
The app sets no cookies and collects no telemetry. It runs inside Jira, where Atlassian's own policies apply. This website (labels.taskhooker.com) uses no analytics or tracking cookies.
7. Changes to this policy
We update this page when the app's data handling changes. The date above shows the latest change.
8. Contact
Taskhooker Pty Ltd, Melbourne, Australia · support@taskhooker.com · Support portal