CueDraftUnderstand how CueDraft handles selected text, permissions, and AI paths.
CueDraft works from selected text on macOS, so privacy expectations should be clear before you use it. This page explains what stays local, what depends on hosted providers, and why the app needs macOS permissions.
How text moves through CueDraft
CueDraft works on selected text from 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 selected text follows that provider path instead. Logging and retention can vary by provider.
Why macOS permissions are required
CueDraft uses macOS automation permissions to support selected-text 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.
Account and billing data
Account, billing, and package access are managed through the CueDraft customer portal.
Questions about account data or privacy expectations can be sent to support@cuedraft.com.