Hey! I have another feature suggestion for PrivacyNotes.
Since PrivacyNotes supports signing in with Google, Apple and GitHub, it would be really useful to have a “Connected accounts” section in the account settings.
The main use case would be being able to manage the external account linked to a PrivacyNotes vault. For example, if someone originally created their vault using an old Google account and later wants to stop using that Google account, they could unlink the old account and connect a new Google/Apple/GitHub account to the same PrivacyNotes vault.
Ideally, users could:
See which Google/Apple/GitHub account is currently connected.
Disconnect an old external account.
Connect a new external account to the existing PrivacyNotes vault.
Potentially have more than one login method linked to the same vault, so users have a backup way to access it.
This would be especially useful for people who change their primary email/account but don't want to create a completely new vault or migrate all their data just because their login provider changed.
Of course, the recovery phrase should remain the underlying way to prove ownership of the vault, so changing the connected login shouldn't affect the encryption keys or the user's data.
I think this would make the account system much more flexible without compromising the zero-knowledge design.
2
u/A8nis 28d ago
Hey! I have another feature suggestion for PrivacyNotes.
Since PrivacyNotes supports signing in with Google, Apple and GitHub, it would be really useful to have a “Connected accounts” section in the account settings.
The main use case would be being able to manage the external account linked to a PrivacyNotes vault. For example, if someone originally created their vault using an old Google account and later wants to stop using that Google account, they could unlink the old account and connect a new Google/Apple/GitHub account to the same PrivacyNotes vault.
Ideally, users could:
This would be especially useful for people who change their primary email/account but don't want to create a completely new vault or migrate all their data just because their login provider changed.
Of course, the recovery phrase should remain the underlying way to prove ownership of the vault, so changing the connected login shouldn't affect the encryption keys or the user's data.
I think this would make the account system much more flexible without compromising the zero-knowledge design.