WIGGWIGG is built on a zero-knowledge architecture: your vault data and identity details are encrypted on your device. For communications protected by our current sealing method, stored content is sealed to your account communication key, which a supported WIGGWIGG client opens after you sign in and unlock. We keep no key that can read a communication sealed this way. A small set of communications retained from the private beta still uses our older server-side encryption and remains readable by us at rest. Signing in and unlocking in a supported web client automatically starts a separate bounded pass for up to 50 eligible SMS rows. Private-beta voicemail, call-log numbers, MMS attachments, retained object versions, and additional SMS rows remain server-readable until later passes or separate maintenance. The companies below (“subprocessors”) help us operate the WIGGWIGG Service. We share only what is necessary, and only in encrypted or non-content-bearing form, except where a function inherently requires otherwise (for example, telecommunication carriers carry call and SMS content, as is true of all phone networks).
| Subprocessor | Purpose | Data categories | Location |
|---|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting: databases, encrypted media storage, application servers | Encrypted user data, account metadata | Canada (DNS query logs in us-east-1 for 90 days; CDN edge caches of encrypted files in North America and Europe) |
| Telnyx | Voice, SMS/MMS and 911 (E911) connectivity | Phone numbers, call/SMS routing and content in transit, E911 address (registered and retained by Telnyx for emergency routing; our stored copy is encrypted) | United States |
| Stripe | Payment and subscription processing | Billing details, payment tokens (we never store full card numbers) | United States / global |
| Blockonomics | Cryptocurrency payment processing | Crypto payment addresses, amounts, transaction metadata | Global |
| Resend | Newsletter delivery (and unsubscribe confirmations) to addresses subscribed on the Website | Email address, newsletter content | United States |
| Canadian Centre for Child Protection (Arachnid Shield) | Automated detection of child sexual abuse material (CSAM) in media | The perceptual fingerprint (PDQ) of each picture, computed on our own servers. The picture itself is never sent. No account identifiers. Confirmed matches are reported as required by law | Canada |
| Microsoft (PhotoDNA edge hashing) | Automated detection of child sexual abuse material (CSAM) in media | The PhotoDNA edge hash of each picture, computed on our own servers. The picture itself is never sent. No account identifiers. Confirmed matches are reported as required by law | United States / global |
| Have I Been Pwned (Pwned Passwords) | Password breach checks | 5-character SHA-1 prefixes of passwords (k-anonymity), through our own edge cache; never the password or its full hash | United States / global |
| Apple (APNs) | Push notification delivery to iOS devices | Device push tokens, encrypted notification payloads | United States |
| Google (FCM) | Push notification delivery for the Android app installed from Google Play (our de-Googled build uses our own relay instead) | Device push tokens, encrypted notification payloads | United States |
| Browser push services (Mozilla, Google, Apple) | Web push delivery | Push endpoint, encrypted notification payloads | Provider’s region |
| Vercel | Hosting for the marketing website (not the WIGGWIGG application) | Website visitor request data (e.g. IP address) and newsletter sign-up submissions in transit | United States |
We may update this list as our services evolve. Material changes will be reflected in our privacy policy.