Privacy

Understand how CueDraft handles selected text, account data, and optional hosted providers.

CueDraft works from the text surface in front of you on macOS, so privacy expectations should be clear before you use it. This page explains what stays local, what uses cookies or account data on the web/customer surfaces, and what changes when you choose a hosted provider.

How text moves through CueDraft

CueDraft works on the selected text you are using in the app in front of you. It captures that text, lets you run an action, and then gives you a review path before the result goes back.

If you use CueDraft Engine, generation stays on your Mac. If you choose a hosted provider, the text needed for that run follows the provider path instead. Logging, retention, and processing rules can vary by provider and are governed by that provider when you select it.

Web, account, and session data

CueDraft uses account/session cookies on the website and customer surfaces so sign-in, portal access, and account checks can work reliably.

Email address, account state, subscription status, registered devices, billing status, and related support context may be stored and processed so CueDraft can operate the account, protect access, support billing, and answer customer requests.

Privacy-safe product metrics

CueDraft may collect product health and usage metrics so we can tell whether the Mac app is being installed and used. These metrics can include app version, internal release identifier, macOS version, anonymous install ID, launch/activity timestamps, and feature/action counts.

Usage metrics do not include text content, selected text, prompts, rewritten text, clipboard contents, source app names, window titles, document names, URLs, or file paths.

Billing and third-party services

Checkout, subscription management, and refund/cancellation handling may involve third-party payment or customer-management infrastructure. Those providers process billing and account-management data under their own policies when they are part of the transaction flow.

Hosted AI providers are optional. They only receive text when you explicitly choose them for a run inside CueDraft.

Why macOS permissions are required

CueDraft uses macOS automation permissions to support reliable capture and approved edits in the app you were using.

When a text surface is not a good fit for direct editing, the panel keeps the result available so you can copy, revise, or try again.

Retention and privacy questions

When you stay on CueDraft Engine, selected text can stay local to your Mac. Account, session, billing, and support records are retained for as long as reasonably needed to operate the service, resolve billing issues, prevent abuse, and meet legal/compliance needs.

Questions about account data, privacy expectations, or support follow-up can be sent to support@cuedraft.com.