Personal Safety — breach monitoring and your protection posture

Personal Safety is your protection posture in one place, at /me/safety. It is a core account-level surface — like emergency contacts, it is always available in your Personal context, not a module you turn on. It doesn't store anything new; it reads your own data and lets you manage your own settings.

Breach and identity monitoring:

The page shows breach alerts for the identities you have verified — if an email or other verified identity of yours turns up in a known data breach, it surfaces here with plain-language guidance on what to do. You can acknowledge or resolve each alert as you handle it. Only verified identities are ever checked, and only you can read your own alerts.

The monitoring opt-out:

Monitoring is on by default because it is protective, but it is your call — there is a single opt-out on the page if you don't want it running.

What is being monitored:

The page lists the verified identities under monitoring, pulled from your identity graph, with a link to add or verify more. The more of your identities are verified, the more complete the coverage.

Your protection posture:

Personal Safety also links out to the surfaces that own each protection rail rather than duplicating them — passkeys and two-factor coverage live in your Account settings, and trust visibility lives at /me/trust. The page gathers the picture and points you to the right place to change each piece.

A note on what is real:

The breach check is server-side and privacy-preserving — only verified identities are checked, and the external check is enabled by the platform rather than something you configure. Masked-email aliases and data-broker removal appear as clearly-labeled upcoming items; they are on the roadmap, not built yet, and the page says so plainly rather than pretending otherwise.