Security, in plain words.

What we do to protect your meetings, tickets and code, what we do not do yet, and who else handles your data.

Last updated 1 October 2026. A first sketch: bracketed values are still to be confirmed.

In short

  • Everything travels over TLS, between your browser and us and between our services.
  • Meeting recordings and documents are stored encrypted at rest.
  • Your meetings, tickets and code are not used to train models.
  • You sign in without a password, and every request is checked against your organisation and project.
  • We hold no security certification yet, and we say so rather than imply one.

At a glance

Encryption in transitYesTLS on every connection.
Encryption at restTo confirmRecordings and documents: yes. Database: [to confirm].
Where data is hostedTo confirm[hosting region and provider]
BackupsTo confirm[frequency, retention and restore testing]
Passwordless sign-inYesEmail code or your identity provider's account.
Single sign-on (SAML)Not yetPlanned for Enterprise.
SOC 2NoNot held. We will say here when an audit starts.
ISO 27001NoNot held.
Penetration testNot yetNone yet. The first will be summarised here.
Status pageNot yetNot yet published.

Who else handles your data

  • Clerk — Sign-in and sessions · [region]
  • LiveKit — Live audio and video for meetings · [region]
  • Cloudflare R2 — Storing meeting recordings · [region]
  • [speech-to-text provider] — Transcribing recordings · [region]
  • Anthropic — Turning transcripts into summaries and tickets · [region]
  • Resend — Sending invitation email · [region]

Report a problem

Found a vulnerability? Write to security@iter8.co.uk. Acknowledged within three working days, and we will not take action against research done in good faith.