Security
How Meymo protects your data: local first, with explicit network flows.
Last updated: September 2026
This page summarizes Meymo's security approach. Meymo Desktop processes audio and text locally by default; only some features use the network.
01Privacy shield
The privacy shield replaces detected information with markers and can restore identities in a reply. The 20 most recent correspondence tables are encrypted on this computer, separately from history, and can be deleted. Nothing is sent automatically. Always review the text: detection may be incomplete and does not guarantee compliance with professional secrecy.
02Local-first architecture
Dictation, transcription, rewrite and history are processed locally on your device. Your audio and text are not sent to Meymo for these local operations.
03Network flows
Use the network: account and sign-in, desktop connection and signed entitlements, billing via Stripe, updates, and a connector only when you explicitly save a finalized result and send it to a destination you chose. Drafts, raw dictation and unsent results remain local.
04On the app
Data stays local by default, entitlements are signed and verified, and you can delete your local data from the app. Sensitive tokens are protected by operating-system mechanisms where applicable.
05On the web companion
Traffic uses HTTPS, payment webhooks are signed, linked computers can be revoked, and secrets stay server-side.
06Diagnostics and support
Technical diagnostic: optional for each request. Preview its exact content before sending, or export it as a file. Only version, system and technical events are shared; dictations, audio, history and secrets are excluded.
07Reporting a vulnerability
To report a security issue, contact us at the address below. Please do not publicly disclose a vulnerability before we have had a chance to fix it.