End-to-End Encryption (E2EE) - iOS

Overview

End-to-end encryption (E2EE) ensures that your media content remains private and secure by encrypting it on the sender's device and decrypting it only on the receiver's device. This prevents intermediaries, including VideoSDK servers, from accessing or modifying the content.

E2EE is particularly important for applications in security-critical domains such as telehealth, finance, and legal services.

How E2EE Works

• E2EE is applied at the room level, where a single shared key encrypts and decrypts all media tracks during a session.
• Participants without the key cannot access the media.
• The entire encryption process is handled client-side. VideoSDK does not access or store any encryption keys.

Key Management & Distribution

You are fully responsible for generating, managing, and securely distributing encryption keys to all participants. VideoSDK never stores, accesses, or transfers your encryption keys.

• Common Key Distribution Approaches:
  • Generate the key on your server when creating a meeting.
  • Send the key securely along with the meeting access token.
  • Use HTTPS-secured API calls to fetch the key on the client.

important

⚠️ Ensure that all participants have access to the correct encryption key before joining the room.

The table below shows the minimum SDK versions that support E2EE. All subsequent versions also include E2EE support.

iOS	React	React Native	Flutter	Android	JavaScript
2.2.2	Coming Soon	Coming Soon	2.1.0	Coming Soon	Coming Soon

Enabling E2EE in VideoSDK iOS

To enable E2EE in VideoSDK for iOS, follow these steps:

  private func initializeMeeting(cameraPosition: AVCaptureDevice.Position? = .front, customVideoStream: CustomRTCMediaStream? = nil, customAudioStream: CustomRTCMediaStream? = nil) {
        // initialize
        meeting = VideoSDK.initMeeting(
            meetingId: meetingData.meetingId,
            participantName: meetingData.name,
            micEnabled: meetingData.micEnabled,
            webcamEnabled: meetingData.cameraEnabled,
            customCameraVideoStream: customVideoStream,
            customAudioTrack: customAudioStream,
        )
        // listener
        meeting?.addEventListener(self)
        // keySetup() for enabling E2EE
        keySetup()
        // join
        meeting?.join()
    }

    func keySetup() async {
        do {
            let customKeyProvider = try await BaseKeyProvider()
            try await customKeyProvider.setSharedKey("<Your Encryption Key>")
            VideoSDK.setKeyProvider(customKeyProvider)
        } catch {
            print("Error setting encryption keys: \(error.localizedDescription)")
        }
    }

Additional Configuration Options

You can customize the encryption behavior by passing parameters while creating the BaseKeyProvider instance:

Parameter	Type	Description
discardFrameWhenCryptorNotReady	bool	If true, frames will be discarded when the cryptor is not ready, ensuring no unencrypted content is sent.

warning

Make sure to set the encryption key using setSharedKey before assigning the key provider with setKeyProvider, otherwise it will throw an error.

Event for E2EE State Changes

To monitor encryption state changes for each participant's media stream:

func e2eeStateChanged(forParticipant participant: Participant, state: E2EEState, _ stream: MediaStream) {
    print("Participant: \(participant.displayName)")
    print("E2EE State: \(state)")
    print("Media Stream Kind: \(stream.kind)")
}

The possible values for state are:

State	Description
EncryptionSuccess	Media encryption is successfully applied.
DecryptionSuccess	Incoming media is successfully decrypted.
EncryptionFailed	Encryption encountered an error.
DecryptionFailed	Decryption encountered an error.
InternalError	Internal processing error occurred.

To Check Whether E2EE enable not

You can check whether E2EE is enabled by using e2eeEnabled property of Meeting class.

let isE2EEEnabled = meeting.e2eeEnabled
print("Is E2EE Enabled: \(isE2EEEnabled)")

Limitations

E2EE only applies to media. It does not apply to:

• Chat messages or metadata
• API calls and signaling data

These communications are still protected by TLS but are not encrypted end-to-end.

info

Recording and transcription features are not supported when End-to-End Encryption (E2EE) is enabled.