TB Meet, powered by Jitsi, supports End-to-End Encryption (E2EE) to help ensure that only meeting participants have access to the content of the conversation — not even the server can access decrypted audio or video. This feature reflects our commitment to secure, private communication between practitioners and clients.


While E2EE is available in TB Meet, it is currently in an experimental phase, and functionality depends on the browser and device being used.


Understanding Encryption in TB Meet

When you start a video call in TB Meet, your audio and video streams are automatically encrypted between your browser and the TB Meet servers. This protects your call from eavesdropping while the data is in transit—no extra action is needed from you.

What is E2EE in TB Meet?

End-to-End Encryption (E2EE) means your meeting content is encrypted on the sender’s device and decrypted only on the recipient’s device. This prevents intermediaries — including the server — from accessing audio or video streams.

Why does E2EE show as an “Experimental”?

E2EE is marked as "experimental" because TB Meet (via Jitsi) is currently rolling it out with limitations. While functional on supported platforms, it may not work consistently across all devices or browsers due to current web technology constraints.

Which browsers and devices support E2EE?

Supported:

  • Latest versions of desktop browsers, including:

    • Google Chrome

    • Microsoft Edge

    • Other Chromium-based browsers

Not supported:

  • Mobile browsers (e.g., Safari or Edge on iPad/iPhone)

  • Devices or browsers that do not support insertable streams, which are required for E2EE

What happens if someone joins from an unsupported browser or device?

If E2EE is enabled and a participant is using an unsupported browser, they may not be able to see or hear other participants in the meeting.

How do I know if a participant’s setup doesn’t support E2EE?

TB Meet will display a warning under the Security Options if someone in the meeting does not support E2EE. You may see a message like:


This helps you make informed decisions about enabling or disabling E2EE.


Best Practices for Using E2EE in TB Meet

  • ✅ Enable E2EE only when all participants are on supported desktop browsers

  • ❌ Disable E2EE if any participant is on a mobile device or unsupported browser

Additional Meeting Access Controls in TB Meet

To further protect your meetings:

  • Only participants who are added to the event in Therabyte can join the meeting.

  • Even if the meeting link is shared externally, unlisted users will be required to log in to their client portal to access the session.

  • TB Meet also includes a Lobby feature, allowing practitioners to approve or reject participants requesting access to the meeting.


These layers of protection work alongside E2EE to maintain a secure and controlled virtual meeting environment.