Privacy policy

Version: 8 November 2026. Applies to "Google Chat Notifications for Jira" (the "App").

Who we are

The App is provided by mindmotion.tech ("we"). Contact: contact@mindmotiontech.com.

For the Jira and Google Chat data the App processes on your behalf, your organisation is the data controller and we act as a data processor.

What data the App processes

• Jira issue data, processed in memory and not stored: issue key and summary; status, assignee, priority and watchers; up to 3 comment previews; display names. We use it only to build a notification card.
• Configuration, stored: notification rules (names, filters and JQL), Google Chat webhook URLs (stored encrypted), default settings.
• Account link, stored: your Jira account ID, your Google Chat direct-message space ID, your Google user ID and your Google e-mail address. Stored only after you connect, and deleted when you click Disconnect.
• Preferences, stored: which notifications you want, the digest hour and your Jira time zone.
• Recent mentions, stored for at most 2 days: the issue key and who mentioned you. This is used for your daily digest.
• Technical logs: issue keys, event types and error codes. No issue contents, e-mails or webhook URLs.

We do not sell data, use it for advertising, or use it to train AI models. We never access Google data beyond sending messages to chats where you added the App. We do not request access to your Google messages, files or contacts.

Where data is stored

Stored data lives in Atlassian Forge hosted storage, inside your Atlassian cloud site's infrastructure. Notifications are delivered by Google's Chat API to your organisation's Google Workspace. Interactive Chat events (for example the "connect" command, or a click on Assign to me, Change status or Comment) pass through our stateless endpoint on Cloudflare. It stores nothing and only forwards a signed request to your own Jira installation of the App, which performs the action as you.

Subprocessors: Atlassian (hosting), Google (message delivery), Cloudflare (endpoint).

Retention and deletion

• Temporary event data is kept for seconds, with automatic expiry within 6 hours.
• Your account link is deleted when you click Disconnect. Rules are deleted when an admin deletes them.
• Once a week the App checks with Atlassian which accounts were closed, and deletes all data of those accounts (account link, preferences, digest state).
• When the App is uninstalled, all stored data is deleted immediately. Atlassian's platform backups are destroyed within its standard retention period (about 28 days).

Google API Services User Data Policy

The App's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Security

All traffic uses HTTPS. Requests from Google are verified by signature, and account-link codes are cryptographically signed and expire after 15 minutes. See our documentation for details.

Your rights

Under GDPR and similar laws you can request access, correction or deletion of personal data. Because your organisation controls the data, please contact your Jira administrator first. You can also write to contact@mindmotiontech.com and we will help.

Changes

We will post changes on this page and update the effective date.