Your conversations are yours — not our data.

The short version

• CueAside servers do not store your audio, screenshots, transcripts, questions, or answers. Conversation content is processed in real time and requests to our AI provider are sent with storage disabled.
• Your session history lives in the CueAside app on your Mac, under your control.
• On our servers we keep the minimum needed to run the service: account and optional profile data, subscription state, content-free monthly usage, and bounded operational diagnostics.
• We do not sell your data or use it for advertising.
• The homepage prints the same collection and retention boundaries as a plain-language privacy ledger.

What we collect

Account. When you sign in, we store your email address and account identifiers with Supabase, our authentication and database provider. If you use an identity provider such as Google, it may also supply the name and avatar shown in your CueAside account menu.

Billing. Payments run through Stripe. We store your subscription status, plan, and renewal dates. Card numbers never touch CueAside servers—Stripe handles checkout and the billing portal. We retain Stripe webhook event identifiers and processed times for up to 90 days so a retried event is not applied twice; we do not store the webhook body in this receipt table.

Usage counts. To enforce monthly fair-use limits we keep numeric counts for answers, fallback transcriptions, provider-token grants, and live-transcription duration. To make a retried duration report idempotent, a random event identifier and its duration can be retained for up to 90 days. These records never contain audio, transcript text, questions, answers, or session IDs. An answer's automatic network retries share a 15-minute receipt containing a random request ID, one-way account and request fingerprints, an attempt count, and timestamps. It contains no conversation content; expired receipts are eligible for cleanup after a 24-hour buffer and are pruned as new receipts arrive.

Waitlist. If you join early access, we store the email and signup source you submit so we can send your invite.

Abuse prevention. Rate-limit records use pseudonymized keys derived from network information; we do not keep raw IP addresses in these records. Inactive keys are removed after 30 days.

Website analytics. Vercel Web Analytics records page visits and aggregated dimensions such as referrer, country, device type, browser, and operating system. Speed Insights records page route, URL, connection type, and Core Web Vitals such as load and interaction timing. These services do not receive CueAside account details or conversation content from us.

Crash diagnostics. When crash reporting is enabled in a distributed app, we collect the app version, operating-system and device class, crash stack, a closed error code, and bounded numeric status values. We exclude account and session identifiers, screenshots, view hierarchy, network requests, local paths, audio, transcripts, questions, answers, prompts, prepared context, and saved session content.

Performance diagnostics. For up to 30 days we keep content-free answer timing and transcription health records. A one-way pseudonymous account hash can be attached to answer timing records so an administrator can investigate a specific account without storing its email or raw account ID in the metric. A transcription record can contain the stream type, capture source, delivery path, selected model and language, signal duration, voiced duration, peak level, silence threshold, and a closed result such as completed, empty, or failed. These records contain no session identifier, filename, audio, transcript, question, answer, prompt, prepared context, or provider response.

Administration records. The private operator Console uses opaque admin sessions and a content-free audit log to protect account, billing, and diagnostic access. Expired or revoked admin sessions are removed after seven days. Audit entries can keep the administrator ID, affected account ID, action, and time for up to 90 days, but contain no conversation content.

How conversation content is handled

During a session, audio is transcribed by Deepgram and relevant context is sent to OpenAI through the CueAside API to generate your answer. If live transcription is unavailable or uncertain, a bounded audio segment may be sent to OpenAI for a second transcription attempt. CueAside servers do not retain the audio, transcripts, or generated answers after the response is delivered to your app.

If you invoke Scan or Attach Screenshot, the selected screenshot is sent through the CueAside API to OpenAI so it can answer what is on screen. Screenshot capture is not continuous, and CueAside servers do not retain the image after the response is delivered. Pending screenshots remain only in the app until they are used, cleared, or the session ends.

Requests include a pseudonymous safety identifier—a one-way hash that lets the provider enforce abuse protections without receiving your email or account details.

The context you prepare (resume, notes, briefs) and your saved sessions stay in the app on your Mac. Removing them there removes them from CueAside.

Services we rely on

• Supabase — authentication and database hosting.
• Stripe — checkout, subscriptions, and the billing portal.
• Deepgram — live speech-to-text transcription.
• OpenAI — answer generation and fallback transcription, including user-invoked screenshot analysis.
• Vercel — website and API hosting.
• Sentry — privacy-limited crash and error diagnostics.

Each provider processes only what its role requires, under its own security and privacy commitments.

Your responsibilities in live conversations

CueAside listens to conversations you take part in. Laws about recording and transcribing conversations vary by region, and some require the consent of other participants. You are responsible for using CueAside in a way that complies with the laws and policies that apply to you.

Deleting your data

Account deletion is one call to our API: it cancels any active subscription immediately, removes your billing record and usage counters, and deletes your sign-in identity. You can also email support@cueaside.com from your account address and we will run the same deletion for you, along with any waitlist entry. Session content is deleted directly from the app, since it is stored on your Mac. Content-free operational receipts, pseudonymous performance records, hashed abuse-prevention counters, and security audit records age out under the retention periods above rather than recreating a deleted account.

Changes and contact

If this policy changes in a way that matters, we will note it here with a new date. Questions are welcome at support@cueaside.com.