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

• Encrypted transport for standard meetings, with strict E2EE wording reserved for meetings where that mode is enabled.
• Private deployment is planned for teams that need more control over media and meeting data.
• SSO, SCIM and granular host controls.
• Transcripts visible only to attendees, never shared with third parties.
• Security controls are designed for auditability; formal compliance certifications should only be claimed when completed.

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