The questions we get asked before a yes.
Short, true answers. If yours isn't here, write to us: it will join the list.
Do I need to install an app?
No. The participant scans a QR code (or types the session code) and the page opens in their phone's browser. Nothing to download.
Do I need an account to listen?
No. No account, no name, no email. Only the organizer has an account.
Which phones work?
Any recent smartphone with an up-to-date browser: Safari on iPhone, Chrome on Android, and the other common browsers. Earphones are needed, wired or Bluetooth, the ones everyone already owns.
Can I switch channel during the session?
Yes, at any time, with one tap. The switch happens on the connection already open: the cut is imperceptible.
What network is needed in the room?
A decent Wi-Fi or a mobile connection. Count about 30 MB of data per hour per participant (compressed voice, with loss protection). We help you check the network before the event.
What is the delay between the voice and the ear?
The stream is continuous and live (WebRTC), not segment-based playback. Mouth-to-ear latency in a real room has not been measured yet with real phones: we publish no figure before doing so.
What happens if the network drops?
The phone reconnects by itself as soon as the network is back, and the page says in plain words what is happening (“connecting”, “sound lost”, “session ended”). The speaker also sees whether their voice is getting through.
How many channels and participants?
Today: 5 channels per session, 30 participants per channel, 155 simultaneous participants per session. These ceilings are enforced by the server and evolve with the pilots. Several rooms = several sessions.
How long does a session last?
Four hours from the start, extendable with one tap up to eight hours. The session then ends by itself: nothing stays open by oversight.
Who speaks on a channel?
The speakers: interpreters, commentators, guides, presenters. Each receives a personal link for their channel, revocable at any moment. Several speakers can be authorized on a channel; one voice goes through at a time.
Are exchanges encrypted?
Yes: HTTPS for pages and the API, encrypted WebRTC for the audio. The session code is random and unguessable; it only grants the right to listen.
What data is collected?
To listen: no personal data. The end-of-session survey is anonymous. Leaving an email to stay informed is optional, behind a consent box unticked by default, with unsubscription at any time; these addresses are kept for at most one year.
Does Sasa replace interpreters or a booth?
No. Sasa carries your interpreters' voices to the phones; it does not translate. It replaces receiver distribution, not an ISO booth where regulations require one, and it brings interpretation where it did not exist.
How much does it cost?
During the pilot phase, it is free and supported. The upcoming model is based on duration, channels and participants, with no imposed subscription. No price is published before it is real.
How do I start?
Request a demo: thirty minutes online, with your own phones. If Sasa fits, LOBAKA opens a pilot organizer account, with its limits stated, and supports you through your first event.
Can I create a session myself?
Not freely yet: during the pilot phase, sessions are created on request, with an account opened by LOBAKA. Self-service will come with the pricing model.
A question that isn't here?
Ask us, or see Sasa working in thirty minutes with your own phones.