[ANN] MystSafe - a fundamentally different secret vault

[myst-safe]

NO ACCOUNT.
NO PASSWORD.
NO BACKEND.

MystSafe is fundamentally different from conventional password managers and secret vaults.
Conventional password managers keep a permanent encrypted vault under the provider’s custody.
MystSafe keeps the vault on your trusted devices and uses external storage only to move signed, encrypted updates.

There is no MystSafe-operated sync backend.
MystSafe connects directly to storage you choose.

Quantum-Safe Cryptography
MystSafe combines standardized post-quantum algorithms with established classical cryptography, so confidentiality and authenticity do not depend on a single cryptographic family.

Free after beta. Free at home and at work.
Use MystSafe for personal, family, freelance, and individual professional work at no cost.

Website
https://mystsafe.com

[myst-safe]

App Store launch

MystSafe is now on the App Store!
A password manager and secret vault.
No MystSafe account.
No master password.
No MystSafe-hosted central vault.
Your secrets. Your devices. Post-quantum protection.

https://mystsafe.com/get-mystsafe/
#MystSafe #Privacy

Remember less

A password manager shouldn’t give you another password to remember.

Meet MystSafe: no master password, no MystSafe account. Your vault stays on your devices.

Start free on iPhone, iPad & Mac:
https://mystsafe.com/get-mystsafe/

[myst-safe]

No master password does not mean no authentication

Disclosure: The explanation below is AI-generated and is shared for discussion.

Removing a master password does not remove the need to authenticate. In MystSafe, the user's trusted device authorizes vault access through local authentication. There is no MystSafe username or email login.

The distinction is between protecting access and memorizing a separate vault password. Device security and a recovery plan still matter; “passwordless” does not mean those responsibilities disappear.

The vault lives on the user's devices. Synchronization carries encrypted updates through the chosen provider rather than placing a permanent vault database under MystSafe's custody.

The useful questions are about the boundaries of that model: how another device becomes trusted, what happens when a device is lost, and how recovery is prepared in advance.

Which of those would you want explained first?

Product context:
https://mystsafe.com/get-mystsafe/

[myst-safe]

“One recipient can claim a share” is not the same as “nobody can keep a copy.”

MystSafe Share Once uses an encrypted, time-limited link. A browser recipient can claim the share without installing the app. The single-claim rule governs the exchange; it cannot control a screenshot, photograph, or copy made after the secret is revealed.

That distinction is important when evaluating a short-lived sharing workflow. Ask two questions separately: what prevents another protocol claim, and what can the successful recipient retain?

For a low-stakes test, use made-up sample text rather than a real credential. Review the claim behavior, the browser-viewing experience, and what happens when a link expires.

What wording would make this boundary clearest in a sharing screen?

Product context: https://mystsafe.com/get-mystsafe/

[myst-safe]

An encrypted vault and the account registered around it are two different things to evaluate.

With MystSafe, creating and using a vault does not require a separate MystSafe username or email registration. Trusted devices establish access instead.

That removes a conventional MystSafe vault login from the setup. It does not remove every provider or every kind of metadata: Apple handles App Store purchases, and synchronization uses the selected Google Drive or GitHub account. MystSafe also operates limited services with their own information handling.

For us, the useful distinction is between vault confidentiality and account privacy. A product can address one without making the other question disappear.

When evaluating this design, what would you want made most visible: which service establishes vault access, which accounts are still required, or what metadata each service processes?

Product context:
https://mystsafe.com/get-mystsafe/