Your workspace is local. Provider connections can send context.

Specs, planning, readiness, implementation summaries, reconciliation, and validation evidence are repository-visible files. Normal CLI use does not upload those artifacts to the website.

The browser GUI connects to a runtime on your machine. When you choose a remote inference provider, prompts and permitted project context can leave your machine for that provider. Review the connection, context disclosures, and provider terms before sending. Local storage does not mean remote inference is offline.

Choose additional project files in Chat context before sending. The open document is included with your question. Selecting context permits reads when you send; document updates require a separate action.

Conversation history and runtime state are stored locally. Review ignore rules and what you commit; keep credentials and private state outside version control. Your external coding agent has its own storage and disclosure behavior.

The website uses Vercel Analytics for page views and interactions. Custom events include a bounded entry channel such as ChatGPT, another recognized assistant, other, direct, or unknown. Recognized campaign tags take precedence over referrer hostnames. That category stays in memory across navigation within the page application and resets on a full page load. We add no visitor identifier or storage cookie for this attribution and send no raw campaign values or referrer URLs in custom event properties. Missing referrers can appear as direct traffic; attribution does not prove a recommendation or a successful installation. Provider and browser opt-out behavior applies.

The website publishes release-pipeline-produced downloads, release notes, checksums, and manifests, and links to the separate canonical documentation application.

Stripe secrets, webhook payloads, customer records, license signing keys, recovery evidence, and support identity records belong behind server-only boundaries.

Local file operations and signed license verification are local-first and offline-capable. Online activation is not required for those operations. Connected remote inference requires network access.

Local storage and signed-license verification are separate from optional provider disclosure. Payment and signing material stay behind server-only routes, and release checksums are published for buyer verification. These boundaries are not a certification, security guarantee, or claim that every environment is compatible.