Communications

Loookit is browser based and all communications use HTTPS and WSS protocols and as a WebRTC based service, it encrypts all media exchanges by default.

The browser-based implementation with its sand-box limits access to the local resources of the user’s computer. Access to the Microphone, Camera, and Screen are available only after the appropriate participants give appropriate Permission Requests/Grants.

Loookit’s  WebRTC mandates a Permission Request model for Multimedia interactions. So the Agent has to ask for permission before using any Audio/Video/Screen share/Snapshot feature.  And it requires each participant to grant permission before the media exchange starts.

Loookit enforces security policies like closing all unused ports, disabling ping and so on.

Ephemeral Content

Loookit is browser based and all communications use HTTPS and WSS protocols and as a WebRTC based service, it encrypts all media exchanges by default.

The browser-based implementation with its sand-box limits access to the local resources of the user’s computer. Access to the Microphone, Camera, and Screen are available only after the appropriate participants give appropriate Permission Requests/Grants.

Loookit’s  WebRTC mandates a Permission Request model for Multimedia interactions. So the Agent has to ask for permission before using any Audio/Video/Screen share/Snapshot feature.  And it requires each participant to grant permission before the media exchange starts.

Loookit enforces security policies like closing all unused ports, disabling ping and so on.

Session Access

Loookit offers SSO as well as Password based user authentication schemes.

Session IDs, Passcodes & QR Codes

Loookit offers password protection through a combination of encryption and practices such as requiring passwords to be of a minimum length, a mix of upper- and lower-case characters, special characters. Loookit, also, does not support permanent conference rooms. Sessions can only be setup by the host at the time of use and unique session ID’s that are valid only for the session are used. The host can track each participant as they arrive and end session if unknown participants join.

Similarly, session passcodes are unique and issued only on demand.

QR Codes, can only be used by customers to request sessions but do not give access to an ongoing session.