> For the complete documentation index, see [llms.txt](https://docs.forgappify.com/field-rules/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forgappify.com/field-rules/jira-administrator/security.md).

# Security

How Field Rules keeps data secure - Forge sandboxing, OAuth 2.0 scoped access, data residency, and the Runs on Atlassian badge, with no external data egress.

Our app is built on Atlassian’s Forge platform and integrates securely with Jira via OAuth 2.0. All data remains within Atlassian’s cloud environment, ensuring compliance with enterprise-grade data residency and security standards. The app holds the **Runs on Atlassian** badge, confirming no customer data leaves the Atlassian ecosystem.

### Secure Integration

* **OAuth 2.0 authorization** provides scoped, delegated access to Jira data, limiting permissions to only what the app needs.
* The app runs entirely within Atlassian’s Forge sandbox, eliminating external servers or infrastructure.

### Data Handling & Residency

* Field rules and app data are stored exclusively inside Jira or Atlassian-managed infrastructure.
* Data residency aligns with the region of the Jira Cloud instance, meeting enterprise geographic requirements.
* No data is transmitted outside the Atlassian environment.

### Compliance & Security Assurance

* The app operates under the security controls of Atlassian’s cloud platform, which adheres to industry standards for cloud security and compliance.
* Our development follows secure coding practices and minimal permission principles.

### Runs on Atlassian Badge

* Confirms the app runs fully within Atlassian’s infrastructure without external data flows.
* Provides assurance of enterprise-level security, data residency, and compliance standards.
