ZERO RETENTION GUARANTEE

PRIVACY POLICY & DATA SPEC

Cue is engineered with an ironclad zero-knowledge, client-side first architecture. We operate zero intermediary proxy servers that read, store, or train on your prompts. Your API keys and inputs stay in your personal browser sandbox.

Last updated: September 2026 • Effective immediately

Executive Privacy Commitment

Cue is designed with a strict zero-knowledge, client-side first architecture. We do not operate proxy servers that read, store, or train on your prompts. Your API keys and raw inputs never leave your personal browser environment.

• 0% Prompt Retention: Prompts and completion pairs never touch Cue servers
• Local Keys: API keys stay in sandboxed browser storage
• No AI Training: We never train models on your data
• Google Limited Use: Full adherence to Google API policies

Information We Access and Collect

When you interact with Cue via our website (cueprompt.in) or the Cue Chrome Extension, we collect the minimal data necessary to deliver and authenticate our service:

  • Account & Authentication Metadata: If you choose to sign in via Google OAuth, Apple ID, or Clerk, we receive your email address, full name, and avatar URL. This information is used solely to identify your account, display your profile initials or avatar within the dashboard, and attach your active subscription tier.
  • Subscription & Transaction Identifiers: For Cue Pro subscribers, our payment processor (Razorpay, supporting Cards, UPI, and NetBanking) processes billing securely. We store your anonymous customer ID, subscription status, and expiration timestamp. We never see, store, or process credit card numbers or banking credentials.
  • Aggregated Usage Telemetry: Anonymized event counts (such as total compiler activations) collected without IP addresses, personally identifiable information, or prompt text, strictly for performance monitoring and error diagnosis.

Information We Do NOT Collect (Zero-Retention Guarantee)

Cue differs fundamentally from legacy cloud wrappers. We explicitly commit to the following architectural guarantees:

✕ Never Collected or Stored
  • • Your draft prompt text
  • • Prompt and completion pairs
  • • Webpage contents or chat history
  • • Your third-party LLM API keys
  • • Browser navigation or search history
🛡 Client-Side Sandboxing
  • • Processed entirely in browser sandbox memory
  • • Keys stored in sandboxed chrome.storage
  • • Direct TLS 1.3 browser-to-provider dispatch
  • • Zero intermediate server hops or logs

Browser Extension Permissions & Data Security

The Cue Extension requests only the minimum permissions required for execution:

  • storage: Required to securely store your local settings, theme preference, and encrypted API keys locally on your device via chrome.storage.local.
  • Host Permissions: Scoped strictly to supported AI chat surfaces (chatgpt.com, claude.ai, gemini.google.com, perplexity.ai) and provider API endpoints. Cue does not run on banking, healthcare, or arbitrary domains.