Legal
What we hold, why we hold it, how long for, and how to get it deleted.
This page has not been reviewed by a lawyer
It is an engineering description of how the platform handles your data, written so that it is accurate about the system rather than complete as an agreement. It is not a contract, nothing on it is a legal commitment, and where a real agreement would make a promise — about liability, refunds, warranties or how long we keep anything after you leave — this page deliberately says nothing instead of guessing. Reviewed text replaces it before WeTalk is generally available.
Recordings and transcripts of conversations with your agents, the caller's number, anything the caller tells the agent, and the documents you upload. We do not sell any of it and we do not use your recordings to train models for anyone else.
You choose, per workspace. The defaults are thirty days for recordings, twelve months for transcripts, twelve months for orders and survey results, and twenty-four months for the audit log. Caller details can be deleted with the conversation or kept so that regulars are recognised; when they expire we remove the number and keep only a hash, so your totals survive without the number surviving with them.
Search by number or email and export or delete everything tied to it. Deletion removes recordings, transcripts, orders and answers within twenty-four hours and is written to your audit log.
In one place, and we would rather name it than imply a choice you do not have. Your recordings, transcripts, documents and order history are stored and processed in Microsoft Azure's Italy North region, inside the European Union. There is no region picker at signup, because there is one region. Some of the work a conversation needs — carrying the call, turning speech into text and back again, taking a card payment, reading an uploaded document — is done by the sub-processors listed below, and each of them is named with what it sees. If either the region or that list changes, we will say so here before it changes, not after.
The full sub-processor inventory is below: who they are, what they do for us and what they receive. It is a complete list, not a sample.
One region, named rather than chosen: everything WeTalk stores is in Microsoft Azure's Italy North region, inside the European Union. There is no region picker at signup, because there is one region. The companies below do the parts of a conversation we do not do ourselves. This is the complete list, not a selection from it.
What they do · Hosts the whole platform — the application, the database, the stored recordings and documents, and the GPUs the conversation model runs on.
What they receive · Everything WeTalk stores: recordings, transcripts, uploaded documents, order and survey data, and account details. All of it in the Italy North region.
What they do · Carries phone calls — inbound numbers, outbound dialling and the SIP trunk your own provider points at.
What they receive · The phone numbers on both ends of a call, and the call audio while it is in flight.
What they do · The second carrier, so that outbound calls are not dependent on one supplier.
What they receive · The phone numbers on both ends of a call it carries, and the call audio while it is in flight.
What they do · Turns speech into text as the caller talks, and is the default voice that speaks the agent's side.
What they receive · Conversation audio, and the words the agent says. Also the recognition vocabulary drawn from your documents — menu item names, for example — which is what makes it hear them correctly.
What they do · An alternative voice, used only for the languages where a customer or we choose it over the default.
What they receive · The words the agent is about to say, for the languages it is enabled on.
What they do · Takes card payments for credit, on their own hosted form.
What they receive · Your billing details and the card entry itself, which happens on their page rather than ours. WeTalk never sees a card number — only the last four digits and a token.
What they do · Reads the documents you upload and turns them into the structured menu or question set your agent answers from. It also runs the deeper of the two optimisation passes — the one that listens to the recordings rather than only reading the transcripts, so it can hear a pause, an interruption or a mispronounced price.
What they receive · The documents you upload. Conversation audio as well, but only for the deeper optimisation pass and only on the conversations you ask it to examine — never as part of answering a call.
Questions about your data?
privacy@wetalk.io reaches a person, not a queue.