MySudo Password for Safari is a Mac password manager whose organising idea is identity compartmentalisation. The official description groups passwords, passkeys and payment details by the Sudo identities created in the separate MySudo privacy app. That is a more specific proposition than simply collecting every login in one undifferentiated list: a user can distinguish shopping, travel, banking and personal accounts by the identity associated with them.
The target audience is someone already using, or prepared to understand, that Sudo identity model. Organisation can reduce confusion, but it does not by itself prove that websites cannot correlate activity. This is a source-based First look, not a security audit. We have not tested encryption, browser integration, recovery or resistance to compromise.
Based on official store information. We have not tested this app hands-on.
What it does
The documented workflow starts with an encrypted vault and entries organised by Sudo. A sensible first step is deciding which identity belongs to a particular account before saving its login. If an existing account uses an address associated with a different identity, moving its password into another group does not necessarily change the information already held by the website.
The listing names strong unique password generation, autofill for passwords and passkeys, and saving new logins while browsing. Those functions address different points in an account's life: creating credentials, using them and retaining a new entry. Check the site and selected identity before accepting an autofill suggestion. A correct password applied to the wrong intended account is still an organisational mistake.
Weak or reused password identification is also listed. Treat an alert as the beginning of a deliberate account update, not evidence that changing a vault entry changes the website automatically. Confirm that the service accepts the new credential and that recovery information remains available. The developer describes synchronising an encrypted vault across mobile and desktop, which makes it important to understand which devices can access the same identities.
Before you install
The developer states that the product uses end-to-end encryption and biometric authentication. Those are attributed design claims, not properties we have independently verified. Review the current security documentation and recovery process before relying on the vault as the only record of important access. Biometric convenience does not answer what happens after a lost device or a failed authentication attempt.
Identity compartmentalisation also has limits outside the password manager. Reusing contact details, payment information or identifying content can connect accounts regardless of how neatly their credentials are grouped. The store's broad claim about preventing cross-linking should therefore not be interpreted as proof of complete anonymity. Consider the whole account relationship and the information already shared with each service.
Safari integration needs its own permission review. Understand what the current extension requests and what must be enabled for the intended workflow. We have not inspected its implementation or established compatibility with every website and passkey flow. Before moving a large collection, use a low-risk account to learn how entries are created, selected and updated without losing the original recovery path.
A useful migration plan keeps the old and new records understandable until the new workflow has been checked. Avoid deleting an existing vault merely because an import or saved entry appears successful. Verify a representative login on the actual website and understand any export or recovery options documented by the provider. The reviewed listing does not establish every migration capability, so those should be confirmed rather than assumed.
A separate identity is most useful when the associated contact information and account purpose are also consistent. The manager can organise that decision, but cannot make it automatically correct.
Price and access
The linked US Mac App Store entry offers a free download. The description ties the identity organisation to Sudo identities created in MySudo, so check the current access requirements and terms for both products before assuming installation alone supplies the complete arrangement.
The reviewed source does not establish a complete subscription price, unlimited entitlement or every account prerequisite. Confirm those details in the official purchase and setup information. Evaluate the service around the credentials and devices it must support, not only the installation price. We have not tested purchase restoration, access after a plan change or how a separate MySudo account affects the vault workflow.
Our take
The distinctive reason to inspect MySudo Password is the relationship between credentials and deliberately separated identities. That may help a user who already thinks in those categories and wants the same structure visible when browsing in Safari. Someone seeking only a basic password list should first consider whether the additional identity model is useful to their routine.
Start by mapping a few existing accounts to their intended identity, then investigate the provider's security, recovery and compatibility documentation. Try a small, reversible workflow before changing important banking or recovery credentials. The listing describes useful password-management functions, but it does not replace independent judgement about account separation. Our take remains provisional until there is documented practical testing and a clearer account of the access conditions relevant to the individual user.
Sources
App icon from the official store listing.
