CueEncrypted in your account. Yours to take or delete.
What you ask about your screen is sent with the question and not kept. Your meetings, notes and memory are in your Cue account, encrypted, so they are on every device you use; your audio stays on your Mac; and one switch keeps everything on your devices instead. Here is the whole picture.
Four places. Nothing hidden.
On your device, and only there
- A meeting’s audio, written to your Mac and deleted after the time you choose in Settings, a month by default. Dictation audio too
- Screen summaries and the things Cue noticed on screen
- Reference material you paste in
- The search index over your memory, diagnostics, and the log of actions Cue took
- Your personal dictionary and settings
- The calendar on your Mac, read under the macOS Calendars permission, never uploaded
- Your Cue sign-in, and nothing else of yours: macOS does not let Cue read what other apps put in the Keychain
Sent over TLS, processed, discarded
- The text needed for the request you triggered: the thread, your dictated audio, a meeting’s segments
- The model is reached through Cue’s backend, so the app never holds its credentials
- The request is not stored on our servers, and its working state is deleted when it finishes
- Deep research is the exception: its report waits for your Mac for three days at most, its working data for one, then both are deleted
- Screenshots are sent when you ask Cue something, so it can see what you mean. On by default; you can turn them off
- Nothing you record or dictate trains a model
- One exception: a live conversation streams your mic straight to a realtime voice provider. Cue asks first, naming them
In your Cue account, encrypted
- Your meetings: write-ups, transcripts, questions, marks and folders
- Your memory: people, facts, promises, and your writing style and samples
- Meeting briefs and the answers you gave while preparing
- Your drafts and dictation history
- Your chats with Cue, including what Cue looked up to answer you
- Encrypted at rest with a key unique to your account, in the United States. Cue’s servers can open it, to sync your devices and run the features you use. It is not end-to-end encrypted. Nobody at Cue looks at it; if support ever needs to, we ask first, and that access is time-limited and logged. Every read is logged
- Your account (your email), your subscription state, and anonymous usage counters for fair use: numbers, not content
- Turn on local mode, or delete your account, and the cloud copy is deleted within 24 hours, backups included
In your team’s workspace, on Teams and Enterprise
- Documents your team adds for everyone’s Cue to answer from: the text Cue read from them, never the original file
- Encrypted at rest with a key unique to your team, in the United States. Cue’s servers can open it, to answer your team’s questions. It is not end-to-end encrypted
- Google’s Gemini API turns the text into embeddings, the numbers that let a question find the passage that answers it. Those are derived from the text and stored without that extra encryption
- Remove a document and its text and embeddings are deleted at once. If your team stops paying, the workspace is deleted after 30 days
- A folder an admin connects from Google Drive, OneDrive or Notion is read through that admin’s own account and checked for changes every hour. A file that leaves the folder leaves the workspace
- Your own files and memory never go into the workspace
Every learning behavior has a switch.
Keep a copy in your Cue account
Your meetings, notes, memory and chats with Cue, encrypted, so they are on your Mac and your iPhone. Turn on local mode and the cloud copy is deleted within 24 hours, backups included.
Learn from what I send
The master switch for everything Cue learns from sent messages. Exclude specific apps while leaving it on elsewhere.
Review before it remembers
What Cue notices lands in a review inbox first. Every accepted row carries its provenance, so you can delete that line on its own.
Preview before insert
Drafts show up in a review card before anything touches your field. There is no auto-send code path at all.
Keep the audio
Not at all, a week, a month (the default), or three months. Sent in segments only to be transcribed, never stored on our servers.
Screenshots, on by default
Sent when you ask, so answers use what is on screen. Turn it off and Cue works from accessible text only. Deleted when the request finishes.
Let Cue act on my Mac (beta)
Does nothing until you turn it on. Watch me asks before every step. Deletes are blocked, and credential fields are refused. macOS asks you before Cue controls another app or opens your Desktop, Documents or Downloads.
Live conversation, and its consent
The one path where audio leaves your Mac without passing through us: it streams to Google’s realtime voice service. Cue asks first.
Hide Cue from screen sharing
Hides Cue's windows from screen sharing and screen capture. The app itself stays visible in the Dock and the menu bar, and windows that belong to macOS rather than Cue, like the sign-in sheet and the file picker, cannot be covered. On paid plans, off until you turn it on.
The app talks only to Cue’s backend, over TLS, and holds no credentials for anything beyond it. Sign-in and payments are handled by dedicated providers, so we never see your password or your card number.
One request, end to end.
What actually happens when you hold the key, in order, with nothing left out.
You trigger
Nothing leaves your Mac until you tap, double-tap or hold the key, or press record. Idle means silent.
It travels over TLS
Only the moment’s text or audio goes, encrypted, through our backend.
The model runs
The reply streams back into the field your cursor is in, or onto the meeting’s page.
If a step wants to act
Every step is classified twice, on the server and on your Mac. The stricter answer wins, and the step waits for you.
The request is not kept
Its working state is deleted the moment it finishes. An action paused on your Mac expires within the hour, and a research report is deleted once your Mac has it, within three days.
The app that runs it
Updates are cryptographically signed, and the signature is verified before anything installs.
Everything that can receive it.
Every function that can receive something of yours, what it gets, and the route it takes. Nothing else is in the path.
Google, the model
Field text, on-screen text, thread context, selected memory, a transcript
Your Mac → Cue’s backend → the modelGoogle, meeting transcripts
The stretches of a recorded meeting where someone is speaking
Your Mac → Cue’s backend → the transcriber. Neither clip nor text is keptGroq, speech to text
Dictation clips, and a meeting’s audio when Google cannot take it
Your Mac → Cue’s backend → the transcriber. Neither clip nor text is keptGoogle, spoken answers
The answer text to be spoken
Your Mac → Cue’s backend → the voice serviceGoogle, live conversation
Your mic audio, while a live conversation is open
Your Mac → the provider directly. Asked firstComposio, connected accounts and research
Requests to read an account, run a search, read a page for research, or make a write you confirmed
Your Mac → Cue’s backend → the brokerClerk, sign-in
Your email, name, and an account id
Your browser or Mac → the identity providerStripe, payments
Your card details
Your browser → the processor. Cue never sees a card numberNeon, your cloud copy
Meetings, notes, memory, drafts, dictation history, chats with Cue, encrypted
Cue’s backend → the database, in the United StatesExpo, then Apple or Google, your phone’s notifications
A helper’s name, how many things it made or wants you to approve, and your phone’s notification token
Cue’s backend → your phone. Only once you turn notifications onVercel and Upstash
Short-lived codes, usage counters, a request’s working state, a research report until your Mac has it
Cue’s backend only. Deleted when it finishes; a research report within three daysUpstash
What Cue changed in a connected account with your approval: the ids it changed, so you can undo it
Cue’s backend only. 24 hours for Undo, 7 days for the list of changes. Never the contentComposio, Clerk, Stripe, Upstash and Vercel maintain SOC 2 Type II reports. Cue’s own compliance program is under way. The privacy policy says what each is limited to doing.
What we keep, we keep for you.
Your screens, your audio and the requests Cue runs are not kept on our side. What we do keep, your meetings, notes and memory, is encrypted, never used to train anything, and yours to download or delete.
No screen history
Screenshots are sent with screen questions and deleted when the request finishes.
No audio on our servers
A recording is sent to be transcribed and stays on your Mac.
No copy of a request
Processed, streamed back, and deleted when it finishes. A research report waits for your Mac, three days at most.
No bot in your calls
And no email to your attendees: the recording is your Mac’s own audio.
