Last updated June 2, 2026
AdminLedger for Jira Data Processing Addendum
This page identifies the data processing terms and processing details for AdminLedger for Jira, an Atlassian Marketplace app provided by Elevara.
DPA
For customers that subscribe to AdminLedger for Jira through the Atlassian Marketplace and where Elevara processes Customer Personal Data as a processor or service provider, Elevara uses the Bonterms Data Protection Addendum (Version 1.0) as an attachment to the applicable Marketplace agreement.
The Bonterms Data Protection Addendum is available at Bonterms Data Protection Addendum (Version 1.0).
Processing Details
| Subject matter | Providing AdminLedger for Jira, including Jira admin review scanning, generated findings, CSV exports, scan history, settings, and optional Confluence report publishing. |
|---|---|
| Duration | For the customer's subscription term and any post-termination period required by applicable law or Atlassian Forge data deletion behavior. |
| Purpose | To provide the app, support customer-requested admin review workflows, maintain app settings and scan history, and respond to support or security requests. |
| Processing activities | Access, retrieval, analysis, storage, export, display, and deletion of app data as needed to provide AdminLedger for Jira. |
Data Categories
AdminLedger may process the following customer data categories:
- Jira project metadata.
- Jira custom field metadata.
- Jira workflow metadata.
- Jira group names and admin-like group metadata.
- Confluence page summary metadata when report publishing is configured.
- App settings entered by administrators.
- Generated scan reports, findings, evidence, recommendations, CSV exports, and recent scan history.
- Support contact information and support request content submitted through Elevara support channels.
Subprocessors
AdminLedger v1 is hosted on Atlassian Forge and stores app data in Forge hosted storage. Elevara does not use an external app backend for AdminLedger v1.
- Atlassian: Marketplace, Forge hosting, Forge functions, Forge hosted storage, Jira Cloud, and Confluence Cloud services used to provide the app.
- FormSubmit: support form routing for customer-submitted support requests.
- GitHub Pages: public documentation, privacy, security, DPA, and support resource hosting.
Security Measures
- Forge-hosted application runtime and storage.
- No external Elevara backend in v1.
- No external AI service calls in v1.
- No Atlassian Personal Access Tokens, passwords, or shared secrets required from customers.
- Status-level operational logging that avoids request paths and scan data.
- Non-destructive product behavior: AdminLedger does not delete fields, change permissions, remove users, or rewrite workflows.