← On Deck

What On Deck collects

This page describes what the On Deck code in this repository does. If it ever disagrees with the code, the code is right.

In short

• Your sessions, prompts, code and project paths stay on your machine.
• Anonymous usage counts are sent by default. You can turn them off in Settings → Privacy. When they are off, nothing is sent.
• Bug reports, feedback and survey answers are sent only when you click Send, and you can read the text first.
• Installed builds check GitHub for new releases. Nothing is downloaded or installed without your click.

What stays on your machine

On Deck watches your Claude Code sessions through Claude Code's hooks and status line. Those hooks post events to a server on 127.0.0.1 (this computer only) that requires a token created at install time.

On Deck keeps its data in its data folder:

• macOS: ~/Library/Application Support/on-deck
• Windows: %APPDATA%\on-deck

File	What it holds
state.json	Your settings and session preferences (favorites, groups, mute, names you gave sessions). For sessions seen recently it also keeps the session name, the project folder (cwd), start and last-seen times, the last status and context percentage. Sessions older than 30 days are removed.
token	The token of the local server (file mode 0600 where the system supports it).
logs/hub.log	On Deck's own log, up to 512 KB per file, one previous file kept. Prompt text and tool inputs are not written to it.
telemetry.json, telemetry-queue.json, install-id, uninstall-ref	Usage-statistics state described below.

On Deck reads the session registry in ~/.claude/sessions and, from Claude Code transcripts, one record type that marks a conversation handed to a new session. It does not read anything else from transcripts.

On Deck changes ~/.claude/settings.json only when you press Install or Uninstall, and it makes a timestamped backup first. Deleting the data folder does not remove the hooks; use Uninstall in Settings for that.

Anonymous usage statistics

On by default. On the first launch a notice explains it. Nothing is sent until you have closed the notice, or it has been on screen for five minutes. Events recorded before that wait in a queue on your machine.

Turn it off: Settings → Privacy. When it is off, On Deck records nothing, clears the queue and removes the copy of the install id that the Windows uninstaller reads.

Every request carries: the random install id, app version, operating system and its version, CPU architecture and the interface language.

The install id is a random UUID created on the first launch. It is not derived from anything on your machine and is not linked to your name or account.

Events (the full schema is in src/main/telemetry/props.ts):

• app_installed: first launch of a new install, with the channel (dmg, nsis or dev) and whether it is an upgrade from a version without statistics.
• app_started: every launch.
• app_active: once per local day, with counts for that day: sessions seen, the most at the same time, questions answered here, notifications shown, terminals opened from On Deck.
• first_session_seen, question_answered, terminal_opened: the first time each happens, with no other data.
• feature_used: first use of favorites, groups, mute, rename, language, details or the menu bar popover.
• settings_changed: which setting changed. Only on/off values, language, theme, or a choice from a short list are sent. Numbers you typed are reported as just "changed".
• update_installed: the version you updated from.
• integration_installed, integration_install_failed, integration_uninstalled: the result of Install or Uninstall, with a short error code on failure.
• error: a handled technical failure as a fixed code (for example, that the local server could not start), and where it happened. At most one per code every six hours.
• survey_shown, survey_dismissed: that the survey card was shown or declined.
• telemetry_enabled: sent when you turn statistics back on.

Events are sent in batches of up to 100, about once a minute. Nothing in an event is free text.

Where they go: to the On Deck API, a server run by the developer (PostgreSQL, with Grafana dashboards). It is not a third-party analytics service. The address is in src/main/telemetry/api.ts. The server does not store IP addresses: the address is used only in memory, hashed, to apply rate limits. Nightly database backups are kept for 14 days.

Bug reports

A report is sent only when you open Found a bug? Send us a report (the bug icon in the top bar, or Settings → Support) and press Send report. The full diagnostic text is shown first, so you can read it. You can also Save to file instead; then nothing leaves your computer.

A report contains:

• the description you wrote and the contact you optionally typed;
• the app version, Electron and Chrome versions, operating system and version, locale, and time since start;
• the integration state: whether the hooks and status line are installed, whether the local server listens, the notification state, the path of the Claude Code settings file;
• the result of a live test of the hook script, and counters of requests the local server received since start;
• whether tools are found on the system (claude, sh or bash, curl, tmux, git, PowerShell), the claude --version output, and the values of CLAUDE_CONFIG_DIR and the Git Bash path where they apply;
• On Deck's own hook entries and status line from the Claude Code settings file, with other hooks only counted;
• a list of sessions by a shortened id (8 characters), status, source, times, context percentage, model, whether a terminal is known (process id, terminal app, tmux pane yes/no), number of background tasks, and whether a question is pending. No session names, prompts or project paths;
• the recent hook events, with time, shortened session id and the status they produced;
• the last 200 KB of On Deck's log.

Everything passes through a redaction step that removes the On Deck token, bearer values, bot tokens and your home folder (shown as ~). Paths to tools and to the hook scripts can still appear, with the home folder replaced.

Screenshot (optional). The screenshot is of the On Deck window as it is on screen. It is on by default when available, and the form says so. It can show session names and task text (the latest prompt is shown in the Task column). Untick Screenshot of the On Deck window to leave it out.

The report is stored on the On Deck server and forwarded to the developer's Telegram chat. The request also carries the install id, like every request.

Feedback

Send feedback sends the text you wrote (up to 4,000 characters) and the contact you optionally typed, together with the app version, system and install id. It is stored on the On Deck server and forwarded to the developer's Telegram chat.

Survey

After you have used On Deck on at least three different days, and at least seven days after the install, the app may show a short survey card: how you would feel without On Deck, and optionally what it gives you, what is missing, and a contact. Answers are sent only when you press the button. One answer is kept per install; a new one replaces it. The card can be declined, and then it is not shown again.

Update checks

Installed builds check the public release repository Y0LAREN/ondeck-releases on GitHub, 15 seconds after start and then every four hours. The check fetches release information only. Installing an update requires your click.

The request goes to GitHub, which sees the usual request data, such as your IP address. On Deck does not add its install id to it.

Windows uninstall page

On Windows, uninstalling may open a short page asking why you left. Your answer is stored on the On Deck server and forwarded to the developer's Telegram chat. It is linked to your install only while statistics are on.

Never sent

Automatically, On Deck never sends:

• prompts or any other conversation text;
• session names, project paths, file names or code;
• branch names, user names, or any text you did not type into a feedback, report, survey or contact field.

Two cases are your choice. If you write a name or path into a report, feedback or survey, or if the report screenshot shows one, it is sent when you click Send.

Your choices

• Turn statistics off: Settings → Privacy.
• Send nothing: do not press Send on reports or feedback, use Save to file, or untick the screenshot.
• Leave the survey: press the close button on the card.
• Remove the local data: quit On Deck, use Uninstall in Settings (to remove the hooks), then delete the data folder.
• Questions about your data: send feedback from the app.