Security

What we do today to protect vaults — and what we are still hardening.

Last updated: July 23, 2026

Current controls

  • HTTPS for traffic to the application.
  • Authentication via NextAuth with optional Google and Apple sign-in.
  • Media stored in cloud object storage with per-user path isolation.
  • Server-side authorization checks on media and dashboard APIs.
  • Rate limiting on sensitive API routes when Redis/Upstash is configured.
  • Payment processing via Stripe when paid plans launch (not active yet).

Honest limitations (in progress)

  • Capsule passwords are bcrypt-hashed before storage and checked on unlock/claim. This is a share-link gate — not end-to-end encryption of media bytes.
  • Third-party imports (e.g. Google Photos) are not production-ready; prefer manual upload.
  • Media blobs still use Firebase Storage in this cutover; structured capsule data moved to Cloudflare D1. R2 cutover is next once the bucket is enabled.
  • Long-term estate / death-protocol access workflows are on the roadmap and not fully automated yet.

Your responsibilities

  • Use a unique, strong password and enable provider MFA where available.
  • Only invite people you trust when family sharing features are enabled.
  • Keep local devices and recovery emails secure.

Reporting issues

If you believe you found a security vulnerability, contact us via Contact with steps to reproduce. Please avoid public disclosure until we have had a reasonable chance to remediate.

Questions? Contact us.