Privacy policy
Last updated 2026-10-24 (beta).
What we store
- Your Sentry organization slug, installation id and region.
- Credentials needed to act on your behalf: short-lived Sentry access tokens, or for Internal Integrations the client secret and token you provide. Encrypted at rest (AES-256-GCM).
- Google Chat webhook URLs you add and the names you give them. Encrypted at rest.
- For threading: which Sentry issue ids were posted to which Space, and their last state. Deleted after 90 days without activity.
- Operational logs without message content: timestamps, status codes, internal ids.
What we don't store
- Sentry event payloads, stack traces, tags, request data, or data about your application's users. Alerts are processed in memory; a rendered card waits in a delivery queue only until Google Chat accepts it (normally seconds).
- Emails, IP addresses and token-like strings found in issue titles are masked before posting to Chat.
Who processes data
- Cloudflare, Inc. hosts the service (Workers, D1, Durable Objects).
- Google receives the messages you route to Google Chat. Sentry receives the status changes and comments you trigger.
Retention and deletion
Uninstalling the integration deletes your Spaces, tokens and thread references immediately. Remaining account records are deleted on request.
Contact
Oopsbell is made by Sperar. Not affiliated with Functional Software, Inc. (Sentry) or Google LLC. Google Chat™ is a trademark of Google LLC.