Spec Watch

Security practices

Version 1.0 · Effective November 11, 2026.

This page describes how ARCH BADGER 500, LLC ("we", "us") handles security for Spec Watch (the "App"), a Jira and Confluence 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), 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), no remotes, and no web trigger. It exposes no remote REST APIs.

The App does not store page bodies, issue descriptions, comments, or attachments. It stores settings, page-link metadata (including page titles and issue keys), flag and dismissal records, and pointers to digest pages, as listed in section 2 of the Privacy Policy. We cannot read the data the App stores in your site.

The only pages the App writes are digest pages it created in your Confluence site. Those pages stay on Atlassian. The App never rewrites a spec or runbook.

Platform logs. The App writes operational logs to Atlassian's Forge platform. They may include issue keys, page ids, field ids, skip reasons, counts, and error names or messages, but not page bodies, issue descriptions, comment text, or secrets. An error message passed on from Jira, Confluence, or Forge could still repeat an identifier. We do not treat these identifiers as anonymous. We view these logs only to run and fix the App. The logs stay on Atlassian.

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.

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. The App stores no passwords, API tokens, webhook secrets, or other shared secrets.

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 issue updated events and the changelog so only watched fields flag a linked page.
read:page:confluence Read page storage to find Jira links, plus owner and last edit time. Page bodies are not stored.
read:user:confluence Look up a user's display name so digest titles and the "Cleared by" byline can show a name instead of an account ID.
read:space:confluence List spaces while building the page index.
read:confluence-content.summary Receive page created and updated events.
write:page:confluence Create and update Spec Watch's own digest pages only. The App never rewrites a spec or runbook.
storage:app Save settings, the page index, flags, and dismissals 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.

The App asks for no permission to call servers outside Atlassian.

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.
  • 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.

Flagging is rules-based: it compares a Jira issue's changelog to the last-edited time of each linked Confluence page. The App does not call large-language-model APIs of its own.

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