On your machine
The program is local
Capture, playback, the run log, and the audio path to the transmitter, the phones, or the captions all run on your own computer.
Privacy
Where your audio actually goes.
Yazyk runs the audio pipeline on the computer in your sound booth. The audio reaches the speech services that recognize and speak it, and it does not pass through a Yazyk server.
Local pipeline, vendor calls, files that stay with you.
Yazyk runs on your computer and talks to the speech vendors from there. The recordings it writes stay on that machine, and we hold account and usage information rather than copies of your events.
To the vendors
Speech services see the speech
Recognition and synthesis are performed by third-party speech services, so the audio is sent to them while the event runs.
Not to us
We keep no copy of your events
Your audio and its translation do not pass through a Yazyk server, and we hold no archive of either.
1. Audio during an event
Speech from your sound desk is captured on the computer in your booth. To be recognized and spoken in another language it is sent to third-party speech services, which is how live translation works at all. It is not routed through a Yazyk server, and no copy of it is kept on our systems.
2. The files Yazyk writes on your machine
A run does leave files behind, and they are worth knowing about. It writes a run log, a recording of the translated audio it produced, and, when cloning is used, the short reference clip taken for that voice. All three sit on your own computer, under your control, and you can delete them like any other file. We are not sent copies.
3. The receipt and what reaches us
The event receipt is generated from the run log and carries measurements: event length, translated speech, coverage, listener delay, and the time and duration of each interruption. That full receipt stays with you.
Today the software reports nothing back to us at all. The usage channel is built on our side but is not yet connected on yours: no running event sends us a report, so the only record of what happened is the one on your own machine. When it is connected, and it will be before anyone is charged, what it sends is a session identifier, the language tags in use, and how many milliseconds of translated audio were produced for each. Not the content of what was said, and not the coverage, delay or interruption figures, which stay on your receipt. This paragraph changes when the behaviour changes.
4. Voice references
If you use the speaker's own voice, a short reference recording is used to create a voice at the speech vendor for that event. When a run shuts down cleanly the software deletes that vendor side voice; a crash, a lost network, a slow vendor response at shutdown, or a vendor error can leave it behind, which is why the operating runbook also carries a manual cleanup step. We do not build a library of voices, and we do not use your audio or voice references to train models.
5. Account information
We hold what is needed to run an account and talk to you: name, organization, email address, licensing status, and correspondence you send us.
6. Telling the room
The people in your building are the ones whose speech is processed. Telling them that an event is machine translated, and that speech is processed by third-party services, is your responsibility as the organization running it.
7. This website
This site sets no cookies, loads no analytics, no third-party fonts, and no external resources of any kind. Every page is still a single request.
It runs three small scripts, all written inline in the page, and between them they do two things. The first is the colour scheme: whether you chose light or dark is kept in your own browser under the name yazyk-theme, it never leaves your device, and it is not sent to us. Clearing your browser storage removes it. If you never touch the switch, nothing is stored at all and the site follows the setting your system already has. The second is presentation only: a section fades in as you scroll to it. That one stores nothing, sends nothing, and switches itself off if you have asked your system for reduced motion.
Like any website it is served by a hosting provider, which keeps its own ordinary request logs.
The contact form is the one place this site collects anything. Submitting it posts to our own server on this same domain, and what you typed is stored in our own database so a person can read it and reply: your name, your email address, your organization, and your message, with the time you sent it and the browser string your browser volunteered. One more thing is stored that you did not type: a scrambled fingerprint of your network address, which exists only so that one person cannot flood the form, and which is a one-way hash rather than the address itself. We keep no IP address for this site. It is not sold, and it reaches no advertising or analytics service, because there are none on this site. It is not, however, kept nowhere but here: this site and that database run on Cloudflare, so Cloudflare processes it as our hosting provider in the same way it already serves you this page. Ask at the address below and we will delete it.
Email you send us directly is kept only to answer you.
8. Your requests
Write to hello@yazyk.ai to ask what we hold about you, to correct it, or to have it deleted. Deletion of a voice reference or a local run log is something you can also do on your own machine, because that is where those files live.
9. Changes
If this page changes, the date at the top changes with it.