Privacy policy: Outage & Maintenance Banners
Last updated: 31 October 2026
Outage & Maintenance Banners is made by Stacix ("we"). This policy explains what the app stores and who can see it.
Summary
- The app runs entirely on Atlassian's Forge platform. It does not send any data to us or to any other server.
- We cannot see your data. It stays in your Atlassian site's Forge storage.
- The app does not store personal data about the people who view your notices. For notices themselves, it records which team member made each change (their Atlassian account ID), shown only on the admin page.
What the app stores
In your site's Forge storage (hosted by Atlassian, in the same data region as your Jira site):
- The notices your admins create: type, title, message, start and end times, link, targeting (portal IDs, portal pages, request type IDs, Confluence space keys), what was affected, and the incident timeline, and whether each notice is paused.
- Counts per notice: a number of views (and how many of those were on the "Raise a request" form) and a number of link clicks. No names, account IDs, IP addresses or other identifiers are stored with them.
- Incident updates your team posts on an outage notice (stage, time, short text, and the promised time of the next update).
- "I'm affected too" counts: one number per outage notice. To count each signed-in person once, the app keeps a one-way fingerprint made from their account and the notice (it can't be turned back into who they are), deleted with the notice. Nothing else about the person is stored.
- New service requests: one number per hour, plus the times (only the times) of requests from the last 48 hours, for the "tickets saved" estimate. Nothing about the requests themselves (no summaries, people or content) is stored. Hourly counts older than 45 days and times older than 48 hours are deleted automatically.
- Who can post notices: the names and IDs of the Jira groups an admin allowed.
- Who changed each notice: for the last 10 changes to a notice, what was done (for example "Resolved"), when, and the Atlassian account ID of the person who did it, so admins can see who posted or resolved it. Deleted with the notice. Once a week the app reports these account IDs to Atlassian, as Atlassian's privacy rules require. If someone's Atlassian account is closed, their ID is removed from every log.
In each viewer's own browser (local storage, never sent to us):
- Which notices they dismissed, so dismissed notices stay hidden.
- Whether they already clicked "I'm affected too" on an outage, so they're counted once.
- The last day a notice was counted as viewed, so a view is counted once a day.
What the app reads from your site
The app asks Atlassian for these permissions, and uses them only as described:
| Permission | Used for |
|---|---|
read:jira-work |
Checking that the person using the admin page is a Jira admin |
read:confluence-user |
Checking that the person using the Confluence admin page is a Confluence admin |
read:servicedesk-request |
Listing your service portals in the admin page so you can target them |
read:space:confluence |
Listing your Confluence spaces in the admin page so you can target them |
storage:app |
Saving notices and counts in Forge storage |
read:jira-user |
Listing Jira groups for "Who can post notices", and checking whether the current user is in one |
write:app-data:jira |
Setting a flag that shows agents the outage panel only while an outage notice is live |
write:servicedesk-request |
Only when your admin chooses "Also reply to the requests raised during the outage" while resolving: posting that reply as the admin, so JSM notifies those customers as usual |
The app also listens for new Jira issues so it can add 1 to the hourly count for service requests. It reads only the project type and creation time. When resolving an outage, it searches (as the admin) for service requests created since the outage started, to offer the reply above.
Data residency
The app keeps all its data in Forge hosted storage, which supports data residency. If your organization pins Jira or Confluence to a location (for example the EU, the US or India), the app's data is stored in the same location and moves with it. The app shows as Pinned in your Data residency settings.
- In scope (pinned with your site): everything listed under "What the app stores" above, meaning notices, incident updates, counts, the "I'm affected too" fingerprints, request counts and times, allowed groups and the change log.
- Out of scope: nothing the app controls. Data kept in each viewer's own browser (dismissed notices, the "counted today" marker) never leaves that browser.
Sharing
We don't sell, share or transfer your data. We have no access to it. Atlassian hosts it as part of the Forge platform under Atlassian's privacy policy.
Retention and deletion
- Admins can delete any notice at any time; its counts are deleted with it.
- If you uninstall the app, Atlassian keeps Forge-hosted app data for 28 days in case you reinstall, then deletes it (Atlassian Forge storage).
- Viewers can clear the app's browser data by clearing their browser's site data.
Children
The app is a business tool and isn't directed at children.
Changes
We'll update this page if the app starts storing anything new, and change the date above.