Privacy-focused design
Your secrets have no home at MystSafe.
You do not create a conventional MystSafe username or email login to hold your vault. Secret contents live encrypted on your trusted devices, and MystSafe does not operate a central vault database or synchronization service.
PRIVACY BEFORE THE VAULT
Encryption can hide your secrets. Registration can still identify you.
Encryption protects what is inside a vault. Registration can still identify the person behind it.
A conventional vault account creates a lasting identity record—usually an email address, username, login, and recovery path—around the service protecting your most sensitive information. Even when the vault contents remain encrypted, that account becomes another source of personal data to expose and another login for attackers to target.
MystSafe lets you create and use your core vault without giving MystSafe your name, email address, or phone number. Your trusted devices establish access, so there is no MystSafe vault login to remember or recover.
MystSafe cannot read your vault in normal operation and does not collect a history of the items you open, search for, or copy. Because MystSafe does not possess readable vault contents or that local access history, it cannot report or disclose them. Editing can create encrypted updates and synchronization traffic.
Connected services still process technical information. License and device identifiers can connect requests and purchases; pairing and Share Once keep limited operational state; your chosen Google Drive or GitHub provider sees account and network metadata. Google Sign-In declares some data for functionality and analytics. See what each service handles.
Your devices unlock your vault. No personal signup details required.
Put privacy-focused design to work
Keep your encrypted vault device-controlled without a conventional MystSafe account or central MystSafe vault database.