Security & Privacy

Your identities and their vaults are client-side encrypted. Only you hold the keys. We can't see your passwords, credentials, or personal information. Built secure from day one.

Security Overview

Two Layers of Protection

We protect your data in two distinct ways: Application Security (zero-knowledge encryption for your identity data) and Communications Security (privacy-first handling of phone calls and messages).

Application Security

Zero-knowledge encryption, authentication, and account recovery systems that protect your identity data.

  • Zero-knowledge encryption
  • Password never leaves device
  • Anti-phishing protection
  • Multi-factor authentication
  • Recovery systems
  • We cannot read your vault or identity data
Learn more about Application Security

Communications Security

How we handle phone calls and messages while minimizing data collection and complying with telecom laws.

  • Checked by fingerprint, never by sending your picture
  • Zero-knowledge encrypted storage
  • Minimal metadata retention
  • Telnyx infrastructure
  • Legal compliance
  • Full transparency
Learn more about Communications Security

Built Secure from Day One

Security isn't an afterthought at WIGGWIGG. It's our foundation. We use zero-knowledge encryption for your identity data and implement privacy-first practices for all communications.

Zero-Knowledge Client-Side Encrypted Identity Data Privacy-First
Account access

How you sign in

Your password opens the door. A second factor checks that it's really you. And neither one decrypts your data for you.

Passkeys

A passkey replaces the code you type with what your device already knows how to do: your fingerprint, your face, or the device PIN.

  • It's bound to the official domain. A site imitating us, even copied pixel for pixel, can't use it: that's what makes it phishing-resistant.
  • It adds to your password, it doesn't replace it. We ask for the password, then the passkey.
  • You can register several, one per device, and remove one at any time.

The authenticator app

A six-digit code that changes every 30 seconds, generated by the authenticator app of your choice.

  • The code is generated on your device, offline. Nothing travels by text message, so there's nothing to intercept at the carrier.
  • You set it up from the web dashboard, in your security settings.
  • It's a good option when you want a second factor that doesn't depend on one single phone.

A recovery key before the first factor

Before you turn on your very first second factor, we ask you to have a recovery key in place: the 24 words you write down and keep. Nobody here can reset your keys for you: a lost device must never be able to lock you out for good.

What this protects, and what it doesn't

A passkey and an authenticator code protect access to your account. They don't unlock your data: the key that decrypts your vault and your identities is derived from your password, and your 24-word recovery phrase remains the only way to rebuild it.

Deep Dive

How Our Security Works

Explore our multi-layered security architecture. Each layer protects you differently, and together they provide defense in depth.

Zero-Knowledge Authentication

Your password never leaves your device. We prove you're you using cryptographic signatures, not by storing your credentials.

How Authentication Works

Anti-Phishing Protection

Two-way authentication where the website proves its identity to you before you enter your full password.

How Anti-Phishing Works

Recovery Phrase

Your ultimate backup: a 24-word phrase that can restore account access when you've lost everything else.

How Recovery Works

Spam Filter

Up to five checks, depending on the channel, assess calls, texts, and MMS. Carrier lookup and community reports have their own switches; STIR/SHAKEN and neighbor-spoof are always read when they apply.

How the Spam Filter Works

Security Whitepaper

The full technical account: threat model, cryptographic architecture, data classification, and an honest list of our limitations. Written for a skeptical, technical reader.

Read the Whitepaper

Vulnerability Disclosure

Found a flaw? Here's how to report it, in good faith and without fear: our scope, the rules, a real safe harbor, and what to expect in return.

Read the Disclosure Policy

Responsible Use

Our public commitment to platform integrity. What WIGGWIGG is for, what it must never be used for, and how we enforce it.

Read Our Commitment

Security Questions

Can WIGGWIGG see my passwords?

No. Your passwords and identity details are encrypted on your device using zero-knowledge encryption before reaching our servers. We mathematically cannot decrypt your data - only you hold the keys. No one at WIGGWIGG can see your passwords.

What happens if WIGGWIGG gets hacked?

Even in the unlikely event of a breach, your passwords and identity data remain protected. They're encrypted with keys only you control, so attackers would only get encrypted gibberish. We also use industry-standard security practices to prevent breaches in the first place.

How is WIGGWIGG different from other password managers?

WIGGWIGG combines zero-knowledge password management with Canadian phone numbers and complete identity management. You can organize passwords by identity (work, personal, business) and each identity can have its own phone number. It's a privacy-first digital identity platform.

What is zero-knowledge encryption?

Zero-knowledge encryption means your data is encrypted on your device before it's sent to our servers, using keys derived from your master password. We never see your master password or encryption keys. This is the same approach used by security-focused services like 1Password and Bitwarden.

Are my phone calls and texts private?

We minimize what we collect from communications. We choose to perform certain safety checks, including spam filtering and detection of known illegal content, in memory at receive time. Preservation or reporting duties can apply if review confirms the content is illegal. Under our current method, message content is sealed on Canadian servers to the account communication key, which a supported client opens after sign-in and unlock. Voicemail audio is sealed the same way when Listen-by-phone is off and a usable account communication key resolves. For a communication sealed this way, we keep no key that can read it. A small set retained from the private beta remains readable under our older server-side encryption until a separate re-sealing process. A few exceptions stay readable by our servers, and we name them: voicemail while Listen-by-phone is on or when the account has no usable communication key, the other party's number in a call log when the account has no usable key or key lookup fails, the intros your callers record, automatic-reply text, the text and audio of your voicemail greeting, of the announcement we play to you on pickup, and of the prompt your callers hear before they identify themselves. We never record your calls. A call-recording add-on is on the roadmap; if it ships, recordings will be sealed to you like voicemail. For end-to-end encryption between sender and receiver (we never see plaintext at all, even in transit), use Signal with your WIGGWIGG phone number.

Where is my data stored?

Your encrypted identity data is stored in Canada, subject to Canadian privacy laws (PIPEDA). VoIP communications are transmitted through Telnyx (US-based, SOC 2 Type II compliant). Remember: your identity data is encrypted on your device first, so location matters less when the data is unreadable anyway.

Ready to Create Your First Identity?

Discover a better way to manage separate identities, sealed with zero-knowledge encryption.