Security overview
Last updated: October 3, 2026
The App is built to keep your Jira data inside Atlassian and send each update only where you decide.
1. Architecture
- Jira CloudYour site emits an event when an issue changes.
- App on Atlassian ForgeRuns inside Atlassian's cloud: applies your filters and builds the message.
- chat.googleapis.comThe only outbound destination, over HTTPS.
- Your Google Chat spaceOnly the spaces your admins or users configure.
- No SagoSoft servers. We don't operate servers, databases or queues for the App. Code, storage and logs run on Atlassian's platform and its security program.
- Data residency. Forge storage follows your Jira site's data residency location when one is pinned; otherwise Atlassian chooses where it is hosted. See the privacy policy.
- No analytics, trackers or third-party scripts in the App or on this website.
2. Data protection
- Encrypted secrets. Google Chat webhook links are stored with Forge's secret storage (
kvs.setSecret), encrypted and separate from the settings. The settings pages never receive the full link again, only a masked version. - Encryption at rest and in transit. Forge storage is encrypted at rest by Atlassian. All traffic, to Jira and to Google, uses HTTPS.
- Minimal data. Issue content is processed in memory to build a message and is not stored. Comment excerpts are capped at 600 characters.
- Logs without content. Error logs contain technical details (event type, issue key, HTTP status, short error message), not issue summaries, comments, API response bodies or webhook links.
3. Outbound connections
The App's manifest allows exactly one external destination, https://chat.googleapis.com, and Forge blocks any other. In addition, the App only accepts links with the form https://chat.googleapis.com/v1/spaces/…/messages?key=…&token=….
4. Permissions (scopes)
| Scope | Why |
|---|---|
read:jira-work | Read issues, projects, statuses and watchers, check JQL filters and build the daily summary. Read-only: the App never changes your Jira data. |
read:jira-work with user impersonation | Before each personal notification, ask Jira as that user whether they can see the issue and the comment. Each user authorizes this in Atlassian's consent screen. |
read:jira-user | Show display names instead of account IDs. |
storage:app | Keep the settings and the encrypted webhook links in Forge storage. |
report:personal-data | Report stored account IDs to Atlassian every week and delete closed accounts. |
The App has no write scopes for Jira.
5. Access control
- Admin page. Jira only shows it to administrators, and every server-side action checks again, as the current user, that they have the Jira Administer permission.
- Personal page. The user's identity comes from Forge's server-side context, never from the browser request, so each user can only read and change their own subscription.
- Personal notifications fail closed. A message is sent only if Jira explicitly confirms that the person can see the issue (and the comment). Any error means nothing is sent. Deactivated accounts get nothing.
- Restricted comments and Jira Service Management internal notes never reach shared spaces, and their text is never sent anywhere.
- Shared spaces. Everyone in a Google Chat space sees what it receives. Administrators decide which spaces and filters to use.
6. Licensing, privacy and deletion
- Without an active license, event processing and summaries don't run; deleting data still works.
- Account IDs are reported weekly to Atlassian's personal data reporting API; data of closed accounts is deleted.
- Deleting a space or turning off a personal subscription removes its settings and webhook link from the App's storage right away. Atlassian may keep deleted data in soft-deleted copies and backups for its own retention period. After uninstalling, Atlassian keeps the App's storage for up to 28 days and then deletes it permanently (see the privacy policy).
7. Development practices
- Small codebase built on Atlassian's official Forge packages and React, with their dependencies.
- Automated tests for the notification rules, filters, permissions, input validation and message building. Releases go out through a script that first runs those tests and
npm audit: a known high or critical vulnerability in a dependency blocks the release. - Updates are delivered through Atlassian's Forge deployment; changes that need new permissions require an administrator's approval.
8. Report a vulnerability
Email security@sagosoft.com with the subject “Security” and include the steps to reproduce, the impact and your contact details. Please don't access other customers' data, disrupt the service or make the issue public before we've had a reasonable time to fix it. We won't take legal action against good-faith research that follows these rules. We fix vulnerabilities within the timeframes of Atlassian's security bug fix policy for Marketplace apps.
Fix timeframes under that policy: critical within 10 days, high within 4 weeks, medium within 12 weeks and low within 25 weeks.
9. Incident response plan
A security incident is any real or suspected unauthorized access to, or use, disclosure, change or loss of, Customer Data handled by the App, or a compromise of the App itself.
- Detect. Reports to security@sagosoft.com, Atlassian security tickets for the App and the App's error logs in the Forge developer console.
- Contain. Deploy a fix, or a version that turns off the affected feature, through Forge. If a webhook link may have been exposed, we ask the affected customers to delete it in Google Chat and create a new one, which makes the old link stop working.
- Notify Atlassian with a P1 ticket in the Atlassian Ecosystem service desk promptly and no later than 24 hours, with updates at least every 6 hours until it is resolved.
- Notify customers. Affected customers hear from us through their Atlassian technical contact, aiming for 72 hours from identification, using Atlassian's incident and vulnerability notification templates, and as required by law.
- Learn. We share a post-incident review through the same ticket and fix the root cause.
We review this plan at least once a year.