Translation apps for lawyers: what to check before a client call
November 3, 2026 · Kamban
A public defender on r/publicdefenders admitted something a lot of lawyers think and few say out loud. On attorney-client calls that run through a language line, there is a stranger on the call: "I know they're supposed to keep things confidential and I've heard good ones are trained to 'forget' things they hear. But like...I don't know who that person is, at all. It just stresses me out."
Their preference was an in-house interpreter or a bilingual colleague. Most firms do not have one free on a Tuesday afternoon.
That gap is why lawyers start looking at translation software. This post is about what to check before you point any of it at a privileged conversation. It is not legal advice. Your bar's rules and your engagement letters outrank anything written here.
The interpreter you never vetted
Start with the baseline you are comparing against, because the baseline is not zero risk.
A phone interpreter is a person you did not hire, did not vet, and will never meet, who hears the entire conversation. They are bound by their employer's confidentiality terms. You are relying on a contract between two other parties.
Often that is still the right call. A certified legal interpreter brings judgment that software does not have: register, idiom, the gap between a client's words and a client's meaning, and a professional duty to say so when they cannot render something accurately. For a deposition, a plea colloquy, or anything on the record, that is what you want, and in many proceedings it is what the rules require.
The r/publicdefenders worry is about the other calls. The quick ones. The scheduling call, the "did you get the documents" call, the ten-minute check-in where booking an interpreter costs more effort than the call itself. Those are the calls that go untranslated, or get handled by the client's teenage daughter, which is worse.
Software is a candidate for that middle tier. Which raises the real question.
Cloud AI fails the same test for a different reason
Lawyers have spent two years working out whether client material can go into AI tools, and the answer keeps landing on "depends where it goes."
A lawyer at a 15-attorney firm on r/LawFirm described the deadlock. Their managing partner "is fearful of putting client data into any LLM," believes uploaded case files could end up training public models, and "wants ironclad proof that we aren't violating attorney-client privilege."
The partner is directionally right. Asking a vendor for ironclad proof is the wrong move, because no vendor can supply it. What a vendor can tell you is the architecture, and architecture is checkable.
Two failure modes come up over and over.
Retention. "We do not train on your data" is a different promise from "we do not store your data." Major providers publish retention windows for abuse monitoring that apply even with training turned off. A lawyer on r/legaltech put the consequence plainly: "As lawyers we need to keep our clients information completely confidential. This therefore raises concerns about the possibility of using cloud-based AI tools such as Claude or ChatGPT."
Permissions. A lawyer on r/Lawyertalk found the disqualifying detail without opening a privacy policy. Most of the integrations they wanted "require me to agree to give the app access to 'everything on my computer.' To my mind, that is very obviously not something I can do while still following the rules of confidentiality."
That second instinct is the useful one. The question is not whether a vendor deserves trust. It is how much they are asking you to hand over before the question even comes up.
What on-device means, precisely
On-device is the architectural answer, and the phrase gets used loosely enough to be worth pinning down.
On-device means the processing happens on your own machine's processor. Audio is captured, recognised, translated, and spoken locally. No network request carries the content. There is no server copy, so there is no retention policy to read, no subprocessor list to audit, and no vendor breach that can expose your client's words.
VoiceLeap works this way on macOS 26.2 and later on Apple Silicon, using the speech recognition, translation, and voice synthesis built into macOS. Your audio stays on your Mac.
Here is what on-device does not buy you:
- It does not make a conversation privileged, or restore privilege waived some other way.
- It does not make anything compliant with any framework. Compliance is a property of your practice, not of one app.
- It does not improve accuracy. On-device models are capable and they are not a certified human.
- It does not stop you recording something you should not have recorded.
On-device removes one specific risk: your client's words reaching a third party. That is the risk those Reddit threads are circling, and it is worth removing. It is not the only risk in the room.
Six questions to ask any vendor
Paste these into an email. The answers sort the field quickly.
- Where does the processing run? On my device, or on your servers. If servers, in which jurisdiction.
- What do you retain, and for how long? Audio, transcripts, and metadata are three separate answers.
- Do you train on customer data, and is the default opt-in or opt-out?
- What permissions does the app request? Full disk access and "everything on my computer" are a different category from microphone and system audio.
- Does anything join my meeting? A bot in the participant list is visible to your client, and to opposing counsel.
- What happens when I cancel? If server-side data exists, who deletes it and on what timeline.
Run these against your current language line as well. Question two tends to produce the most interesting answer.
Where VoiceLeap fits, and where it does not
Being direct about this, because a lawyer audience will find the gap anyway.
VoiceLeap translates live audio on a Mac in both directions. Listen mode translates what you hear. Speak mode translates what you say and routes it into Zoom, Google Meet, or Teams through a virtual microphone. Conversation mode runs both at once. In Listen mode you can also pick Subtitles only, which keeps the client's own voice playing and puts the translation on screen, so you hear how something was said and read what it meant. It covers 10 languages and 30+ regional locales, and costs $29 a year or $49 once.
It fits the middle tier: the client check-in, the intake call, the document question, the call that otherwise does not happen in the client's language at all.
It does not fit these:
- Court, and anything on the record. Use a certified interpreter. This is not a substitute and should not be offered to a tribunal as one.
- Sworn testimony, depositions, plea discussions. Same answer.
- Any proceeding whose rules specify a qualified interpreter. The rule decides, not the tool.
- Anything where accuracy has to be attestable. Software cannot take the stand and certify its own output.
Quality also varies by language pair, because the models are Apple's. Test your pair before you lean on it.
The consent question is separate
One more point, independent of which tool you pick.
Translating a live conversation is not the same as recording it. If you do record, consent law applies. Most US states permit recording with one party's consent. Roughly a dozen require every party to agree, and one participant sitting in such a state can pull the whole call under the stricter rule. Outside the US, several countries treat unconsented recording as a criminal matter.
You know this better than a software blog does. It belongs here because some tools record by default and some do not, and that difference should sit on the checklist above rather than surface afterwards.
Run the six questions first
Take the list in this post and send it to whatever you use now, your current interpreting vendor included. Those answers will tell you more than any comparison page.
If an on-device translator looks like a fit for the middle tier of calls, download VoiceLeap and run the 7-day trial on a call that is not privileged, so you can judge the quality before it counts. Every feature is unlocked and it does not ask for a card.
Frequently asked questions
Can lawyers use AI translation tools without waiving privilege?
This is not legal advice and your bar's rules decide. The checkable part is architecture: where the processing runs, what is retained, whether the vendor trains on your data, and what permissions the app requests. A tool that processes on your own machine never transmits the conversation to a third party.
Is an on-device translation app safer than a cloud one?
On-device removes one specific risk, your client's words reaching a third party, because there is no server copy and no retention policy to audit. It does not make a conversation privileged and it does not make your practice compliant with any framework.
Does VoiceLeap replace a certified legal interpreter?
No. A certified interpreter brings judgment on register and meaning plus a professional duty to flag what they cannot render accurately. VoiceLeap fits quick calls such as check-ins and intake, not proceedings that need a qualified interpreter.
Can I use a translation app in court?
No. For court, depositions, sworn testimony, or anything on the record, use a certified interpreter. Where rules specify a qualified interpreter, the rule decides and software is not a substitute.
What should I ask a translation vendor about confidentiality?
Where the processing runs and in which jurisdiction, what they retain and for how long across audio and transcripts and metadata, whether training is opt-in or opt-out, what permissions the app requests, whether anything joins your meeting, and who deletes server-side data when you cancel.