// privacy

Privacy, in plain terms

Last updated: June 12, 2026

OnCue is built to keep your conversations close to you. Most of what it learns lives on your own machine. This page says exactly what it captures, where each thing lives, and what OnCue will never do — no hand-waving.

What OnCue captures

  • Live call audio.While a session is running, OnCue listens to your microphone and the meeting's system audio and turns it into a speaker-tagged transcript. It only listens while you have a session running.
  • Messages you point it at. When you connect Slack or Telegram and attach a channel, chat or thread to a session, OnCue reads the recent messages in that conversation so it can draft a relevant reply. It reads what you point it at — not your whole workspace.
  • What you give it. Your persona, the people you track, knowledge notes and files you add, and the sessions you create.

Where it lives

OnCue is local-first by design. Here is the honest map of where each piece of data actually sits:

on your machineYour full transcripts, your knowledge base (notes, files and digested sources), and your learned reply preferences stay in OnCue's data folder on your own computer. They are not uploaded.
OS keyring / deviceWhen you connect Slack, your Slack token and cookie are stored in your operating system's credential keyring. Telegram's login session is kept in a local file on the device. These channel credentials never leave your machine — they are not sent to OnCue's servers — and they are erased when you sign out or disconnect.
your account (synced)So you can pick up on another device, a bounded copy of your persona, your people, your saved templates, distilled notes, and your session records syncs to your OnCue account. Session records include a recent tail of the transcript and the suggestions from that session — recent activity, not your full local archive.
model gateway (in transit)To draft a reply, summarize a session, or write a brief, the relevant conversation text and context are sent over our metered model gateway, which forwards them to the language-model provider and returns the result. This is message text passing through to generate a response — billed against your usage.
transcription providerYour live audio is streamed directly from your machine to our speech-to-text provider (Deepgram) over an encrypted connection, using a short-lived token, and comes back as text. The audio does not pass through OnCue's own servers.

Account email, billing status and usage counts live with your account; card details are handled by Stripe and never touch our servers. We do not sell your data, and we do not use your transcripts or conversations to train our own models.

What OnCue never does

  • It never sends messages on your behalf. OnCue drafts replies; sending is always an explicit action you take. There is no auto-send to Slack, Telegram, or anywhere else.
  • The overlay is yours alone.The on-screen advisor is shown only to you on your own screen. It is not part of any screen share, recording, or broadcast — the other people in your call don't see it.

A word on encryption

We want to be precise rather than reassuring-sounding: data in transit between your machine, our gateway and our providers travels over TLS, and your connected Slack credentials are protected by your operating system's keyring. We do not claim end-to-end encryption, and the local transcript and knowledge files on your own machine are not separately encrypted at rest by OnCue — they are ordinary files protected by your own device and operating system. Keep your computer secured.

Your control

Your data is yours to take or remove. From the desktop app's Account & Settings, you can export a copy of your data and delete it — including your sessions and the synced copy in your account. Disconnecting Slack or Telegram erases their stored credentials from your device, and signing out clears your local persona, knowledge, preferences and channel credentials.

You can also email admin@kupia.io to request access to, export of, or deletion of the data held with your account, and we will help.

Recording consent is your responsibility

Recording or transcribing a meeting may require the consent of the other participants. You are responsible for complying with the recording-, wiretap- and privacy-consent laws that apply to you before capturing audio or messages with OnCue, and for obtaining any consent those laws require.

Who we are & how to reach us

OnCue is built and operated by Kupia Lab. For any privacy question, or to exercise the controls above, email us at admin@kupia.io. For the full legal terms that govern the service, see our Terms of Service.