Copy versus live permission
Sharing a password through Google Password Manager is not a live permission that you can revoke for the recipient. It creates a copy that lives in the recipient’s Google Account. There is no supplied mechanism for retroactively deleting that copy, and you should not assume one exists.
Google Password Manager can share a copy of a saved password with a member of your Google family group; that copy is stored in the recipient’s Google Account. Source
Because the copy already exists, the practical way to stop the sharing is to change the password at the service itself. Google’s own guidance points to this.
Google advises changing the service password when you no longer want to share that service. Source
A common mistake is editing or deleting the entry in your own password manager and treating that as done. That action changes your record, not the credential the service accepts. The recipient’s copy, and any session already opened with it, is not affected by your local edit.
Rotation checklist, service by service
Work through each service where you shared a password. The order matters: change at the service first, then update your own record.
- Sign in to the service directly and change the password there.
- Update the saved entry in your Google Password Manager so it matches.
- If the service offers a way to sign out other sessions, use it; do not assume changing a password ends existing sessions.
- Repeat for every service where the same password was shared or reused.
- Remove the shared copy from your own view only after the service password has changed.
Reuse is the multiplier here. If the shared password also protected other accounts, those accounts are exposed to the same recipient.
Reusing the same password on other accounts can expose those accounts to someone with whom you shared it. Source
Decision table
| Situation | What actually stops the sharing | What does not |
|---|---|---|
| You shared one service password | Changing that service’s password | Editing your password-manager record only |
| The same password is reused elsewhere | Changing it at every service that uses it | Changing it at one service |
| You want to tidy your vault | Removing your local entry after rotation | Assuming removal deletes the recipient’s copy |
| You are unsure which services were affected | Rotating every service that used that password | Waiting for a revocation notice |
Manual verification
After rotation, confirm the change took effect at the service, not just in your vault. Sign in with the new password in a fresh session, and check that the old one is rejected. If the service shows active sessions, review them. Do not treat an edited or empty profile as evidence that stored data was deleted.
For broader account-audit guidance, see our related methodology articles on TruthsSeek. TraceSeek can optionally check known public usernames across 3,000+ platforms, with a free first scan and results typically in 20-30 seconds. It cannot change platform settings, access private content, prove ownership, or find all accounts by phone or email. A public username match is a lead, not proof of ownership.
Key facts
Google Password Manager can share a copy of a saved password with a member of your Google family group; that copy is stored in the recipient’s Google Account.
Google advises changing the service password when you no longer want to share that service.
Reusing the same password on other accounts can expose those accounts to someone with whom you shared it.