Cue

Privacy Policy

Last updated:

In short: Cue reads the conversation in front of you so it can write a reply that fits, and it does that on your Mac. What it remembers lives in a file in your own Library. It is never uploaded, never synced to a server of ours, and never used to train anything. There is no account, no sign-in, no analytics, and no telemetry. When you run an action, only the small context that action needs is sent to the AI provider whose key you supplied, directly from your Mac, and Cue shows you exactly what it sent. Choose a local model and nothing leaves your machine at all.

This policy explains what Cue ("Cue", "the app") does and does not do with your information. It is written in plain language.

Information we collect

Cue does not collect personal data. There is no account and no sign-in, and the developer does not receive, store, or retain information about you. Some data is used only on your device:

These are ordinary files in the app's own folder in your Library, plus one Keychain item. You can browse the memory, edit it, delete a single entry, or clear all of it at any time.

How Cue reads the conversation

Cue's whole job is to write something that fits the conversation you are in, which is why macOS asks you to grant Accessibility access. That reading happens locally, on demand:

What Cue remembers, and what it does not

Cue keeps a memory so that a promise you made in one conversation is known in the next one. It is deliberately one-directional: only your own facts travel between conversations. What another person told you stays in that person's conversation and is never repeated to someone else. Everything Cue holds is visible in the memory browser inside the app, in plain words, and any line can be edited or removed.

What Cue does not do

The AI provider you choose

Cue has no AI of its own. You supply a key for a provider you already trust, such as Anthropic, OpenAI, or Google Gemini, or point Cue at any OpenAI-compatible endpoint, or run a model locally with Ollama. When you run an action, the request goes directly from your Mac to that provider over HTTPS, never through us. It carries only what is needed for that one action: the context read from the app, the relevant part of Cue's memory, and your instruction. That provider's own privacy policy and data-retention terms then apply to that request, so it is worth reading theirs. If you choose a local model, no request leaves your Mac at all.

Permissions

Cue asks for one macOS permission, and it only enables the feature:

If you do not grant it, Cue still opens; the writing features simply stay off until you do. You can revoke it at any time in System Settings.

Third-party services

None beyond the AI provider you choose and configure yourself. Cue has no third-party SDKs, no advertising or analytics services, and no hosted backend of its own.

Data retention

Because the developer never receives your data, there is nothing for the developer to retain. Cue's memory, your actions, and your settings remain on your device until you remove them or uninstall the app.

Your choices

You control the permission in System Settings → Privacy & Security, and you can change or revoke it whenever you like. Inside the app you can browse and edit everything Cue remembers, delete any entry, clear the memory entirely, remove your API key, and switch to a fully local model. Denying a permission only disables the related feature; the rest of the app keeps working.

Children's privacy

Cue is a general-audience utility. It does not knowingly collect any information from anyone, including children.

Changes to this policy

If this policy changes, the date above will be updated. Material changes will appear here before they take effect.

Contact

If you have any questions about this policy or your data, please write to support@appsbymo.app.