Agent Ledger for Jira

Security practices

Version 1.0 · Effective November 11, 2026

This page describes how Arch Badger 500, LLC ("we", "us") handles security for Agent Ledger for Jira (the "App"), a Jira Cloud app sold through the Atlassian Marketplace. It is separate from our Privacy Policy, which explains what the App stores and how that data is removed.

1. Data handling

The App is a Forge app. It runs on Atlassian's cloud, inside your Atlassian site. We run no servers or databases of our own for the App.

The App keeps its data in Atlassian Forge storage (the Key-Value Store and, for the optional webhook secret, the secret store), in your site's data residency location. It makes no calls to servers outside Atlassian. Its Forge manifest declares no external network permissions (permissions.external) and no remotes.

The App stores metadata, not content. It does not store work-item descriptions, comment text, attachments, or source code. The full list of stored fields is in section 3 of the Privacy Policy. We cannot read the data the App stores in your site.

The one inbound exception is optional. If a Jira admin sets up the GitHub webhook, GitHub sends pull-request, review, and push events into the App. The App checks each event's signature against the secret the admin set (HMAC-SHA256, compared in constant time). Events that do not match are rejected. The webhook is a Forge static web trigger: it returns a fixed status response and never sends App data back to GitHub or anywhere else.

2. Encryption

Because the App stores data only in Forge hosted storage, encryption is provided by Atlassian's platform:

  • At rest. Atlassian's Forge documentation states that Forge hosted storage is encrypted at rest with AES-256. See Forge and SOC 2 and the Key-Value Store documentation.
  • In transit. Atlassian documents that data is encrypted in transit with TLS 1.2 or higher.
  • Secrets. If an admin sets the optional GitHub webhook secret, it is kept in Forge's secret store, not in ordinary app storage. The App never shows the secret again or writes it to logs.

We do not operate a separate store, network, or key-management system for the App, and we do not add our own encryption layer on top of Forge.

3. Permissions

When a Jira admin installs the App, Atlassian asks them to approve only these permissions. Each is the least the App needs for the job described:

Permission Why the App asks for it
read:jira-work Read work items and their change history to build the reports. Comment text is not stored.
read:jira-user Tell app accounts (such as AI coding agents) from people, using the account type.
storage:app Save the App's results, settings, and (if configured) the webhook secret in Forge storage.
report:personal-data Report stored Atlassian account IDs to Atlassian's personal data reporting API, and erase or refresh them when Atlassian says an account is closed or updated.
read:graph:issue:jira Read work items through Atlassian's Teamwork Graph so linked development data can be found.
read:graph:pull-request:external Read pull requests linked to a work item, as the person viewing the page.
read:graph:commit:external Read commits linked to a work item, as the person viewing the page.
read:graph:repository:external Read repository metadata for those linked pull requests and commits, as the person viewing the page.
read:graph:user:atlassian Read Atlassian user data linked through Teamwork Graph, as the person viewing the page.

The App asks for no permission to call servers outside Atlassian, and no permission to edit work-item fields, comments, or descriptions.

4. Reporting a vulnerability

Email support@archbadger500.com with SECURITY in the subject line. That is the security contact published on our support page, Service Level Agreement, and Privacy Policy.

Please include which App version you are reporting (a Jira admin can find it under Apps → Manage your apps), what the issue is, how to reproduce it, and how we can reach you. Do not send passwords, API tokens, or other secrets, and do not include real customer data beyond what you need to show the issue.

You can also report a problem through Atlassian Support. Atlassian forwards app issues to us.

We do not run a paid bug bounty.

5. Response targets

Support hours are Monday to Friday, 9:00 AM to 5:00 PM US Central Time (America/Chicago), excluding US federal holidays, matching our Service Level Agreement.

A suspected security issue in the App is handled as Critical. The first-response target is within 24 hours, Monday to Friday. For Critical requests, that 24-hour clock runs Monday through Friday, including US federal holidays. A Critical request received on a Saturday or Sunday is answered within 24 hours of 9:00 AM Central on the following Monday. While a Critical issue is open, we keep you updated at least once each business day.

We aim to fix confirmed vulnerabilities within the timeframes in Atlassian's Security Bug Fix Policy for Marketplace apps. For cloud apps these are currently 10 days for Critical, 4 weeks for High, 12 weeks for Medium, and 25 weeks for Low severity.

If we confirm a security incident that affects your data, we will notify Atlassian and the affected customers without undue delay, and no later than 72 hours after confirming it, as set out in the SLA.

6. Vulnerability management

The App's source repository uses continuous integration on every pull request and on every push to the default branch:

  • Unit tests must pass.
  • npm audit runs on production dependencies and fails the build at high or critical severity.
  • Dependabot opens weekly update pull requests for npm packages and GitHub Actions.
  • Gitleaks scans for committed secrets.
  • A CycloneDX software bill of materials for production dependencies is produced and stored as a build artifact for 90 days.

The App does not call large-language-model APIs of its own. Attribution is a rules-based estimate from work-item and pull-request metadata.

7. Certifications

Arch Badger 500, LLC does not hold third-party security certifications (for example SOC 2 or ISO 27001) for the App. The App relies on Atlassian's Forge platform for hosting, storage, encryption, access control, backups, and data residency. Atlassian publishes its own platform certifications and security documentation, including Forge and SOC 2.

8. Related pages

9. Changes

If we change these practices, we will post the new version on this page with a new version number and effective date.

10. Contact

Arch Badger 500, LLC (Indiana, USA). Email support@archbadger500.com