The trust question

Why private?
Because trust is not a setting.

Every AI notetaker promises privacy. Almost all of them mean a checkbox in the settings, while your conversations keep flowing through someone else's servers. This page explains why we built Bygmind differently: processing on your device instead of promises in the terms of service.

Four events,
one pattern.

2020 Schrems II

The CJEU strikes down US data transfers.

With the Schrems II ruling (C-311/18, July 2020), the Court of Justice of the EU invalidated the Privacy Shield agreement. Ever since, any transfer of personal data to US cloud providers stands on shaky legal ground. Recorded conversations are among the most sensitive data there is.

Since 2025 Consent

Class actions over recordings without consent.

In the US, class actions against AI notetakers are keeping the courts busy. The recurring allegation: cloud services and meeting bots record conversations without the consent of all participants. Whoever uses such services shares that risk.

Ongoing AI training

Training on user conversations, per privacy policy.

Several cloud services reserve the right in their privacy policies to use recordings and transcripts to train their own AI models. Your client conversations become part of another company's product. And the policy can change with any update.

Any time Shutdown

The vendor can pull the plug.

Cloud services get discontinued, acquired, or withdraw from markets, including the EU. When the business model or the legal situation changes, you lose access. Your recordings sit on servers you do not control.

The pattern: as long as conversations sit on third-party servers, your privacy depends on other people's business decisions, lawsuits and privacy policies. No matter how trustworthy the vendor looks today.

Feature toggle vs.
structure.

The feature toggle

"We don't train on your data (if you opt out)." A checkbox, a policy, a promise. All of it can change with the next policy update. The data is still there: on the vendor's servers.

The structural answer

Processing happens on your device. By default, your conversation sits on no server at all, so nothing can be trained on, sold, or leaked there. That is not a promise. It is architecture. And where you do want cloud, say for sync or your own model, that is your active choice.

What "on-device" means
at Bygmind, concretely.

  • Transcription in 25 languages runs on your device, not on our servers. On the free tier, nothing of yours sits with us at all.
  • Speaker recognition and voice ID are computed locally. Voice profiles never leave the device.
  • Summaries work with a local model fully offline. You can verify it in airplane mode.
  • If you want to use a cloud model like Claude or GPT, you do so deliberately, with your own API key and only for the request you make.
  • Sync is opt-in, never required: via the Bygmind Cloud or your own Nextcloud or S3. Without sync there is not even an account.

With this approach, GDPR compliance is not a compliance project but a side effect: data that never leaves your device raises no transfer questions.

See for yourself.
In airplane mode.

Download Bygmind, switch on airplane mode and record. Transcription, speaker ID and summaries still work. That is the whole proof.

Download on App Store