Appearance
Usage data and privacy
Clusto can send anonymous usage statistics so we know which parts of the app are worth improving. It is optional and off until you opt in. This page lists exactly what is collected, what never is, and how to control it. The feature ships behind the telemetry.usage feature flag; when the flag is off, nothing is collected and the prompt does not appear. Settings > Privacy stays available while the device still has an install id, so you can always delete what was sent.
Opt in, opt out
- On first launch the app asks "Help improve Clusto?" with two equally weighted buttons: Share usage data and No thanks. Nothing is recorded or sent before you choose. Closing the dialog without choosing asks again on the next launch.
- Change your mind any time in Settings > Privacy: the Share anonymous usage data checkbox turns collection on or off. Turning it off deletes anything not yet sent.
- Your choice is stored on the device only. Each device decides for itself.
What is sent
Every upload carries a random install id, the app version, the platform (windows, linux, macos, android, ios, web), the form factor (desktop, phone, tablet), and a list of events. An event is a name plus properties from a fixed list of allowed values. Anything outside this list is rejected by the server.
| Event | Property | Allowed values |
|---|---|---|
app_started | none | - |
daily_active | none | - |
view_opened | view | connect, sessions, session, workspace, cluster, projects, teams, team, settings, logs, tasks, reports, files, notes, agent_docs, knowledge, ssh, chats, other |
feature_used | feature | command_palette, detached_window, notes_edit, file_upload, file_download, git_commit, ssh_connect, tunnel_connect, task_run, team_run, report_open, cloud_sync, theme_change, other |
session_created | kind | terminal, agent |
provider | shell, claude, codex, opencode, copilot, openrouter, ollama, custom, ssh, other | |
chat_started | provider | claude, codex, opencode, copilot, openrouter, ollama, custom, assistant, other |
cluster_shape | nodes | 1, 2-3, 4-10, 11+ |
sessions | 0, 1-5, 6-20, 21+ | |
connect_result | result | ok, auth, timeout, tls, refused, other |
transport | ws, wss, tunnel | |
update_installed | from, to | an app version number such as 1.14.50 |
onboarding_step | step | first_launch, connected, first_session, first_chat, signed_in |
Cluster size and session counts are sent as ranges, never exact numbers.
What is never sent
- File names or paths, commands, prompts, or model output
- Project, session, node or host names
- Error text
- Your account id or license key
- Your IP address (never stored with the events; a short-lived abuse rate limit sees it and forgets it within 24 hours)
Usage data is sent without your account token, so it cannot be tied to your Clusto account.
Install id
When you opt in, the app creates a random id for the device. It is not derived from anything about you or your machine and is not linked to your account. When you opt out or delete your data, the id is discarded and a new random one is created if you opt in again.
Retention
- Raw events are kept for 90 days.
- Aggregated statistics (counts and trends, no per-device detail) are kept for 25 months.
- Install records not seen for 25 months are deleted.
See what is sent
In Settings > Privacy, View what is sent shows the usage data waiting on this device, exactly as it will be uploaded. Events are queued locally, uploaded about every 15 minutes and when the app is hidden or closed, dropped after 7 days if they cannot be sent, and capped at 500 queued events. The same view is in the F1 command palette as View usage data queue.
Delete your data
Settings > Privacy > Delete my usage data deletes every usage event stored on clusto.app for this device's install id and turns sharing off. It cannot be undone. Data from other devices is not affected; do the same on each one.
Downloads and update checks
Separately from the app's usage statistics, the download server (dl.clusto.app) keeps an aggregate log of downloads and update checks. It records the client version and the OS and architecture taken from the User-Agent. The log contains no IP addresses and no query strings, only counters, and it is not linked to any account or install id.
Privacy policy
The full policy is at clusto.app/legal/privacy.