Security and trust: Outage & Maintenance Banners

A short page for your security review. Details are in the privacy policy.

Where it runs

  • Built on Atlassian Forge and designed for the Runs on Atlassian program: all code runs on Atlassian's infrastructure and all data is stored in your site's Forge storage, in the same data region as your Jira site.
  • No external calls. The app has no servers of its own and sends no data anywhere: no analytics, no email, no webhooks. There's nothing of ours that can go down or leak your data.
  • Uninstalling removes the app; Atlassian deletes its stored data 28 days later.

Who can do what

  • Jira admins manage all notices. Only they can choose who can post, and reply to customers in bulk when resolving.
  • Confluence admins manage notices that show only in Confluence; anything that reaches the service portal is posted from Jira.
  • People in groups an admin allows can post notices, run incidents and post updates from Apps → Announcement banners in Jira.
  • Every action is checked on the server (not just hidden in the page), and each notice keeps a log of its last 10 changes with who made them.
  • Customers and anonymous visitors only see notices meant for the page they're on, and can dismiss them or click "I'm affected too".

What it stores

Notices, their counts (numbers only), incident updates, which groups may post, a change log, hourly request counts and the times of the last 48 hours of requests. No request content, no customer names or emails. See the privacy policy for the full list and retention.

Permissions it asks for

Each permission and why is listed in the privacy policy. The only write permissions are for the app's own flag that shows agents the outage panel, and for the optional admin-only "reply to the requests raised during the outage" step.

Support

support@stacix.com, replies within 1 business day (Monday to Friday, India time, UTC+5:30).