Usage Diagnostics Only

Effective August 27, 2026 · Applies when No prompts or transcripts is selected.

full transcripts · diagnostics only · send nothing · overview

What leaves your machine: anonymous operational statistics and crash information. No prompts, code, responses, or transcripts.

Diagnostics

Events keyed by a random telemetry ID can include install and upgrade events, session and turn counts, onboarding steps, provider and model names, coarse feature use, performance and crash information, numeric task-progress counts, version, OS, and architecture. They exclude prompts, responses, source code, file contents, paths, task descriptions, goals, and plans.

Purpose and retention

We use diagnostics to operate, secure, debug, and improve jcode. Hosting and analytics providers process them for us. We do not sell individual diagnostic events. Raw events are kept roughly 90 days; aggregate non-identifying rollups may be kept longer.

Choices and rights

Change this setting with /telemetry everything | no-prompts | nothing. JCODE_NO_TELEMETRY=1 or DO_NOT_TRACK=1 forces binary telemetry off. To request access or deletion, email [email protected] with your telemetry ID or account email.

Separate services

This setting controls binary telemetry. Model requests still go to your selected provider. Subscription routing, optional partner discovery, and this website are separate: subscription requests pass through our router without being stored as content; discovery sends a short tool query when enabled; the website uses a first-party beacon honoring DNT and GPC.