Skip to content
Docs · Privacy by design

Privacy

Privacy by design

Yomenie starts from the most private default: mic and camera off, capture that stops by itself, server-enforced hearing, no recording, no trackers in the app.

Updated

On this page

People share an office in Yomenie, so nothing they say, show or do should travel further than they expect. Every feature starts from the most private default and widens only when you choose. Here’s what that means in practice.

Your mic and camera are off by default

  • They start off on every visit, and only your own click or key turns them on.
  • Nothing turns them on for you: not joining a room, not a video meeting, not a ring, not a reload, not an agent, not another person.
  • There’s no “camera on automatically” setting, and the camera is never restored after a reload.
  • Yomenie asks for mic and camera permission once when you arrive, so you don’t meet a prompt mid-conversation. It stops the tracks at once, and never asks again in that browser if you say no.
  • Screen sharing starts only from your own click on Share screen, and your browser’s picker decides what is shared. It’s never restored after a reload.

Capture stops by itself

Your mic, camera and screen share turn themselves off when their reason ends: when you leave the meeting room you turned them on in, when your open-space conversation ends, when you walk into a room without video, when you press Leave, or when you close the tab. Yomenie tells you each time. Stopping always releases the device, so the camera light goes off. The full rules.

The server decides who hears whom

  • Audio, video and screen shares only flow between connected people in the same conversation. That’s enforced on the server, not just in your browser. If your connection drops for a moment, you keep your place in the conversation for up to 10 seconds, so a blip doesn’t cut the call; after that you leave it.
  • Private-room walls and locked doors hold on the server.
  • Video and screen sharing never flow in a room whose video is off.
  • AI agents never receive audio, video or a screen share.

Nothing is recorded

There’s no recording, and no frames or thumbnails are stored anywhere.

You can always see when you’re live

The mic and camera buttons, the speaking ring, your face in the dock and your self-view show it. Your self-view can be shrunk but never hidden while your camera is on. While you share your screen, the dock says “You’re sharing your screen” with a small preview of what you’re sending and a Stop button. If something turns your mic, camera or screen share off for you, Yomenie says so.

One live tab

Only one Yomenie tab is on the floor and in your call at a time, so you can never hear or be heard from a tab you can’t see (a forgotten background tab, another window, a browser pane in another app). Other tabs keep working for everything else: open the board, chat or settings in a second tab and it stays live there, but it never holds your place, mic, camera or screen share, and never rings.

Opening the floor itself in a new tab moves your place and call there. The older tab stops your mic, camera and screen share (the camera light goes off) and leaves the call; its board, chat and settings keep working, and its floor page shows “You’re on the floor in another tab” with Use here and Close this tab. Use here moves the floor and call back the same way. When you close your floor tab, a second tab you left open takes your place after a few seconds, so you stay in the office. Nothing turns your mic or camera on when you switch: you press them again where you are. A reload simply picks up where you were, and the phone app is never affected.

Your attention stays on your device

  • Whether you’re looking at the Yomenie tab is never sent to the server or to anyone.
  • When a ring arrives, your own browser decides whether to chime or show a notification.
  • Notification permission is only asked when you click to allow it.
  • One exception, for bandwidth: video tiles nobody can see stop being received. That carries no reason and is never shown to anyone.

Local stays local

  • Device previews (the mic level meter, test sounds, the camera preview in settings) never leave your device.
  • Your device choices, keyboard shortcuts and other preferences are stored in your browser, not on the server.
  • Copy voice diagnostics builds its report on your device and sends nothing; you choose where to paste it. It never contains audio, chat text, emails, tokens, device names or network addresses.

Problem reports

This is the one place where diagnostics leave your device, because fixing a broken call matters more than keeping its logs local.

  • Report a problem (the ? help menu in the left rail, Audio & video settings, the status menu, the keyboard shortcuts sheet) sends what you write, the kind of problem, a screenshot only if you pick or paste one, and the same voice report Copy voice diagnostics builds. It also sends the page you were on (no query, except a few harmless keys), the app version, your browser and OS family, screen size, whether you were connected, and the last few app errors with links and anything token-like removed. See what’s sent shows the exact JSON first.
  • From your AI tool: ask Claude Code or another connected tool to report a problem with Yomenie (report_problem). It sends what you said, the kind of problem and, if named, the conversation and ticket as references only (a public channel’s name, “a private channel”, “a direct message”, a ticket key; never messages), with links, emails and anything token-like removed. It’s a report by hand: no voice report or browser details, just the tool’s name and what the server knew. You get the reference back; add_report_note adds more within a day.
  • When a call goes wrong (someone’s mic is on but no audio arrives, your audio isn’t going out, a connection drops, the camera won’t start, the video service refuses a call), your browser sends that report by itself a few seconds later and says so above the dock: “Sent a report to help fix this · Add a note”. The other people in that conversation are asked to send theirs too, silently. A problem your tab closed on is sent after the reload. At most a few an hour.
  • A short summary of every call, so we can count how many calls work: when a call ends, your browser sends how long it lasted, how long until you first heard each person (and they you), any silences or dropped connections, how many times it had to reconnect, the app version, your browser and OS family, and whether it started by walking up, a ring or a room. Only numbers and fixed codes: no audio, words, names of devices or network addresses. The server adds who was in the call and when each mic came on.
  • Turn it off in Settings, Profile: “Send reports automatically when a call goes wrong” (on by default). Off, nothing is sent automatically (no reports, no call summaries), not even when someone else’s call asks; reporting by hand still works.
  • Reports never contain audio, video frames, chat text, emails, tokens, device names, network addresses or session ids. The server adds what it knew at the time: who was in your conversation, the room, which tracks you were sending and receiving, and its own voice log lines for you.
  • Only Yomenie’s team reads them (the people on our Issues board’s team): not other members, and not your workspace’s owners or admins. They’re deleted after 30 days (call summaries after 90) and aren’t in the audit log. We also file a short ticket for each report on our own team’s board (your display name, workspace, what you wrote, browser and app version; never the diagnostics).

Sign-in emails

When you ask for an email with a link or code (to sign in, join a team, create an office, confirm a change or add a passkey), we keep a short record so we can tell when those emails stop arriving and help the person who is stuck.

  • What’s kept: your email address, the time, what the email was for, who hosts your mail (Google, Microsoft or other, looked up from your domain’s public mail records), whether our mail service accepted the email, and whether the link or code was then used.
  • What isn’t: the link, the code or anything that could sign someone in. Not your IP address either.
  • Who reads it: only Yomenie’s team (the same people who read problem reports). Not other members, and not your workspace’s owners or admins.
  • How long: 90 days, then it’s deleted. Deleting your account deletes your records at once.
  • If our mail service refuses an email, the page tells you so, and our team gets a note with no address in it.

Minimum data, stored hashed or sealed

  • Sign-in links, join links, sessions, agent keys and MCP tokens are stored only as SHA-256 hashes.
  • Third-party secrets in connections are encrypted and never returned, to anyone.
  • Other members don’t see your email; only owners and admins do, on the Team page.
  • Where you stood on the floor is kept in memory for 15 minutes so a reload puts you back, then forgotten. It’s never stored.

No trackers in the app

The app at yomenie.us/app has no third-party analytics or trackers: what happens on your floor stays between you and your team. This marketing and docs site may use cookieless, aggregate analytics (Cloudflare Web Analytics) for its own pages.

Presence is honest

“Online” means connected right now, nothing more. You set your own status and status note; nothing sets them for you except the “Clear after” you chose.

Changes are visible

Changes to who can reach someone or what an agent can do are written to the audit log or your account’s security log, so people can see them later.