Privacy by architecture — encryption and self-hosting

Plenty of products bolt privacy on at the end. MeetOye builds it into the shape of the system, so the safe path is also the default path.

Media never touches the brain

Audio, video and screen share flow through a dedicated media engine (a self-hosted LiveKit SFU). The backend API only mints scoped join tokens and stores metadata — it never sees raw media. That single rule shrinks the surface where sensitive content can leak.

Controls teams ask for

• End-to-end encryption on by default.
• Self-hosted and on-prem deployment — keep all media inside your own network.
• SSO, SCIM and granular host controls.
• Transcripts visible only to attendees, never shared with third parties.
• SOC 2 Type II, GDPR and HIPAA-aligned controls with audit trails.

For regulated teams — healthcare, finance, public sector — that combination means MeetOye can run entirely inside infrastructure you already trust.