Field Hygiene for Jira is a Jira Cloud app built on Atlassian Forge. This policy explains what data it accesses, the one thing it stores, and why.
What Field Hygiene accesses
Field Hygiene reads your site's custom field metadata (name, type, screen and usage
information, description) and project list, using the read:jira-work and
manage:jira-configuration scopes. Every interactive scan acts as the admin
viewing the page — it can never surface anything that admin couldn't already see in Jira
themselves.
What Field Hygiene stores
One thing, and only one: a daily snapshot of four aggregate counts for the Trends chart — total custom fields, duplicate-name groups, unused fields, and possible duplicates. Never a field name, field ID, project name, or any other identifying content — counts only. Snapshots are kept for 90 days and deleted automatically after that. Everything else Field Hygiene shows you (duplicates, unused fields, missing descriptions, field-count limits) is computed fresh, in memory, on every page load — nothing about it is written anywhere.
Where your data goes
Nowhere outside Atlassian. Field Hygiene runs entirely on Atlassian Forge, with zero external domains in its manifest. It makes no calls to any third-party service, uses no external analytics, and has no servers of its own.
Data retention and deletion
Daily Trends snapshots are pruned automatically after 90 days. Uninstalling Field Hygiene removes its storage entirely — nothing survives an uninstall, because nothing beyond those aggregate counts was ever kept.
Contact
Questions about this policy or Field Hygiene's data handling can be sent to support@isogunlabs.com.