# Privacy — OneCue

Last updated: September 2026.

This policy covers onecue.sh (the website) and the OneCue local install (the
skill and CLI). The short version: the product stores memory on your machine,
not ours; the website collects a waitlist email and aggregate analytics.

## The local product

The OneCue skill and CLI store project memory locally — Markdown records in
`.onecue/memories/` and `~/.onecue/projects/`. Nothing is sent to a OneCue
server; there is no OneCue account. Your coding agent still sends context to
its configured model provider under your existing settings — that boundary is
yours, not ours.

## The website

- **Analytics** — Vercel Web Analytics (cookieless, aggregated page metrics)
  and Google Analytics 4 (sets `_ga` cookies to measure page traffic;
  Google processes this under its own terms).
- **Waitlist** — joining the Cloud launch list stores your email (plus optional
  name, role, and how you found us) with Loops, our email provider. An
  httpOnly cookie (`onecue_waitlist`, one year) remembers that you joined.
- **Hosting** — Vercel processes standard request logs to serve the site.

We do not run ads, tracking pixels, or sell personal data.

## Your choices

Email hello@onecue.sh to be removed from the launch list or to ask what we
hold. Local memories are plain files — delete them any time;
`onecue uninstall` removes the hooks without touching them.

## Changes

If this policy changes materially, the update ships on this page with a new
date.