Doc Drift for Confluence

Service Level Agreement

Version 1.0 · Effective November 1, 2026

This Service Level Agreement (SLA) describes the support and service levels that ARCH BADGER 500, LLC ("we", "us") provides for Doc Drift for Confluence (the "App"), a Confluence Cloud app sold through the Atlassian Marketplace.

1. Scope

This SLA covers customers with an active paid, free, or evaluation (trial) license for the App on Confluence Cloud.

It does not cover:

  • Confluence Cloud, Forge, Rovo, Atlassian's MCP service, or any other Atlassian product or service. Atlassian supports its own products.
  • GitHub, and the delivery of GitHub's webhooks. GitHub supports its own service.
  • Outside AI tools you connect to the App's tools through Atlassian's MCP service.
  • Custom development, training, or consulting.

2. How to get support

Channel Details
Email support@archbadger500.com
Through Atlassian You can also raise a request with Atlassian Support. Atlassian forwards app issues to us, and we respond on the Atlassian ticket.

Support is provided in English. To help us respond quickly, please include:

  • Your Confluence site URL (for example, yourcompany.atlassian.net)
  • The App version, shown in Confluence under Apps → Manage your apps
  • The page ID or link, and for flag problems, the repository and pull request number
  • For webhook problems, the delivery result GitHub shows under the webhook's Recent Deliveries (status code only; don't send the secret)
  • What you expected, what happened instead, and the steps to reproduce it
  • Screenshots or error messages, and roughly when the problem started
  • The severity you believe applies (see section 4)

Please do not send passwords, API tokens, or other secrets. We will never ask for them.

3. Support hours

Monday to Friday, 9:00 AM to 5:00 PM US Central Time (America/Chicago, CST/CDT), excluding US federal holidays ("business hours").

Requests received outside business hours are logged on receipt, and the response clock starts at the beginning of the next business-hours period, except for Critical requests as described in section 4.

4. Severity levels and response targets

The response target is the time from when we receive your request to our first response from a person (not an automated acknowledgment). We confirm or adjust the severity in that first response.

Severity Definition First response target
Critical The App is unavailable or unusable for all users on your site, the App is changing pages in any way other than its own two content properties, or there is a suspected security issue in the App. Within 24 hours, Monday to Friday
High A major feature, such as the page byline, the settings page, the GitHub webhook, or the MCP tools, does not work for many users, or flags are materially wrong. No reasonable workaround exists. Within 2 business days
Medium A feature works only partly, or a workaround exists. Within 3 business days
Low A cosmetic problem, a question about a rule or a flag, a documentation or how-to question, or a feature request. Within 5 business days

For Critical requests, the 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.

A request that Atlassian identifies to us as critical is answered within 24 hours.

These are response targets, not resolution times. We work on Critical and High issues continuously during business hours until they are resolved or a workaround is in place, and we keep you updated at least once each business day while a Critical issue is open. Resolution time depends on the problem, and some fixes depend on Atlassian (see section 5).

If flags are getting in the way, you don't have to wait for us. Anyone viewing the page can click "Not relevant", or an admin can add ignore patterns or remove the space's repository mapping in the App's settings. Then tell us what happened.

5. Availability

The App is built on Atlassian Forge and is designed to meet the Runs on Atlassian requirements. It runs entirely on Atlassian's cloud infrastructure, has no servers operated by us, and keeps its settings and index in Forge storage and Forge SQL within your Atlassian data residency region. It saves two small content properties on each page it flags: the status, score, reason codes, pull request number, and the repository, with its owner replaced by a short code (the repository name itself is not changed), plus the byline text. It does not store page text, comments, attachments, or account IDs, and it stores names only as described in the Privacy Policy.

As a result:

  • The App's availability depends on Atlassian's platform. We do not offer a separate uptime percentage. When Confluence Cloud or Forge is unavailable or degraded, the App is affected too.
  • Atlassian outages are outside our control. Atlassian publishes platform status at status.atlassian.com and Forge status at developer.status.atlassian.com. During an Atlassian incident we will tell affected customers who contact us what we know and restore the App's normal operation once the platform recovers.
  • It depends on GitHub's webhook. The App flags pages only when GitHub delivers a signed push notice. If GitHub is down, the webhook is misconfigured, or the secret doesn't match, the App can't flag pages for that change. GitHub shows each delivery and lets you resend it.
  • The index fills in as pages change. There is no nightly or scheduled sync. The App indexes a page when it is created or edited after the App is installed. Pages that haven't been edited since install are not checked until their next edit. Changes the App misses during an outage show up the next time the page is edited.
  • Limits per push. The App flags at most 25 pages for one push, and acts only on your repository's default branch.
  • Backups and recovery of Forge storage, Forge SQL, and content properties are managed by Atlassian. We do not operate a separate copy of your data.

6. Updates, maintenance, and changes

  • Forge app updates are deployed by Atlassian without planned downtime, so we do not schedule maintenance windows.
  • Updates that need new permissions must be approved by a Confluence site administrator before they take effect, as Atlassian requires.
  • Release notes are published in the version history on the App's Atlassian Marketplace listing. Each saved summary records the matcher version that produced it.
  • We give at least 30 days' notice before removing a feature, making a change that requires customer action, or changing the rules in a way that can make the App flag many more pages than before, through the Marketplace listing and, where practical, a notice inside the App. Urgent security fixes may be released without notice.

7. Escalation

If you have not received a response within the target in section 4, or you are not satisfied with progress:

  1. Reply to your existing support thread with ESCALATION in the subject line. Escalations are reviewed by the owner of ARCH BADGER 500, LLC.
  2. You can also raise the issue with Atlassian Support, which can escalate it to us directly.

8. Security and data incidents

  • Report a suspected vulnerability to support@archbadger500.com with SECURITY in the subject line. It is handled as Critical.
  • We 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. The notice will describe what happened, the data involved, and the steps we are taking.

9. Service credits and refunds

This SLA does not provide service credits, refunds, or any other financial remedy for missed targets. Licensing, billing, and refunds for the App are handled by Atlassian under the Atlassian Marketplace Terms of Use.

10. Changes to this SLA

We may update this SLA. The current version is always published at this page, with its version number and effective date. If a change reduces our commitments, we will give at least 30 days' notice through the App's Marketplace listing before it takes effect.

11. Contact

ARCH BADGER 500, LLC, support@archbadger500.com