Bolt connects Sentry without users' emails: internal IDs replace addresses

For an app built in Bolt, this is a way to retrace the actions leading up to a crash. Session Replay records the user's session, while an internal ID links the error to their account without sharing their email address.

Connecting through Bolt. Connect Sentry in Settings → Connectors → Manage connectors. Once authorized, you can ask Bolt to configure error collection, replace email addresses with internal IDs and send session recordings only when errors occur.

Recordings on errors. In `Sentry.init`, set `replaysSessionSampleRate: 0` and `replaysOnErrorSampleRate: 1.0`. Instead of sampling regular sessions, Sentry sends 100% of sessions with errors, according to documentation dated Jul 30, 2026. The recording retains the preceding activity, so the investigation starts before the crash itself.

Use `Sentry.setUser({ id: userId })` to identify the user. In Sentry developer Luca Forstner's React example, the call sits inside `useEffect` with `[userId]` as its dependency, so the ID updates when the user switches accounts.

You can remove IP addresses and location data in the Sentry project settings: Security & Privacy → Data Scrubbing → Additional Sensitive Fields. According to documentation dated Jul 29, 2026, changes take 5–15 minutes to apply. Add each field on a separate line:

- `city` - `subdivision` - `region` - `country_code` - `ip_address`

To strip sensitive data within the app itself, Sentry recommends `beforeSend` in the SDK. Server-side Advanced Data Scrubbing removes it before storage. Session Replay has separate privacy settings: scrubbing Sentry events does not scrub session recordings.

Sentry is one of Bolt's 8 built-in Connectors, according to company information dated Mar 11, 2026.