Last updated: 17 November 2026
This policy explains what Google Chat Notifications for Jira ("the app") does with data. The app is provided by Baskin, the trading name of Taha Baskın, an individual developer based in Turkey ("we"). Contact: support@baskinapps.com.
The app runs entirely on Atlassian Forge, Atlassian's hosting platform. It has no servers of its own. We don't receive, store or have access to your Jira data or your Google Chat messages. The app sends selected issue information from your Jira site to the Google Chat webhooks that your Jira administrator connects, and to the personal webhooks that individual users connect for themselves.
| Data | Where | Why |
|---|---|---|
| Google Chat webhook URLs | Forge secret storage (encrypted), on Atlassian's infrastructure | To post messages to your spaces |
| Space names, filters and digests you enter | Forge storage, on Atlassian's infrastructure | To decide which events go to which space |
| Personal notifications: the person's account ID, display name and choices, and their webhook URL (in secret storage) | Forge storage, on Atlassian's infrastructure | To send each person their own notifications |
| Combined updates waiting to be sent: issue key, summary, priority, assignee, changed fields and who changed them | Forge storage, on Atlassian's infrastructure | Kept for about one minute, then sent and deleted |
| Messages waiting to be retried after Google Chat was unavailable: the message card and the space it goes to (not the webhook URL) | Forge queue, on Atlassian's infrastructure | Kept for up to about 20 minutes, until delivered or dropped |
| Delivery log: the last 50 entries with time, space name, issue key, event type and result | Forge storage, on Atlassian's infrastructure | To show admins what was sent and why something wasn't |
Forge storage belongs to your Jira installation. Atlassian hosts it under its own privacy policy and data residency settings.
When a Jira event matches a space's filters, or a person's personal notification choices, the app sends a message to that Google Chat webhook (chat.googleapis.com). The message may contain:
Once delivered, messages are stored by Google under your organisation's Google Workspace agreement and retention settings. We have no access to them.
The app doesn't send data anywhere else. It has no analytics, tracking or advertising, and it sets no cookies.
The app reads issue events from Jira, user display names and account types (to show who made a change and to recognise Automation), an issue's security level and a comment's visibility (to keep restricted content out of Chat), lists of projects, issue types, statuses, fields and priorities (for the filter settings), and for personal notifications an issue's assignee, reporter and watchers and whether the person can see the issue. On the project settings page it checks whether the signed-in user is an administrator of that project or of Jira. JQL filters are checked by Jira itself. It uses the Jira permission scopes read:jira-work, read:jira-user and storage:app.
If Google Chat rejects a message, the app writes an error log containing an internal space ID, the HTTP status code and the error text returned by Google. Atlassian keeps these logs for a limited time and makes them available to us for troubleshooting. They don't contain issue content or webhook URLs.
The personal data the app handles is the display names of Jira users, as part of the messages described above, and for people who turn on personal notifications their Atlassian account ID and display name. Your organisation decides which spaces receive messages; each person decides where their personal notifications go. We don't process personal data on our own systems.
Removing a space on the settings page deletes its webhook URL and filters right away. Turning off personal notifications in Personal settings deletes that person's webhook URL and choices right away. When the app is uninstalled, Atlassian deletes the app's stored data under its Forge data retention policy.
Webhook URLs are kept in Forge's encrypted secret storage and are never returned to the browser. The app only accepts webhook URLs on chat.googleapis.com and can only make outgoing requests to that address.
We will update this page if the app starts handling data differently and change the date at the top.