Senyi Labs
Privacy policy
Last updated: [DATE OF PUBLICATION]. This policy covers Herald – Google Chat notifications for Jira ("Herald"), made by Senyi Labs.
Who we are
Senyi Labs, [ENK NAME AND ORGANISATION NUMBER], Norway. Contact: the contact form (topic Privacy).
The short version
- Herald runs entirely on Atlassian Forge, Atlassian's platform for apps. Herald has no servers of its own and Senyi Labs does not copy your Jira data to any system we run.
- Herald sends Jira information only to the Google Chat spaces your administrators connect.
- Herald only reads Jira data. It never changes issues.
- No advertising, no tracking, no selling of data.
What Herald stores, and where
Herald stores the following in Atlassian's Forge storage for your site. It stays on Atlassian's infrastructure and is deleted when Herald is uninstalled, according to Atlassian's retention rules for Forge apps.
| Data | Why | How long |
|---|---|---|
| Connection settings: name, filters, events, message options, Google Chat space ID | To know what to send where | Until the connection is deleted |
| Google Chat webhook URLs | To post to the space. Kept in Forge's encrypted secret storage | Until the connection is deleted |
| Delivery log: time, issue key, a short description of the change, delivery result and error message | So administrators can see what was sent and why something failed | Latest 100 entries per connection |
| Connection health: last success, last error | Health badge and failure alerts | Until the connection is deleted |
| Failure alert recipients (Atlassian account IDs) | To email them when a connection fails | Until changed or Herald is uninstalled |
| Messages waiting to be sent, including issue details | Queueing and combining bulk changes | Seconds to minutes, until delivered |
| Small caches: your site's address, project and board names, whether an account is an app account, which releases were announced | To avoid repeated lookups | Until Herald is uninstalled |
What Herald sends to Google
For each notification, Herald sends to the Google Chat space you connected: the issue key and summary, issue type, what changed, the fields your administrator chose to show (for example status, assignee, priority), comment text when comment notifications are on, and people's display names. Google processes this under your organisation's agreement with Google Workspace. Private content (issues with a security level, restricted and internal comments) is skipped by default.
Emails
Failure alerts are sent by Jira itself, using Jira's notification email, to the people your administrators chose.
App logs
Like every Forge app, Herald writes technical logs to Atlassian's logging service, for example "KAN-12 status changed: sent to 'Support team'" or an error message from Google Chat. Logs can contain issue keys, connection names, event types and account IDs, never webhook URLs. Senyi Labs can read these logs to fix problems, and your site administrators can download them too. Atlassian keeps them for about 30 days.
Your rights
Your organisation controls the data in Jira and in Herald's settings. Administrators can delete connections at any time, which deletes their settings, webhook and delivery log. Uninstalling Herald removes its stored data. For any privacy question or request, including under the GDPR, use the contact form and choose the topic Privacy.
Changes
We'll update this page when Herald's data handling changes, and note the date at the top.