Security

How we protect your meetings. MeetriX is sold to governments and enterprises, and the security model reflects that.

In transit and at rest

Service traffic uses TLS. Meeting audio, transcripts, and reports are stored on managed infrastructure with encryption at rest.

Access control

• Meetings are private to their owner by default; sharing is explicit and per-meeting.
• Workspaces have roles, so institution members see only what their role allows.
• Institution administration supports member roles; record access and delivery settings are configured separately.

Your data is not training data

Our AI is never trained on your data. The speech engine is our own, self-hosted; your audio is not sent to a third-party transcription API.

Deployment options

Three ways to run MeetriX, matched to your data policies:

• Our cloud: the default, fastest way to start.
• Private cloud: a dedicated, single-tenant environment under your control.
• On-premise: the entire pipeline, speech engine included, running on your own GPUs inside your network. The processing boundary, online-platform connectivity and enabled delivery integrations are agreed for each deployment.

See security & on-prem for the full picture, or talk to us about your requirements.

Responsible disclosure

Found a security issue? Email support@lisan.com and we'll work with you. Please don't test against other customers' data.