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 transcribes on your own machine instead of sending the recording to a cloud provider. No audio leaves your computer and no third-party processor receives the transcript, which helps you meet data-residency and minimization requirements. Switch transcript sync off to keep the text in place too. LiteScribe is not a GDPR certification, but on-device processing is a strong technical control.

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 to a third party 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. With transcript sync switched off as well, 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, so no processor other than you handles the audio or produces the transcript. 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 stays on your machine without exception, and no third-party transcription or AI processor is involved at any point, so the recording itself is never handed to anyone. The transcript is the part that needs a decision from you: it syncs to your own LiteScribe account by default so you can read it elsewhere, which means a recording whose text must stay on your own equipment needs transcript sync switched off in Settings, Privacy, or that individual transcript locked. The desktop app also reconnects periodically to validate your subscription and downloads the on-device models once, and neither of those carries your content.

Once a transcript has synced it is governed by the privacy policy like any other cloud content, so a compliance review should treat that sync switch as the control that matters. Set it once for the whole machine and every new local recording stays put, or leave sync on for routine material and lock the transcripts that must not move. 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 no third-party processor ever handles the personal data in it.
4
Keep sensitive data local
New transcripts sync to your own account by default. Switch that off in Settings, Privacy, and lock any existing transcript that must not move.

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 is never uploaded and no outside provider ever sees your transcript. 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 audio 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 content. One more thing worth saying plainly: the finished transcript syncs to your own LiteScribe account by default, so you can read it on your other devices. Turn off "Sync new local transcripts to cloud" in Settings, Privacy, or lock an individual transcript, and the text stays here with the audio.

Local Mode Privacy and security Privacy policy

FAQ

Frequently Asked Questions

LiteScribe is not a GDPR certification, and no software can make your organization compliant by itself. What the desktop Local Mode provides is a strong technical control: transcription and AI run on your own machine, so no third-party processor ever receives the personal data in your recordings. Switch transcript sync off as well and nothing but a plan check leaves the computer. That helps you meet data-residency and minimization requirements.

In Local Mode no audio is uploaded, so the recording itself stays on your own machine in your own jurisdiction. The transcript syncs to your LiteScribe account unless you switch that off, so a strict residency requirement means turning transcript sync off too. Then the data residency is simply wherever your computer is, which is the cleanest way to satisfy the requirement.

The web, mobile, and cloud paths use US-based transcription and cloud AI, so for strict EU data-residency needs use the desktop Local Mode instead, which keeps the recording on your machine. The privacy policy describes the cloud path in detail.

Two things, and only one of them is optional. It reconnects periodically to validate your plan and remaining minutes and downloads the on-device models once, and neither carries your content. It also syncs finished transcripts to your own LiteScribe account by default, which you can switch off in Settings, Privacy. Your audio is never sent in Local Mode either way.

On-device processing is part of Local Mode on the Pro and Business plans, in the desktop app for Windows, macOS, and Linux, after a one-time model download.