PluelyPluelyDocs

Features

Stealth Mode & Screen-Share Privacy

Pluely v1 is built with the assumption that you'll often be using it while sharing your screen, on a call, or presenting — and that the overlay itself shouldn't become a distraction or a giveaway in those moments. Stealth and privacy features run throughout the app, from how the overlay behaves on screen shares to how your credentials are stored on disk.

Discreet during screen shares

The overlay is designed to stay out of the way when you're sharing your screen. Rather than announcing itself, it's built to blend in and avoid drawing attention during a screen share, video call, or recording — so you can reference Pluely's answers or run a Listen session without it becoming the focal point of what others see.

Nothing pops out of the window

Screen-capture protection covers Pluely's window, not things the operating system draws next to it. Since 1.1.0, everything that used to be a system popup is drawn inside the window instead, so it is covered too:

  • Hover hints. The little labels that appear when you rest the pointer on a button are Pluely's own, not the OS tooltip.
  • Menus. The Listen language picker and every other dropdown open inside the window.
  • Right-click. The system context menu is turned off in the app.

One exception: the file picker that opens when you attach a file is drawn by the operating system, so it can show up in a share while it is open. Attach files before you start sharing if that matters.

If you ever notice anything else from Pluely on a shared screen, write to support@pluely.com with a screenshot; that is a bug, not a setting.

What each operating system can hide

Everything below is on by default and needs no setting.

  • macOS: every Pluely window (the overlay, the compact meeting view and the dashboard) is excluded from screen recordings and shares, and the overlay is a non-activating panel: showing it with a shortcut never activates Pluely, so the menu bar and the Dock stay exactly as they were and your meeting app keeps focus. Clicking into the question box to type moves keyboard focus to Pluely.
  • Windows: the overlay, the meeting view and the dashboard are excluded from captures with the system's capture-exclusion flag. This needs Windows 10 version 2004 (build 19041) or newer; on older builds Pluely appears in a shared screen, and App Settings says so. The overlay and the meeting view are non-activating tool windows, so they stay out of Alt-Tab and never take the foreground. The dashboard is a normal window and does show in Alt-Tab. Typing goes to the overlay through Pluely's own keystroke routing when the composer is targeted, again without the overlay taking focus.
  • Linux: neither X11 nor Wayland offers a way to exclude a window from screen capture, so Pluely can appear if you share your whole screen. Share a single window instead. On X11, Pluely stays out of the taskbar and the task switcher, and showing the overlay never takes the keyboard from your meeting app. On Wayland the compositor decides those things, so the overlay may appear in the switcher or take focus when shown. Click the overlay or use the Refocus Input Box shortcut when you want to type. App Settings shows this note on Linux.

Finding Pluely again

Pluely has no menu bar or tray icon, so nothing on screen gives it away. If the overlay is hidden and a shortcut stopped working, open Pluely again from Applications, the Start menu or your app launcher: it is already running, so the overlay comes back. On macOS, clicking Pluely in the Dock does the same. When an update is available, the overlay shows a short Update available line that opens the updater.

Typing into the overlay on Windows

On Windows, typed keys reach the overlay's composer through Pluely's own keystroke routing, so the overlay never has to take focus from the app you are presenting. There is nothing to turn on: show the overlay with its shortcut or the Refocus Input Box shortcut, and type. A hidden overlay never captures keystrokes.

Encrypted, on-device credentials

If you bring your own provider keys (rather than using Pluely's managed models), those keys are stored encrypted on your device. Pluely never exposes the underlying infrastructure behind its managed models — when you use Pluely's managed AI, you're never handling or seeing a raw provider key at all, and when you do bring your own key, it stays encrypted locally rather than sitting in plain text.

Friendly, non-technical errors

Consistent with Pluely's overall approach to trust and discretion, anything that goes wrong — a failed capture, a connectivity hiccup, a stalled transcription — surfaces as a friendly, Pluely-branded message rather than a raw technical error. This keeps the experience calm and consistent whether you're alone or in front of others, and never leaks internal details about what's running behind the scenes.

How it works

  1. Open App Settings in the dashboard: the "Invisible on screen shares" note tells you what your operating system hides.
  2. Nothing to enable: capture exclusion and the non-activating overlay are always on where the OS supports them.
  3. Confirm your overlay theme and transparency (see The Pluely v1 Overlay Window) are set to something unobtrusive for your typical screen-sharing context.
  4. If you're using your own provider key rather than Pluely's managed models, know that it is encrypted at rest on your device the moment you save it.

Tips

  • Test your screen-share setup once with a colleague or a recording before relying on it in a high-stakes meeting, so you know exactly how discreet the overlay appears on your specific setup.
  • Combine a smaller overlay size (S or M) with reduced transparency settings for maximum discretion during a share — see The Pluely v1 Overlay Window for size and appearance controls.
  • On Windows, test the overlay size and position you plan to use once before a call, so typing into it mid-call holds no surprises.
  • Prefer Pluely's managed models if you'd rather never manage or store a provider key yourself — Pluely handles the infrastructure entirely.

Last updated July 10, 2026 · pluely.com