Security

Last updated 15 November 2026

What we do

  • Secrets are encrypted. Connector secrets, calendar sign-ins and integration tokens are encrypted at rest with AES-256-GCM.
  • API keys are stored as hashes. A key is shown once, when you create it. We cannot read it back.
  • Requests are signed. Webhooks to you and calls to your connector carry an HMAC-SHA256 signature and a timestamp, so they cannot be forged or replayed.
  • Test and live are separate. Keys, tenants, webhook endpoints and events for test never mix with live.
  • Your data is yours alone. Every read and write is scoped to your organization, and the database denies direct access from the public internet.
  • We check the addresses you give us. Webhook, connector and calendar feed addresses must be public HTTPS addresses, so they cannot be pointed at our internal systems.
  • No call audio is recorded. Sanaa keeps a transcript and summary of each call, not the audio.
  • Phone numbers cost real money, so they are controlled. Numbers are limited per account, only for live accounts, and only in the US and Canada.

Who handles your data

Sanaa uses a small set of providers to run: Telnyx (voice and phone numbers), Supabase (database), Vercel (hosting) and, when you turn them on, Stripe (payments) and the calendar, chat or CRM tools you connect yourself. We do not sell your data.

What we do not claim

Sanaa has not completed a SOC 2 or similar independent audit. If you need one, tell us.

Report a problem

If you find a security problem, please tell us through your account's Help tab, marked as urgent, and give us a reasonable time to fix it before sharing it.