Security model
VerityVault combines client-side encryption, controlled access, secure transport, and account protections so sensitive information remains useful without becoming casually readable.
Vault content is protected with keys derived through the user's secure access flow.
The service is designed so stored vault content cannot be casually read by VerityVault.
Email verification and optional two-factor authentication strengthen account access.
Application controls, secure transport, database protection, and monitoring work together.
Transparency matters more than vague security language. Account operations require some service data; protected vault content is treated differently.
Keep it separate from passwords used on other services and store it in a trusted password manager.
Keep your recovery passphrase offline in a place only you, or a carefully chosen person, can reach.
Remove access when a relationship, responsibility, or practical need changes.