Spec Watch

Privacy Policy

Version 1.0 · Effective November 10, 2026.

This Privacy Policy describes how ARCH BADGER 500, LLC ("we", "us") handles information in Spec Watch (the "App"), a Jira and Confluence Cloud app sold through the Atlassian Marketplace.

The App runs on Atlassian Forge. It does not run on servers we operate, it does not call servers outside Atlassian, and it has no web trigger.

1. Who this covers

This policy covers people who use a Jira or Confluence site where Spec Watch is installed.

Atlassian also processes data under its own terms and privacy policy. This policy is about the App, not about Jira, Confluence, or Forge themselves.

2. What the App stores

All of the App's stored data is in Forge hosted storage (the Key-Value Store) on Atlassian's cloud, in your site's data residency location.

The App stores:

  • Settings: whether Spec Watch is on, which Jira fields and statuses are watched, and whether the daily digest is on.
  • A page index: Confluence page id, title, space id and key, owner account id, last edited time, version, and the Jira issue keys linked from the page.
  • Flag and dismissal records: page id, title, space, owner account id, issue key, changelog id, flagged time, dismissed-by account id, and dismissed time.
  • Pointers to digest pages the App created (page id, space, title, version).
  • Working records: a marker for each page and day it was flagged (page id, day, changelog id, issue key), a marker for each digest page the App created (page id and owner account id), the list of currently flagged page ids, and the progress of the first scan of your spaces (space ids, space keys, and page cursors).

The App reads page storage only to find Jira issue links. It does not store page bodies, issue descriptions, comments, or attachments. It never rewrites a spec or runbook. The only pages it writes are digest pages it created.

Display names are resolved at read time from the Confluence user API so digest titles and the "Cleared by" byline can show a name instead of an account id. Page history is a fallback. A display name may appear in a digest page title. If no display name can be resolved, the title uses "Unknown user" instead of an account ID.

Atlassian account IDs (the page owner's, and the account that cleared a flag) are personal data. The App stores them to decide who can clear a flag and who gets a digest. They also appear as an @mention on digest pages, and a display name may appear in a digest page title. If no display name can be resolved, the title uses "Unknown user" instead of an account ID. They are pseudonymous identifiers, not anonymous data. Page titles are text your users wrote and could contain names or other personal information; the App stores them as written. The App does not store display names as their own field in Forge storage. When a digest page title includes a display name, or "Unknown user", that title is also stored in the digest-page pointer.

The App requests these scopes:

  • read:jira-work: issue updated events and the changelog.
  • read:page:confluence: page storage, 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: 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: Forge Key-Value Store for settings, the page index, flags, and dismissals.
  • report:personal-data: report the Atlassian account IDs the App stores to Atlassian's Personal Data Reporting API at least every 7 days.

The App has no remotes, no egress, and no web trigger.

The App reads Confluence pages as itself, not as the person viewing them, to build its index. What each person is shown is limited as described in section 4.

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. Atlassian keeps these logs under its own retention policy.

3. Why it is stored

The App uses this data to flag a Confluence page when a linked Jira issue changes after the page was last edited, to show those flags in Jira and Confluence, to honor No doc impact, and to build an optional daily digest for each page owner.

4. Who can see it

Spec Watch shows flags in four places. (1) The byline on a Confluence page shows that page's flag, the Jira issue key that caused it, and, after a flag is cleared, who cleared it and when. Anyone who can view the page sees this. (2) The Jira issue panel lists the flagged Confluence pages that link to that issue, but only pages the person viewing the issue can open. (3) A digest page is an ordinary Confluence page in one space and lists that owner's flagged pages in that space. Anyone who can view the digest page can read the titles it lists. (4) Site admins can change settings, run the digest, and export a CSV of currently flagged pages across your spaces (page id, title, space key, issue key, and flagged time).

We do not receive a copy of your site's data on our own systems. Atlassian operates the Forge platform that hosts the App.

5. Sharing

We do not sell this data. We do not share it with third parties or sub-processors. It stays on Atlassian.

6. Retention and uninstall

The data is kept in Forge storage while the App is installed. The App does not write Jira or Confluence entity properties.

When the App is uninstalled, Atlassian's Forge platform marks the App's stored data for your site as deleted, and the App can no longer read it. Atlassian keeps that deleted storage for 28 days (a restore must be requested within 21 days) and then permanently destroys it. A reinstall starts as a new installation.

Digest pages stay after uninstall. They are ordinary Confluence pages. Their title is Spec Watch digest ( plus the owner's display name, or "Unknown user" if no name can be resolved, they include an @mention of the owner, and they list flagged page titles. Search Confluence for "Spec Watch digest" to find them. If a digest page is deleted while the App is still installed, the App creates it again on the next digest run. After uninstall we cannot see your site, and we cannot delete those pages for you. If a watched page is deleted or trashed, the App drops its flag and related records when it next tries to read that page.

7. Your choices and requests

A site admin can turn Spec Watch off, turn the digest off, and uninstall the App.

Spec Watch reports the Atlassian account IDs it stores to Atlassian's Personal Data Reporting API at least every 7 days. When Atlassian says an account is closed, the App erases that account ID from its storage. When Atlassian says an account's personal data has been updated, the App refreshes it.

To ask about personal data the App stores, email support@archbadger500.com. We will work with you and, where needed, Atlassian. Because we do not host a separate copy of the data, some requests are fulfilled by uninstalling the App or by actions you take in Jira and Confluence. If you email us, we use what you send only to answer you and to fix the App. Please do not send page content, passwords, or tokens.

8. Children

The App is for business use on Atlassian Cloud. It is not directed at children.

9. Changes

We may update this policy. The current version will be published on this page with a new version number and date. If a change is material, we will also note it on the App's Marketplace listing.

10. Contact

ARCH BADGER 500, LLC · support@archbadger500.com · archbadger500.com

Related: Support · Service Level Agreement · EULA · Security practices