VaultZero-knowledge: even we can't see your passwords

Secure Client Credentials, Zero Chaos

Client passwords,
locked down.

Store client passwords, API keys and logins in an encrypted vault per workspace. Your team gets the access their role allows, and every view is on the record.

Free plan forever. Paid plans include a 14-day trial.

Client logins usually live in a shared spreadsheet, an old Slack thread and someone's notes app. Whizo keeps them in one encrypted vault per client, opened with a key only your team holds.

01 / Inside the vault

Unlock, use, lock again.

The master password opens one client's vault and nothing else. Every view is logged, and the vault closes itself when nobody is using it.

Locked

  1. Master password enteredAES-256 key derived in your browser
  2. Vault unlockedOda Dental workspace only
  3. Sarah viewed Instagram loginLogged with time, IP and device
  4. Mike offboardedWorkspace access removed, vault with it
  5. Auto-lockedAfter 5 idle minutes, or the timer you set

02 / Security

Safe by design, not by policy.

Encrypted in your browser, before it is saved

Gl0w!Smile#2026AES-2568f3ac91e77d0a4b2e6150c9f3db852e1

Zero-knowledge encryption

Credentials are encrypted with AES-256 using a key derived from the workspace's master password. We only ever store the encrypted result, so even we can't see your passwords.

Oda DentalLumen SkinKiln Coffee

A vault per client

Each client workspace has its own vault and master password. Credentials never leak between clients.

SarahDesignerViewMikeManagerManageAnaFreelancerNo access

Role-based access

Viewing and managing are separate permissions. Remove someone from the workspace and their vault access goes with it.

  • Sarah viewed Instagram10:42 · 103.21.x.x · Chrome
  • Mike updated Meta Ads10:15 · 49.36.x.x · Safari
  • Mike deleted an old FTP login09:58 · 49.36.x.x · Safari

Audit trail, auto-lock, generator

Every view, edit and delete is logged with who, when, IP and device. The vault locks itself after inactivity, and a built-in generator makes strong passwords in one click.

03 / By the numbers

The details that keep it closed.

AES encryption, done in your browser

PBKDF2 rounds turn the master password into the key

default auto-lock when nobody is using it

isolated vault for every client workspace

04 / Questions

Questions, answered.

How secure is the password vault?

Credentials are encrypted in your browser with AES-256 before they are saved, using a key derived from your workspace's master password. Each workspace has an isolated vault. It's zero-knowledge encryption: we only ever store the encrypted result, so even we can't see your passwords.

Who can access stored passwords?

Only team members whose role includes vault access for that client workspace, and who know its master password. Viewing and managing are separate permissions, so junior staff can read credentials without being able to edit or delete them. Remove someone from the workspace and their vault access goes with it.

What types of credentials can I store?

Website and social logins, email accounts, API keys and any other secret. Each entry holds a title, username, password, URL and notes, and sits in a category such as Social, API Key, Client or Email. There is no cap on entries per workspace.

Can I share credentials with team members?

Yes, at the workspace level. Everyone whose role has vault access on a client's workspace can unlock that workspace's vault with its master password. There are no per-credential or external share links, and every view, edit, and delete is logged.

Is there an audit trail?

Yes. Every view, edit, and delete is logged with who did it, when, their IP address, and their device, so you can maintain security compliance and track team activity.

Lock up every
client login today.

Start free trial

Free plan forever. No card needed.