Field Hygiene for Jira is built to have the smallest possible security footprint. This page explains how it authenticates, what it accesses, and how it handles data — see also the Privacy Policy for what data is read and why.
Authentication & authorization
Field Hygiene authenticates entirely through Atlassian Forge using OAuth 2.0 — there is
no separate login, password, or API key. The app requests two scopes,
read:jira-work and manage:jira-configuration, and every
interactive request runs as the requesting admin (Forge asUser). The one
named exception: a daily scheduled job that takes the Trends snapshot runs with no user
context at all — Atlassian's own platform gives scheduled triggers no user session to act
as — so that one job uses Forge's app-level identity (asApp) instead, purely
to read the same aggregate field counts already described in the Privacy Policy. Every
other request in the app uses the requesting admin's own identity, and can never surface
anything that admin couldn't already see in Jira.
Data flow
When an admin opens Field Hygiene, a Forge resolver queries Jira's field and project metadata as that admin, groups and analyzes it in memory, and returns the result directly to the page. Nothing from that scan is written to storage. Separately, once a day, a scheduled job performs the same kind of scan and writes only four aggregate counts to Forge's Key-Value Store for the Trends chart — see the Privacy Policy for exactly what that snapshot contains.
Hosting & subprocessors
Field Hygiene runs entirely on Atlassian Forge — there are no partner-operated servers, databases, or third-party subprocessors. It makes no network calls to any non-Atlassian domain, and uses no external analytics or logging services.
Data storage & encryption
The only storage Field Hygiene uses is Forge's Key-Value Store, holding one small record per day (four integers) for the Trends chart, retained for 90 days and then deleted automatically. That storage is Atlassian-managed, inheriting Forge's platform-level encryption at rest and in transit — Field Hygiene has no separate infrastructure of its own to encrypt. Everything else the app shows is computed fresh in memory on each page load and never persisted.
Logging
Field Hygiene writes only operational logs through Forge's platform logging — a status code on a failed request, or a line confirming the daily snapshot ran. Logs never contain a field name, field ID, or any other customer content, and never contain credentials.
Vulnerability & dependency management
Field Hygiene's only runtime dependencies are Atlassian's own Forge SDK packages
(@forge/api, @forge/bridge, @forge/kvs,
@forge/react, @forge/resolver) plus React itself as their
required peer dependency — no third-party packages are added on top. Periodic
npm audit checks are run before releases; any findings are traced to their
source before being dismissed or acted on, not assumed clean.
Access control
Field Hygiene is built and operated by a small independent studio. Source and deployment access is limited to the developer's Atlassian developer account, protected with two-factor authentication.
Reporting a security issue
If you believe you've found a security vulnerability in Field Hygiene, please report it to support@isogunlabs.com. We aim to acknowledge reports promptly and will work with you on responsible disclosure.