Privacy
Yazyk runs the audio pipeline on the computer in your sound booth. The audio reaches the speech services that recognize and speak it. If you switch on Internet listeners for a service, the translation also goes out through a relay Yazyk runs, so phones off your network can hear it. We keep no copy of any of it.
Yazyk runs on your computer and talks to the speech vendors from there. If you switch on Internet listeners, it also sends the finished translation to a relay that reaches phones off your network. The recordings it writes stay on that machine, and we hold account and usage information rather than copies of your events.
On your machine
Capture, playback, the run log, and the audio path to the transmitter, to the captions, and to phones on your own network all run on your own computer. Internet listeners are the exception, and the next card says who carries that audio.
Off your machine
Recognition and synthesis are performed by third-party speech services, so the audio is sent to them while the event runs. With Internet listeners switched on, the finished translation also goes out through a relay Yazyk runs on Cloudflare Realtime, which passes it to each phone off your network.
Not kept
We hold no archive of your audio or its translation. The relay behind Internet listeners is ours, and we ask it to pass audio on to the phones, not to record it: no recording of your event comes back to us from it.
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. No copy of it is kept on our systems.
Internet listeners add one more stop, and only if you switch that option on for a service. The finished translation is then sent to a relay we run — a Cloudflare Realtime application on our own Cloudflare account — and the relay passes it live to each phone that opens the link and starts listening. A relay of that kind can hear the translation while it passes it on, which is why we name it here instead of calling the path local. We ask it to send that audio on, not to record it, and no recording of it comes back to us. What goes out is the translation your listeners hear, not the speech from your sound desk.
There are a limited number of places, and each phone that joins takes one, so that no single network address can take them all and shut the rest of your listeners out. For that we store, against your service, when a phone joined, when it last checked in, when its place was given up, how much audio it told us it had received, and a scrambled fingerprint of its network address — a one-way hash, not the address itself, which we keep no copy of. A phone that simply walks away is noticed when its place is reclaimed rather than at the moment it goes, so those last two are rough. Nothing about who the listener is, and nothing about what they heard.
With Internet listeners off, the audio goes no further than your own computer, the speech services, and the devices on your own network: the transmitter, the captions, and phones on your Wi-Fi.
A run does leave files behind, and they are worth knowing about. Into a Transcripts folder on the same computer, named by the date and time of the service, it writes a transcript — what was recognized in the original language and the translation made from it — and, if you switch recording on, a recording of the translated audio it produced. Recording is off until somebody turns it on in the operator console, including on a computer that has been running Yazyk since before that switch existed. Whatever it writes is deleted automatically after 90 days, and the operator console has a control that lists what is on disk and deletes it sooner. It also writes a run log, and, when cloning is used, the short reference clip taken for that voice; those stay on the machine under your control, and you can delete them like any other file. None of it is sent to us.
Recordings made by a version of Yazyk before this one were written to the Logs folder instead, and nothing deletes those. They are yours and they stay where they are until you remove them. If you have been running Yazyk for a while, that folder is worth looking in once.
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.
While an event runs, the software asks us to renew its permission to translate, roughly every forty-five minutes. That request carries a session identifier and, for each language you are translating into, the number of milliseconds of speech we have synthesized in it. That is the measurement your usage and your bill are computed from, so it reaches us by design. The same figures are sent once more when the session ends, which is how a service shorter than one renewal is counted at all. If that last request cannot reach us — the network is down at the moment the run ends — it is not retried, and the usage it carried is not billed.
What that request does not carry: the content of what was said, in any language, at any point. Nor the coverage, delay or interruption figures — those stay on your receipt. The only other thing we learn is the ordinary fact that your computer contacted us. This paragraph changes when the behaviour changes.
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. That one recording is handed to the vendor through a Yazyk server, because only that server holds the key the vendor's voice service asks for; it passes straight through on its way, and we do not keep it. 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.
We hold what is needed to run an account and talk to you: name, organization, email address, licensing status, and correspondence you send us.
A computer you have paired also reports a few things about itself, so that your church’s list of audio sources says which machine is which and so a support call can find it. Those are its computer name, its operating system and version, the version of Yazyk on it, and a hardware identifier the operating system already keeps — the installation identifier on Windows, the platform identifier on macOS. The identifier is collected so that a computer can be recognised as the same computer after Yazyk is re-installed on it. It is sent when you pair the computer and when it starts a service, it is held on that computer’s row on your own account, and it goes nowhere else.
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.
This site sets no cookies, loads no analytics, no third-party fonts, and no resources from another host. Every page except Home is a single request. Home adds one small animation file served by this same site.
It runs four small inline scripts on every page, and a fifth on the pricing calculator. Two set and switch your light or dark preference under the name yazyk-theme; that value never leaves your device, and clearing browser storage removes it. If you never touch the switch, nothing is stored and the site follows your system setting. One script opens the mobile navigation, and one fades sections in as you scroll. The fifth adds up the plan the calculator shows you, from figures already built into that page; it stores nothing and asks us nothing. The homepage also loads one small animation file from this same site to illustrate speech moving through translation to listeners. Those presentation effects store nothing, send nothing, pause when their panel or the page is not visible, and switch 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. Your four typed fields are also copied into a notification email to [email protected], a Google-hosted group owned by Yazyk; the browser string and network fingerprint are not included in that email.
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. The site, database, and notification sender run on Cloudflare, and the destination mailbox runs on Google, so those companies process the submitted fields as our hosting and mail providers. Ask at the address below and we will delete them.
The operator console has a separate feedback form. It sends the category and message you enter, an email address only when you ask for a follow-up, and the bounded technical-log tail only when you check Include my technical logs. Before sending, credentials, selected device names, local paths, and network addresses are removed. The submission is stored with the time, the console browser string, and the same one-way network fingerprint described above so one person cannot flood the form; the network address itself is not kept. It sends no audio, transcript text, or complete log file.
Email you send us directly is kept only to answer you.
Write to [email protected] to ask what we hold about you, to correct it, or to have it deleted. Deletion of a voice reference, a local run log, or a transcript is something you can also do on your own machine, because that is where those files live; the operator console also has a button that deletes a transcript for you.
If this page changes, the date at the top changes with it.