Application Security

Zero-knowledge encryption protects vault entries, saved passwords, and protected identity details. We don't hold the keys needed to read them or your recovery phrase.

Security by Design

How we protect your data

We Can't See Your Passwords or Identity Details

Zero-knowledge encryption means your saved passwords and protected identity details are encrypted on your device before they reach our servers. We never receive the keys that open them.

Anti-Phishing Protection

Your unique security marker proves you're on the real WIGGWIGG site (if you turned it on at sign-up or in Settings). Its seed is stored sealed under a key derived from the first characters of your password, so a stolen database can't mass-render markers.

Modern encryption, built from audited libraries

Hybrid encryption: AES-256-GCM for the content, with the content key sealed by X25519 key agreement, HKDF-SHA256 derivation and XChaCha20-Poly1305, built from the same primitives behind Signal and TLS 1.3.

Quebec Company, Encryption on Your Device

A Quebec company, governed by Quebec and Canadian privacy law. Zero-knowledge encryption protects your vault entries, saved passwords, and identity details regardless of server location.

Your Data, Your Control

WIGGWIGG uses zero-knowledge architecture for protected names, addresses, passwords, and notes, which are encrypted on your device before upload. A forwarding phone number remains server-readable so we can route calls.

We cannot see your passwords, identity details, or recovery phrase. We do not hold the keys that decrypt them, even if we receive a legal request.

Client-side encryption

No server access to keys

You control your data

No password resets

Deep Dive

Application Security Documentation

Learn how zero-knowledge encryption protects vault entries, passwords, and protected identity details

Zero-Knowledge Encryption

We can't see your passwords or identity details, even if we wanted to

  • AES-256 encryption

  • Client-side encryption

  • No key access

  • Encrypted before it leaves your device

Learn more about application security

Anti-Phishing Protection

Built-in protection against phishing attacks

  • Security marker

  • Visual verification

  • Unique avatar

  • Audio signature

Learn more about application security

Recovery Phrase

Your only way to recover access if you lose your password

  • Your only backup

  • 24-word security

  • Offline storage

  • No password reset

Learn more about application security
How It Works

Multiple Layers of Protection

Protected password and identity fields use multiple security layers working together

Learn more about how we protect your communications: Communications Security

Common Questions About Application Security

What is zero-knowledge encryption?

Zero-knowledge encryption means your vault entries, saved passwords, and protected identity details are encrypted on your device before reaching our servers. WIGGWIGG does not hold the keys needed to read them. Operational and communications data follow the separate rules described on the Communications Security page.

What happens if I forget my password?

If you forget your password, you can restore access using your 24-word recovery phrase. This is why we strongly recommend saving your recovery phrase in a secure location when you first create your account. Without your password or recovery phrase, we cannot recover your account. This is by design to protect your privacy.

How does anti-phishing protection work?

Before you enter your full password, we show you a unique security marker (phrase, color pair, and avatar, with an optional audio signature) that only the real WIGGWIGG can display, if you turned it on at sign-up or in Settings. Its seed is stored sealed under a key derived from the first characters of your password, so a stolen database can't mass-render markers. If your security marker doesn't match, don't enter your password. You're likely on a fake site.

Can WIGGWIGG employees see my data?

WIGGWIGG employees cannot read the names, addresses, saved passwords, and notes protected in your vault because they are encrypted on your device before upload. The forwarding phone number on an identity remains server-readable so we can route calls. Operational and communications data follow the separate rules described on the Communications Security page.

What's the difference between application security and communications security?

Application security covers vault entries and protected identity details such as names, saved passwords, and personal details. Communications security covers phone calls and SMS/MMS messages. For communications protected by our current sealing method, stored content is sealed to the account communication key, which a supported client opens after sign-in and unlock. A small set retained from the private beta remains readable under our older server-side encryption until a separate re-sealing process. For communications sealed this way, the difference from the vault is not the protection at rest but when that protection begins: we choose to check the pictures in MMS messages in memory, before encryption; the text of a message is never fingerprinted. Preservation or reporting duties can apply if review confirms a picture is illegal. A few named exceptions stay readable by our servers; they are listed on the Communications Security page.

How do I know my data is actually encrypted?

Encryption of your vault entries, protected identity details, and contacts happens in your browser with Web Crypto and audited JS/WASM libraries. Contacts stay zero-knowledge unless you enable contact recognition for calls. You can inspect network traffic to verify that these protected fields are sent to our servers as ciphertext. Operational data and telephone content in transit follow separate paths and may be readable by our servers or providers, as described on the Communications Security page. For inbound messages protected by our current sealing method, the one-time key is sealed to the account communication key, which a supported client opens after sign-in and unlock. A small set retained from the private beta remains readable under our older server-side encryption until a separate re-sealing process.

What if WIGGWIGG gets hacked?

Even if someone breaches our servers, protected password and identity fields remain encrypted. An attacker would obtain ciphertext for those fields, which cannot be decrypted without your password. We never store your password, and we never store a vault encryption key in a form we can open.

Can I export my data?

Yes. You can export your account data (JSON or HTML) and your vault (Bitwarden JSON or CSV, unencrypted, for moving to another manager). In the account export, the encrypted content of your identities, contacts, and messages stays encrypted, as it is stored; you read it in the app, not from the file.

Ready for Zero-Knowledge Security?

Get started with WIGGWIGG today and experience true data privacy