PluelyPluelyDocs

Features

Your Data Security in Pluely v1

Pluely v1 is designed so you stay in control of your data at every step — what's stored, where it's stored, what gets shared with a model, and how to remove it. This page walks through the concrete mechanics.

History and transcripts are stored locally

Your Ask conversations, Listen transcripts, saved meetings, and prompt library are stored on your own machine as local data, not in a Pluely-hosted account database. That means:

  • Your history is readable and usable only from the device it was created on.
  • There's no central Pluely database of your conversations to be breached, leaked, or subpoenaed independently of your machine.
  • Clearing local data or uninstalling the app removes that history, because it was never duplicated elsewhere.

See Local-first & private for the full picture of what's stored where.

You control what context gets attached

Nothing is sent to get an answer unless you put it there. In Ask mode, you decide whether to attach a screenshot, an image, or a document — Pluely doesn't reach into your files or screen on its own. In Listen mode, audio is only captured while a session is actively running and you started it. If a piece of context feels too sensitive to share, the simplest safeguard is: don't attach it. Ask a more general version of the question, or redact the sensitive part of a screenshot before sending it.

Maximum privacy: your own key or a local CLI

For work where you don't want any request reaching Pluely's servers, Pluely v1 supports two bring-your-own options:

  • Your own provider API key, configured in Model selection. Requests go straight from your device to the provider you chose, using your own credentials and your own account's data policies — Pluely's servers are never in that path.
  • A local CLI already running on your machine — for example Claude Code, Gemini CLI, or a locally-hosted model through Ollama. Pluely hands the request to that tool locally instead of calling out over the network at all. Setup is covered in Connect a local CLI.

Either path is the right call for confidential meetings, regulated data, client work under NDA, or anything else where "leaves my machine" is not an acceptable answer.

You don't need to know — or trust — a specific model vendor

When you use Pluely's managed models (the default, no-setup option), Pluely intentionally doesn't require you to know or choose which underlying model or infrastructure provider is doing the work. You interact with one consistent Pluely experience, and Pluely handles routing, reliability, and provider relationships behind the scenes. If that abstraction isn't enough assurance for a given task, the bring-your-own-key or local-CLI options above give you full visibility and control instead — you pick the exact provider and account.

Safe uninstall and data removal

Because history and transcripts live locally rather than in a hosted account:

  • Removing local app data (through the app's own settings, or by uninstalling and clearing its local data folder on your OS) removes your Ask conversations, Listen transcripts, and saved meetings along with it.
  • There's no separate "delete my cloud account data" step required, because your conversation history was never mirrored to a Pluely-hosted database in the first place.
  • If you're moving to a shared or work-provided computer, a clean uninstall plus clearing local app data is sufficient to leave nothing behind.

Best practices for sensitive work

A few habits make Pluely noticeably more private for high-stakes use:

  1. Use your own provider key or a local CLI for anything confidential — it removes Pluely's servers from the request path entirely.
  2. Be deliberate about attachments — only attach the screenshot, document, or region that's actually needed to answer the question.
  3. Use screen-share stealth during calls so the overlay, your notes, or a live transcript aren't visible to people you're presenting to. See Stealth & privacy.
  4. Pause or stop Listen mode the moment a conversation turns into something you don't want transcribed.
  5. Clear local history periodically if you share a machine, or rely on full-disk encryption (standard on modern macOS/Windows) to protect data at rest.

Last updated 2026-07-10 · pluely.com