Skip to content
Trust & security

A plain-language tour of what happens to your audio, where your data lives, and what you can do with it. Privacy here is architecture, not a setting.

EU-hosted · no audio stored · no bot

01

Captured on your machine

MeetSmara reads your system audio and microphone locally. No bot joins the call, and nothing about your meeting is visible to other participants.

02

Transcribed live, then discarded

Audio streams to an EU speech endpoint, comes back as text in real time, and is discarded. It is never stored — not on our servers, not on your disk.

03

Text stays local, syncs to the EU

Transcripts, translations and notes live in a local database on your machine (they work offline) and sync to EU infrastructure in Zürich (eu-central-2).

EU data residency

Your meeting data is stored in the EU — Zürich (eu-central-2) — and real-time speech runs on an EU endpoint. See our Privacy Policy for the full sub-processor list.

No audio is ever stored

Audio is processed live and discarded. Only transcripts and translations are retained — never the recording.

Local-first

Your meetings live in a local database on your machine and work offline. The cloud holds a synced copy — not the original.

No training on your data

Your conversations are never used to train models. They stay yours — with full GDPR export (JSON or Markdown) any time.

GDPR-by-design

Data minimisation, meeting export and deletion, with company security requirements reviewed before an Enterprise pilot.

Encrypted in transit & at rest

Industry-standard encryption protects your transcripts and account data end to end.

Your data, your controls

  • Export everything as JSON or Markdown, any time — no support ticket needed.
  • Clear your local data or delete your account and its synced data.
  • Meeting export and deletion are available. Custom organization retention is planned.
  • Your conversations are never used to train models.

Sub-processors

Real-time speech recognition and AI processing run on EU endpoints of carefully selected sub-processors. The full, current list — including what each one sees — is documented in our Privacy Policy.

Read the Privacy Policy

GDPR-aligned with EU data residency today. Formal certifications (e.g. ISO 27001) are in progress — we'll say so plainly when they're earned.

Security questions, DPA requests, or something we haven't covered?