No processing agreement for your content
We never see your dictations, emails or receipts. There is technically no route by which they could reach us.
You want GDPR-compliant AI in your office, but you do not want to send client data to a provider in the US? SpeechToWork puts the language model on your own computer. Writing, answering emails, reading receipts, taking meeting minutes: all without an upload.

Most AI tools run on the provider's servers. To use them in line with UK GDPR or EU GDPR, you need a data processing agreement, you have to check sub-processors and server locations, assess international transfers and tell your staff what they may enter. Often the rule at the end is: no personal data. And that removes exactly the work where AI would help most.
Local AI turns this around. If nothing is transferred, there is no processor, no transfer and nothing to redact. The same applies to a GDPR-compliant AI note taker or GDPR-compliant AI transcription.
A language model that is good enough for writing work runs on an ordinary office PC or laptop. In SpeechToWork it takes care of:
A local model does not replace the largest cloud models. It has less general knowledge and is not suited to research or long creative texts. That is why SpeechToWork uses it for tasks where all the information is already in the text: tidying up, rephrasing, summarising, extracting. For this work it is fast, reliable and, above all, confidential.
We never see your dictations, emails or receipts. There is technically no route by which they could reach us.
Content covered by confidentiality duties stays in your firm or practice, because it never leaves the computer.
No billing per request. Use the AI as often as you like; the computing happens on your hardware.
Speech recognition and the language model are installed on your PC and run there. What you dictate ends up in your program and nowhere else. How the data flow works.
Audio and text stay on your computer. There is no server listening in and no AI provider in the background.
No third party processes your dictations. So there is no data processing agreement to sign and no international transfer to assess.
Once installed, SpeechToWork works offline. Only the licence check needs a connection.
Yes. Compliance is simplest with AI that runs locally: if no personal data is transferred to a provider, there is no processor and no international transfer to assess. SpeechToWork works this way. Cloud AI can also be used in a compliant way, but it needs contracts, checks and clear rules on what staff may enter.
You list the activities for which you use the tool, such as correspondence or taking minutes. SpeechToWork is a locally installed aid, like your word processor. There is no recipient or processor for the content. If in doubt, check with your data protection officer or whoever handles data protection in your business.
No, and that is not a matter of a setting: SpeechToWork does not transfer your content to anyone. The language model is downloaded as a file during setup and is not changed afterwards. Your dictations, emails and receipts therefore cannot flow into any training, neither ours nor anyone else's.
On first start, the model files are downloaded. When you start the trial, the app sends your name, email address and a device ID derived from the hardware to our licence service once. In use, the program checks your licence. No dictations, texts, recordings or receipts are transferred. An optional webhook for call notes is set up only by you.
SpeechToWork is about to launch. As soon as the first version is ready, you can download it here: one click, one file, no form.
Coming soonFor Windows 10/11 (64-bit). The download will be available here as soon as it is ready.
One installer for Windows, straight from our server.
A double click is all it takes. No administrator rights needed.
On first start: enter your name and business email, no payment method.
On first start, SpeechToWork downloads the language models once (4 to 6 GB). Already have a licence key? Enter it on first start. What is transferred in the process is explained in our privacy policy.