Security & privacy

What happens towhat you send.

Plainly: where your items go, who can read them, what we keep, and what we never do. No small print.

The short version

Five promises.

  • Never loggedWhat you send never goes into our logs. Our logs record that something happened (a send, a sign-in), never what it was.
  • Never soldNo ads, no selling or sharing your data, no training anyone's AI on it.
  • Encrypted on the wayEvery connection between your devices and Mnem0 is encrypted (HTTPS and secure WebSockets).
  • Yours to deleteDelete an item and it's gone from every device. Delete a workspace and everything in it goes.
  • Honest about the serverYour items are stored on our server so they can reach your other devices. That means the server can read them; see below for why, and what's coming.
How a send works

From your device
to your others.

  1. 01 · Your device

    Sent encrypted

    Your device sends the item over an encrypted connection, signed in with that device's own session.

  2. 02 · Our server

    Checked and stored

    The server checks you belong to the workspace, stores the item, and tells your other devices something's new.

  3. 03 · Your other devices

    Fetched by them

    Connected devices get it at once. Sleeping phones get a push that says only "something new", with no content; the phone then fetches the item itself.

In detail

The long version.

Who can read your items

In Personal, only you, on your signed-in devices. In a team or Quick room, its members. Every request to our server is checked against workspace membership, every time.

Our server can read items too, because it stores them to deliver them and keep your history. We chose this on purpose: features like search, link previews, voice notes and, later, AI that helps you find things need it. Notes apps and most sync tools work the same way. We don't look at your items, and we've built the system so content never ends up in logs.

Secrets: don't send passwords yet

For passwords, one-time codes and keys, an end-to-end encrypted vault is on the roadmap: items in it will be encrypted on your device, and our server won't be able to read them. Until it exists, please keep secrets in a password manager.

Signing in and devices

  • No passwords: you sign in with Google, or by scanning a QR code shown by a device that's already signed in.
  • Each device gets its own session. Sessions expire after 90 days without use.
  • Devices lists every signed-in device. Remove one and it's signed out at once, on every request it makes.
  • Signing out removes that device from the list.
  • In the browser, the session sits in a secure, HTTP-only cookie that page scripts can't read.

What we keep, and for how long

  • Items: until you delete them, or 30 days for unpinned items. Pinned items stay until you unpin them.
  • Quick rooms: deleted with everything in them when they end (after 24 hours by default).
  • Your account: your email address and name from Google, and your devices' names and types.
  • Technical logs: request times and errors, without the content of what you sent; kept briefly to keep the service running.

Who runs the pieces

Mnem0 runs on a small set of well-known services: Render (our server), Supabase (the database, PostgreSQL), Backblaze B2 (stored files), Google (sign-in), and Firebase Cloud Messaging and your browser's push service (content-free "something new" pushes). The contact form adds Cloudflare Turnstile (spam check) and Resend (emails us your message).

Found a problem?

If you think you've found a security issue, please email betalabz.org@gmail.com and give us a chance to fix it before telling others. Thank you.

Get started

Send with confidence.

And keep your passwords in a password manager, for now.