Field Limit Guard

Field Limit Guard - Privacy Policy

Last updated: 2026-06-22

Field Limit Guard (the “app”) is provided by Aria Code. This policy explains what data the app accesses, why, how it is stored and shared, how long it is kept, and how to contact us. Our security practices are described separately in our Security Policy.

What we collect and why

Field Limit Guard is a read-only administrative tool for Jira Cloud. It reads:

  • Custom field configuration, field names, IDs, types, contexts, options, and where each field is used (screens, project associations), to produce its cleanup report.
  • Saved filters (their JQL) to detect where a field is referenced.

It does not read or collect the content of your work items (issues) - no descriptions, comments, attachments, or field values entered by users, and it collects no personal data such as names, emails, or profiles.

How it is stored and used

The app runs on Atlassian Forge and uses Forge-hosted storage only for a small list of field IDs for which an administrator has dismissed a warning. This data is used solely to operate the app for you. We do not use it for advertising or to train any model.

Sharing and subprocessors

We do not sell or share your data. The app makes no calls to third-party services and transmits no data outside Atlassian. The only subprocessor is Atlassian (Atlassian Forge), which hosts and processes the data within its cloud platform on our behalf. There are no other third parties or subprocessors.

Data retention and deletion

Dismissed-warning data persists until an administrator restores the warning or uninstalls the app. Uninstalling the app deletes its Forge storage data. You may also request deletion of any data by emailing us.

Your rights

To request access to or deletion of data associated with your installation, contact hello@ariacode.dev.

Permissions

All scopes are used read-only except the app’s own settings storage:

  • read:jira-work, list custom fields and saved filters.
  • manage:jira-configuration, read field contexts and options.
  • manage:jira-project, read which screens a field appears on.
  • storage:app, store dismissed-warning preferences.

The app performs no write operations to your Jira configuration or issues.

Data residency

Stored data resides in Atlassian Forge storage, subject to Atlassian’s data residency model.

Contact & changes

Questions or requests: hello@ariacode.dev. We may update this policy and will revise the date above when we do.