Wisp

Subprocessors

Last updated 18 July 2026

We use the following third parties to run BA | Wisp. Because content reaches us already encrypted, subprocessors that touch storage handle only ciphertext.

Infrastructure and storage

Hosting and serverless compute: Vercel. Application database (accounts, metadata, ciphertext for small messages): a managed PostgreSQL provider in the EU. Object storage for larger encrypted attachments: AWS S3, EU region. Storage subprocessors hold ciphertext only.

Authentication and email

Sign-in providers you choose to use: Google, Microsoft, GitHub. Transactional email, including sign-in links: our email provider. These see your email address, not message content.

Public networks used for proof

Anchoring publishes a hash to the Polygon and Bitcoin networks via public infrastructure and the OpenTimestamps calendar network. These are public, permissionless networks, not subprocessors in the usual sense; what they receive is a one-way hash of already-encrypted data.