Privacy Policy — Funatic Labs apps for Jira Cloud
Effective date: October 31, 2026 · Provider: Funatic Illuminations, doing business as Funatic Labs ("we", "us")
1. Scope. This policy covers our apps for Jira Cloud: Sprint History Search, Label Cleanup, Default Values, Bulk Link Changer, Blocked-By Close Guard, Release Date Search, Label Wildcard Search and Pinned Comments (each "an app"). It does not cover Atlassian's own products, which are governed by Atlassian's privacy policy.
2. Roles. Your organization controls its Jira data. Each app processes a minimal subset of it, inside Atlassian's platform, only to provide its features.
3. Data each app keeps.
- Sprint History Search: issue IDs, sprint IDs, names, states and dates, the time and ID of each Sprint field change, index status and admin settings, in Forge storage.
- Label Cleanup: settings, allowed groups and roles, hourly request counts, a label count cache (24 hours) and, for 30 days per change, the label names, the account ID of the person who made it and the issue IDs changed (for undo), in Forge storage.
- Default Values: the rules you create, stored by Jira as UI modifications (including any default users you choose), plus one record in Forge storage (the ID of the rule used as a template for new projects).
- Bulk Link Changer: settings, allowed groups and roles, hourly request counts and, for 30 days per change, the search, link types, the account ID of the person who made it and the issues changed (for undo), in Forge storage.
- Blocked-By Close Guard: nothing, and no Forge storage. Jira keeps the validator settings (link type, wording and statuses) in your workflow.
- Release Date Search and Label Wildcard Search: nothing, and no Forge storage. Jira keeps each search function result (version IDs or label values).
- Pinned Comments: no Forge storage. Only comment IDs and the time each was pinned, as a property on the issue. No comment text and no account IDs.
Blocked-By Close Guard, Release Date Search, Label Wildcard Search and Pinned Comments store no personal data. None of the apps store issue summaries, descriptions, comment text, attachments, user names or email addresses.
4. Purpose. Only to provide each app's features. We do not sell, share or use the data for any other purpose.
5. Where it is stored. Inside Atlassian's cloud (Forge hosted storage or your Jira site). No data is sent to Funatic Labs or any other party. Data follows your Jira site's data residency location.
6. Sub-processors. Atlassian only (hosting platform). No analytics, advertising, cookies or tracking.
7. Logs. Technical logs hold only IDs, counts, event names and error codes. Atlassian keeps them for up to 14 days.
8. Retention and deletion. Data is kept while an app is installed, or for the shorter periods above. On uninstall, Atlassian deletes the app's Forge storage (Atlassian keeps a recoverable copy for about 30 days, then destroys it). Settings Jira keeps in your workflows and Pinned Comments' issue property (comment IDs and times only) stay in your Jira site under your control until you remove them. Jira manages the saved search function results.
9. Security. Atlassian encrypts data in transit and at rest. Admin features are limited to Jira administrators or the people they allow. Report security issues to support@funaticilluminations.com.
10. Your rights. For questions or requests about personal data (such as account IDs in Label Cleanup or Bulk Link Changer change records, or default users in Default Values rules), contact support@funaticilluminations.com.
11. Changes. We may update this policy. We will post the new version here with a new effective date; continued use after that date means you accept it.
Contact: support@funaticilluminations.com