Data Encryption
Secure Custom Field values are encrypted with AES-256 before they are stored in Jira.
SCFJ does not maintain a separate external datastore for Secure Custom Field values. Decrypted values are only made available to authorized users and integrations according to the field permissions and API access controls configured in SCFJ.
Data Storage, Retention, and Deletion
Secure Custom Field values are stored in Jira in encrypted form. Secure Field History is stored using Atlassian Forge hosted storage.
SCFJ relies on Atlassian's platform-level data lifecycle for data stored in Jira and Forge:
-
Forge-hosted data: Atlassian Forge retains hosted storage for 28 days after an app is uninstalled.
-
Deleted Jira custom fields: When a Jira custom field is deleted, Jira marks it for deletion and keeps it recoverable for 60 days before permanent deletion.
-
Data residency: Forge-hosted storage follows the data residency location of the host Atlassian app. When an administrator moves supported Jira data to another supported location, Forge-hosted app data is migrated with it.
These retention and residency periods are managed by Atlassian and may change as Atlassian updates its platform policies. Refer to Atlassian's current Forge and Jira documentation for the latest platform-level behavior.
Certifications
Ricksoft, Inc. holds ISO 27001 certification, the international standard for information security management systems (ISMS). This certification covers the organizational security practices governing how Secure Custom Fields for Jira is developed, operated, and supported.
Independent Security Testing
Secure Custom Fields for Jira is actively enrolled in the Atlassian Marketplace Bug Bounty program. This means independent security researchers continuously test the app for vulnerabilities, on an ongoing basis rather than a one-time audit.
Access Control
Field-level permissions are configured by Jira administrators, controlling exactly who can view or edit each secure field's value. Protected fields are displayed as read-only or hidden to any user without explicit permission.
AI / Rovo Capability
Secure Custom Fields for Jira is built so AI-assisted work through Rovo respects the same permission model as the rest of the app, access is never widened for convenience:
-
No more dead ends on access denial. Today, if Rovo denies a user access to a secure field, they're stuck, they have to track down an admin manually, outside both Jira and Rovo. With this capability, Rovo instead offers to request access on their behalf, right from the chat, and routes it to the field's admins for approval. Rovo never reveals who currently holds access, even if asked directly (Coming soon!)
-
Full AI analysis for the people who are already allowed to see it. Users with legitimate view permission get the same Rovo-powered summarization, trend-spotting, and cross-issue analysis that every other Jira field already gets — nothing is held back from them. Anyone without permission is simply excluded from the results, silently, with no data leaked (Coming soon!)
The pitch to a security-conscious buyer: locking down your data doesn't mean losing AI , permitted users get full value, unauthorized users get nothing, and the boundary is never crossed either way.
Questions
For security or compliance questions beyond what's covered here, contact us via the support portal or reach out directly during your demo.