Desktop Local Mode on Windows, macOS, and Linux

Transcription, GDPR, and EU Data Residency

Keep recordings on your own machine to support data-residency and GDPR requirements. The LiteScribe desktop Local Mode transcribes on-device, so no audio leaves your computer.

For GDPR and EU data-residency needs, the LiteScribe desktop Local Mode keeps your audio and transcript on your own machine instead of sending them to a cloud provider. Because no audio leaves your computer in Local Mode, it helps you meet data-residency and minimization requirements. LiteScribe is not a GDPR certification, but on-device processing is a strong technical control. Available on Windows, macOS, and Linux.

Get the desktop app See Pricing

Why data residency is hard for cloud transcription

Under GDPR and similar regimes, where personal data is processed and stored is a real constraint, not a preference. Standard cloud transcription is awkward here, because the audio of a meeting almost always contains personal data, and uploading it to a transcription service plus an AI provider means that personal data is processed by third parties, often outside the EU. The LiteScribe web and mobile apps use US-based transcription and cloud AI, so they sit on the cloud side of this question.

The cleanest answer to a data-residency requirement is for the personal data not to travel at all. That is what the desktop Local Mode provides. The recording is transcribed on your own machine, the AI runs on your own machine, and the audio is not uploaded. The data residency becomes simply wherever your computer is, which is the strongest form of the control you can offer a privacy or compliance reviewer.

How Local Mode supports GDPR principles

Local Mode maps neatly onto several GDPR principles without anyone having to take a vendor promise on faith. Data minimization is satisfied because no audio is transmitted to a processor. Storage limitation is in your hands because the recording lives on your disk and you control deletion. Purpose limitation is clear because there is no third-party AI receiving the transcript to use for anything else. And for the lawful-basis and records work that compliance teams do, fewer processors means a simpler record of processing activities.

It is important to be exact about what this is and is not. LiteScribe does not claim to be GDPR certified or formally compliant on your behalf, and no software can be, because compliance depends on how your organization uses it. What Local Mode gives you is a strong technical measure: on-device processing that keeps personal data on the data controller own equipment. That is the kind of measure GDPR encourages, framed honestly as a capability rather than a certificate.

The honest boundary on residency

To keep this trustworthy, here is the precise line. In Local Mode your audio and transcript stay on your machine, so the personal data in your recordings does not leave your jurisdiction through LiteScribe. The desktop app does still reconnect to our server periodically to validate your subscription and remaining minutes, and the on-device models are downloaded once. Those account interactions do not transmit your audio or your transcript, so they do not move the personal data in your recordings.

If you choose to sync a recording to the cloud for cross-device access, that recording then follows the normal cloud path and its processing is governed by the privacy policy. The point of Local Mode is that this is an opt-in per recording, so you can keep anything that must stay in-region fully on-device while still using the cloud for routine material. Read the privacy policy for the full detail on what the cloud path involves.

Why use LiteScribe Local Mode

No audio leaves your machine

In Local Mode the recording is transcribed on-device, so the personal data in it does not travel to a third-party processor.

Supports data minimization

On-device processing means no audio is transmitted, which helps satisfy GDPR data-minimization expectations.

Fewer processors to document

Keeping transcription and AI local reduces the third parties in your record of processing activities.

Capability, not a certificate

LiteScribe is not GDPR certified, but on-device processing is a strong technical control you can point to honestly.

Transcription, GDPR, and EU Data Residency

1
Install the desktop app
On-device processing for data residency is the desktop Local Mode on Pro and Business. Download LiteScribe for Windows, macOS, or Linux.
2
Enable Local Mode
Turn on Local Mode and download the on-device models once. After that, transcription and AI keep your recordings on your machine.
3
Record in-region
Record or import the recording. It is transcribed and summarized on your own hardware, so the personal data in it stays local.
4
Keep sensitive data local
Leave a recording set to local so it never syncs out of region, and opt only routine material into the cloud when residency is not a concern.

What is private, and what is honest

Privacy on this page means the desktop Local Mode, where your audio is transcribed on your own CPU or GPU and an on-device AI model writes your notes, so your recording and its transcript stay on your machine. The web app, the mobile app, and the cloud path are different: they use a cloud transcription service and cloud AI, so they are not private in this sense. Local Mode is a desktop feature on the Pro and Business plans, available for Windows, macOS, and Linux after a one-time model download.

We will not call the app air-gapped, because it is not. Your content stays on your device, but the desktop app reconnects to LiteScribe periodically to validate your plan and remaining minutes, and it pauses new offline work if it cannot check in for about two days. That account check carries none of your audio or transcript. You also choose, per recording, whether to keep it local or sync it to the cloud for access on your other devices.

Local Mode Privacy and security Privacy policy

FAQ