Privacy policy
Last updated October 6, 2026
This policy explains what data Field Defaults (the "app"), provided by Steadyfield ("we"), handles when installed on an Atlassian Jira Cloud site.
Summary
Field Defaults runs entirely on Atlassian Forge. It does not send any data outside Atlassian's infrastructure, and we cannot see your Jira data.
What the app reads
- On the settings page: your projects (id, key, name, type and the project lead's account id), each project's issue types, and the fields on each issue type's Create screen with their options and the default values Jira fills in, so you can build rules and the app can check them. Each action also checks that the person using the page is a Jira administrator.
- In the Create dialog: the values of the fields your rules cover, and of fields the app filled in or locked earlier in the same browser tab, to tell empty fields and people's own entries apart, plus the account id and time zone of the person creating the issue, for "person creating the issue" defaults and relative dates. These are used in the person's browser.
- When a project changes: the project's name and lead, to keep "project lead" defaults current.
What the app stores
- Your rules (project and issue type ids and names, field ids and names, the default values, and the names of the options you picked so the settings page can show them), in Forge app storage and in the UI modifications Jira keeps for the app.
- With each rule, the default values Jira itself fills in for the rule's fields on each issue type of the project (such as the default priority, or a field's default option or text), so the Create dialog can tell them apart from what people pick.
- In the person's browser, only while the tab is open: a note of the values the app filled in and the fields it locked in the Create dialog, in the tab's session storage. It holds field ids and values (account ids for people fields) and never leaves the person's device. The browser deletes it when the tab is closed.
- For up to one minute, in memory only: whether the person using the settings page is a Jira administrator.
If a rule fills in a user field with a specific person or the project lead, that person's Atlassian account id is stored as part of the rule. The app stores no names or email addresses of people, and never reads or stores the content of the issues people create.
When the app hits an error, Atlassian records it in the app's logs. Those entries can contain ids (project, issue type, rule) and Jira's error text, never names, email addresses or issue content. We can only read logs from your site if a Jira admin allows log access in the app's settings.
Where data is processed
All processing and storage happens within Atlassian Forge and your Jira site. The app makes no external network requests and has no servers of its own.
Data residency
Field Defaults stores data only in Atlassian products and services that support data residency, so it follows your site's data residency location, including when you move it. In scope:
- Your rules, in Forge hosted storage.
- The copies of the rules in your Jira site: the app's UI modifications.
Nothing is stored outside Atlassian, so no data is out of scope. The Create dialog's note in the person's browser stays on their device.
Retention and deletion
Deleting a rule deletes it from app storage and from Jira. When the app is uninstalled, Atlassian marks its storage for deletion and deletes it permanently within 28 days, and the app's UI modifications stop applying. Values already filled into issues stay on those issues like any other value.
Third parties
We use no third-party processors for app data. Atlassian processes data as described in its own privacy policy.