Google currently offers users a way to customize Chromesync. You can either choose to sync everything or specific items like bookmarks, history, and passwords, etc. Within passwords, you might soon get an option to choose which password is stored locally on the device and which goes to the cloud or your Google account.

More Control

A code commit and a few related bug reports that we spotted suggest that Google is working on a project, code named “Butter for passwords” that will give users more control over how passwords are stored.

“chrome://settings/passwords: Show badges for local vs account passwords

This CL adds badges to each password and exception item in
chrome://settings/passwords that identify the storage location of the
item (on this device, or in the Google Account).
The badges only show up if the feature “EnablePasswordsAccountStorage”
is enabled (aka chrome://flags/#passwords-account-storage), and the user
is opted in to the account-scoped password storage.

The badge icons and labels are not final.”

The bug associated with this feature request adds a little more clarity:

“Adapt chrome://settings/passwords to support account-storage passwords. This includes:

• Listing account pwds (already done)
• Differentiating local vs account pwds (separate section and/or badging; no final mocks yet)
• Probably show opt-in status and offer to opt in/out”

From related bug reports that tagged as “Butter for passwords”, the plan seems to be to:

1. Give users an option to choose where to save each password.
2. Add icons next to each password to show whether it is saved on the device or in the cloud.

The design document and screenshots mentioned in the code commit pages are restricted. We will have to wait for few more updates to the Canary channel of Chrome to see this feature in action.

We shall update this article as soon as additional details become available. Stay tuned.

Source: Gerrit and Chromium bug repository.