The questions you were going to ask anyway
Written down before the first conversation rather than after the third, so your security and procurement people can start reading now instead of waiting on us. Every answer here is either already true on this site or already true in the product — where something is not settled, it says so.
How accurate is it, and how do you know?
We publish the number and the method: 46 of 47 checks correct on a corpus of 13 deliberately difficult synthetic calls — 1 wrong fact, 0 missed facts, 21 correct refusals, last run 11 August 2026.
The one wrong fact is described in full on the accuracy page, along with the whole method and a complete messy call beside Talqo's unedited output. The answer sheets were written before the run and are not edited to match results, and the benchmark runs the product rather than a model. If the number moves, the page moves.
The design bias is deliberate and testable: Talqo prefers to be wrongly cautious over wrongly confident. Across that corpus it never once over-claimed a price acceptance.
What do you keep, and for how long?
Transcripts are not kept. A call is analysed and the transcript is discarded — it is not stored as a record. A transcript waiting in the queue is auto-purged within 30 days if it is never processed.
What is stored is the structured output: the summary, the qualification scores, the action items, the deal facts and the quotes that evidence them. That is the product — it is what you are paying to keep — and it is deletable on request, per call or per person.
Our AI subprocessor retains API content for up to 30 days (longer only if flagged for trust & safety review) and never uses it for training.
Who else touches the data?
Four subprocessors, listed in full with roles, locations and transfer mechanisms on the subprocessors page:
- Render — application hosting, database and disk. EU (Frankfurt). No transfer.
- Anthropic — AI processing of transcripts, under a DPA and EU Standard Contractual Clauses. US. This is the one transfer outside the EEA.
- Azure OpenAI — alternative AI processing, opt-in per company and off by default. The deployment is your own Azure resource, so the region is under your control; we transmit from EU infrastructure and receipt the endpoint on every call.
- Resend — transactional email only (password resets, replies). Name and email address only, never transcript or analysis content.
Can we get our data out?
Yes, without asking us. Any user can export their own record from My profile — account details plus their calls with summaries, scores, action items, next steps, concerns and their own coaching, as JSON. An admin can export any user in their company for an Article 15 request, which additionally includes deals, cadences, coaching snapshots and deleted calls.
The one thing an export deliberately excludes is a manager's private coaching notes about someone else. That is a deliberate boundary, and we would rather say so than let "everything" quietly mean "everything except the bit we did not mention".
Can we get it deleted?
Yes, at three levels. A single call can be removed from the product. A person can be erased for an Article 17 request — that reaches their calls including ones already soft-deleted, which we fixed after an erasure walk found the gap rather than after a customer did. And a third party named in a call — someone who never used Talqo and never agreed to anything — can be redacted by name across the stored analysis.
Erasure has a dry run that changes nothing, so you can see the blast radius before you commit.
What happens if we want to stop?
Your notice period and term are whatever your signed pilot or subscription agreement says, and we will state them plainly in writing before you sign anything — we are not going to summarise a contract you have not read on a marketing page.
What we will commit to here: no per-call fees and no usage meters, so leaving is not made expensive by making staying cheap; seats belong to the company, not to a named person; and renew on time and your price is locked. Export works without our involvement, so getting your data out is not a thing you have to negotiate on your way out of the door.
Who owns what?
You own your data. We own the platform. We process your data solely to provide the service to you. We do not sell it, we do not use it to train models, and we do not use one customer's calls to improve what another customer sees.
The analysis produced from your calls is your data too — it is a description of your conversations. You can export it at any time from inside the product.
What happens to our data — and our contract — if Talqo stops operating?
The honest framing first: we are a young company, and this is a real risk you are right to price in. Nothing below is a guarantee dressed up as one, because a guarantee from a company that has ceased to exist is worth nothing — which is exactly why the answer has to be about what you can do without us.
Your data is exportable today, by you, without asking. That is the part that actually protects you, and it is the part you should test early rather than take on trust: any user can export their own record from My profile, and an admin can export any user in the company. Export does not depend on our goodwill, our availability, or a support ticket. If you want a standing copy, take one on a schedule — we would rather you did.
What is stored is deliberately portable. The output is structured data — summaries, scores, action items, deal facts and the quotes evidencing them — as JSON, not a proprietary artefact that only means something inside Talqo. What Talqo adds is the reading, and the reading is written down in a form you keep.
What we will commit to, in writing, in the agreement: a defined notice period before service ends, and a data-export window inside it. If we wind down deliberately, you get notice and a window to take everything out. Ask for both to be written into your contract — and if a vendor will not put that in writing, that is worth knowing about any vendor, including us.
What we cannot promise, and will not pretend to: that an abrupt failure — insolvency, a founder under a bus — comes with an orderly wind-down. No small vendor can promise that honestly. There is no escrow arrangement today and we are not going to imply one exists. The mitigations that are real are the ones above: export early, export often, and hold a copy you control. Talqo also does not hold your transcripts at all, so the worst case is the loss of an analysis layer over conversations you still own — not the loss of the record itself.
What don't you have?
No SOC 2 and no ISO 27001. We are a young company and certification is a roadmap item, not a claim. The security page has a "what we have not built yet" section that stays current, because the fastest way to lose a security reviewer is to have them find the gap themselves.
If a certification is a hard requirement for you today, we would rather tell you now than six weeks into a procurement process.