Skip to content

Security

Security you can read

Hashed credentials, scoped tokens, encryption in transit and per-client rate limits.

Credentials

  • API keys and agent credentials are stored only as hashes, and keys are also peppered. A key's secret is shown once, at creation, and never again.
  • Browsers never see an API key. They get connection tokens scoped to one session and one user, which expire after an hour.
  • Passwords are stored as slow, salted bcrypt hashes. Sign-ins use httpOnly cookies that scripts cannot read.
  • Creating an API key, a restricted key or an agent token, or approving an agent, requires a verified email address.
  • An API key runs your video, not your account. Inviting or removing teammates, changing roles and opening billing need a signed-in owner or admin, so a leaked key can't add a stranger or reach your card.
  • Agents sign in with OAuth 2.1 and PKCE, and their tokens work only on the MCP server. You choose the projects each agent can use, and can disconnect it at any time.

In transit

  • All traffic is encrypted with TLS, and HSTS makes browsers refuse plaintext.
  • Media travels over the same encrypted WebSocket. Tokens go in the WebSocket subprotocol, not the URL, so they stay out of logs.

Your data

  • We relay and store media as opaque bytes, without decoding it. It is decoded only when you ask for an MP4 export, or for a transcript you turn on or ask for, when each participant's speech is sent to Deepgram for speech-to-text. We don't analyse its content otherwise, and we never train models on it.
  • Retention is set per project, from 1 day up to 7 on Free and 90 on pay-as-you-go. Deleting a session or a project deletes its streams, exports and replay links.
  • One API call deletes a single participant's camera, microphone and screen tracks from a recording. Their chat messages are kept. MP4 files exported before the redaction are left alone. The call returns their ids so you can delete each one, and the next export is rendered without that person.
  • Every API key belongs to one project. A key from one project cannot read another project's sessions.
  • Account data is replicated continuously to separate object storage, with 30 days of point-in-time recovery.

Application hardening

  • Rate limits are applied per API key and per client address, and sign-up and password-reset requests get a tighter hourly limit.
  • Webhook targets are checked against private-network addresses, and every delivery is signed with HMAC-SHA256.
  • This website sends a strict Content-Security-Policy, HSTS, and anti-framing and isolation headers.
  • Production refuses to start with a default secret or a misconfigured billing key.