Last updated June 2, 2026
AdminLedger for Jira Privacy Policy
AdminLedger for Jira is provided by Elevara. This policy explains what data the app processes and how it is handled.
Data We Process
AdminLedger processes Jira and Confluence metadata needed to create admin review reports, including:
- Jira custom field metadata.
- Jira workflow metadata.
- Jira project metadata.
- Jira group names returned by admin group lookup.
- Confluence page summary metadata when a reporting space is configured.
- App settings entered by administrators.
- Generated scan reports and recent scan history.
AdminLedger does not intentionally collect payment card data, passwords, attachments, or Jira issue body content.
How Data Is Used
- Generate Jira admin review findings.
- Estimate directional administrative waste.
- Build report-ready recommendations.
- Publish optional Confluence reports when configured by the customer.
- Store recent scan history for trend review.
Hosting And Storage
AdminLedger is built on Atlassian Forge. App data is stored using Forge storage and is not sent to an external Elevara backend in v1.
External Sharing
AdminLedger v1 does not send customer data to external analytics tools, external AI services, or third-party infrastructure.
Retention
AdminLedger stores app settings, the latest scan report, and up to 12 recent scan history summaries. Atlassian controls Forge app data deletion behavior when an app is uninstalled.
Security
AdminLedger uses Atlassian Forge platform authentication and authorization. The app requires only the Forge scopes declared in its Marketplace listing and app manifest.
Contact
For privacy or support requests, use the Elevara support form.