Seer Data Handling & Automation Safety Checklist

Look forSeer reads error messages and stack traces, spans and traces, logs, DOM interactions, profiles, and relevant linked code. Code Review sends only file names and code diffs, plus pull request descriptions, to the AI provider.

Look forSentry uses your data to train generative AI models only with your permission, and AI output stays within your organization. The opt-in sits under Service Data Usage in Legal & Compliance settings. If you opt in, Sentry applies your deletion and retention rules to training data and scrubs personal data (PII) before training.

Look forBy default, models run in Sentry's production infrastructure without model-provider access. Sentry's June 1, 2026 subprocessor list names Anthropic and OpenAI as US AI/ML subprocessors. In June 2025, Sentry's legal team reported data processing agreements (DPAs) and business associate agreements (BAAs) with its ML infrastructure providers. Sentry offers no IP indemnity for AI-generated code, so have legal accept that gap before Seer opens pull requests.

Look forTurn off Show Generative AI Features to disable generative AI across the organization. Seer settings control features per project and repository, and Advanced Settings can block pull request creation or code pushes. In September 2026, an Elekt developer reported a Seer pull request on an internal repository with generative AI on and no Seer subscription. That report was still open on October 25, 2026, so block pull requests and pushes in Advanced Settings on every repository nobody has approved for Seer.

Look forCERT/CC published VU#212479 for CVE-2026-90999 on September 16, 2026. Anyone can send events to a public DSN, and those events can reach a coding agent's prompt through Seer and trigger code execution with repository access. NVD marks the CVE Deferred and assigns no score. CISA-ADP supplies the record's only score, a CVSS 3.1 base score of 9.8 for a network attack requiring no privileges or user interaction. CERT/CC records notification to Functional Software, Inc., Sentry's company, on August 13, 2026. On October 25, 2026, the note still read "We have not received a statement from the vendor" and carried no vendor status. GitHub's advisory GHSA-vh55-q5m4-8wr6 named no patched version, and Sentry's GitHub security advisories and changelog did not mention the CVE. Sentry's one advisory on this kind of attack, from June 5, 2026, covers crafted public-DSN events that told agents to install typosquatted npm packages. It calls that attack "not a vulnerability within Sentry" and recommends Inbound Filters, especially IP address filters. Follow CERT/CC's advice on every public-DSN project until Sentry ships a fix, and either disable automated remediation or handoff or restrict agent package installs.

Look forSeer Agent queries the whole organization and has no finer-grained access controls. It is unavailable when open team access is off. In June 2026, a user asked to delete Seer Agent conversations because everyone in the organization could still see old sessions. Sentry added the request to its backlog, where it sat unresolved on October 25, 2026, so treat every Seer Agent session as visible to the whole organization.

Look forIn August 2026, a Wamiz developer reported Sentry support's confirmation that Autofix commits cannot be signed. Sentry recommends making the Code Review check optional, so a Seer outage does not block merges. Seer runs on Sentry SaaS in the US or EU region you choose, and self-hosted Sentry does not include it.