Jack RuntimeTelemetry
Effective date: 22 October 2026
Jack Runtime reports how it is used, so we can help you when something goes wrong and keep it working as the harnesses it drives change, often weekly. This page lists everything it sends. Nothing else leaves your machine for us.
What it never sends
Whatever the event: prompts, replies and chat text; file names and paths; the names you give repositories, projects, agents and teammates; the wording of hard limits; your documents; command lines and environment variables; your email address.
The product holds the list of events and properties in its code and drops anything not on it.
How we tell installs apart
The first time Jack Runtime runs, it makes a random install ID and keeps it in ~/.jack. It is not derived from you, your machine or your accounts. It links to an account only if you sign in for the hosted relay. jack telemetry status shows your install ID and whether telemetry is on.
Properties on every event
| Property | What it is |
|---|---|
install_id | A random ID made the first time Jack Runtime runs, kept in ~/.jack. It is not derived from anything about you or your machine. jack telemetry status shows it. |
product | Which product sent the event: runtime or work. |
surface | Where it happened, such as the command line, the daemon or the desktop app. |
app_version | The version you run. |
os, arch | Your operating system and processor architecture. |
plan | Your plan: Free, Pro, Team or Enterprise. |
schema_version | The version of this list of events. |
country, region | Worked out from your IP address when the event arrives. The IP address itself is then discarded, never stored. |
Events
| Event | When it is sent, and what it carries |
|---|---|
command_executed | You run a jack command.The command and the names of the flags you used, never their values. |
command_completed | A jack command finishes.The command, its exit code, how long it took and whether it succeeded. |
daemon_started | The Jack Runtime daemon starts.Nothing beyond the common properties. |
tool_called | A harness or app calls one of Jack Runtime's MCP tools.The tool, the calling harness or MCP client by product name, the outcome, any error code and how long it took. |
session_state_changed | A worker session changes state, such as from working to waiting.The old and new state, the worker's harness, the orchestrating harness, whether Jack Runtime started or attached to the session, and how deep it sits under other workers. |
turn_completed | A worker finishes a turn.The harness, how many events of each type the turn had, token counts and how long it waited for permission. Never what was said. |
install_snapshot | Once a day.Which harnesses are installed and logged in, and how many sessions, groups, projects, agents, routines, tasks and hard limits you have. Counts only, never names. |
relay_connected | Your Jack Runtime connects to the hosted relay.Nothing beyond the common properties. |
update_checked | The product checks for a new version.The update channel and the version it found. |
update_installed | A new version is installed.The old and new version and the channel. |
Crash reports
When Jack Runtime hits an internal error, it sends a crash report to Sentry: the error, the stack trace, the version, your operating system and the same install ID. Stack traces show paths inside Jack Runtime, not your own files, wherever the build allows. Sentry does not store your IP address.
When you first run it
The first time you use Jack Runtime in a terminal (never in CI or a script), it tells you once that telemetry is on, what it collects and how to object, with a link to this page.
Turning it off
Telemetry stays on in the Free, Pro and Team plans, because it is how we support you. Enterprise organisations can have telemetry turned off for the organisation. There is no switch for it in the app.
You can object at any time under GDPR Article 21(1). Email [email protected] with the reasons that apply to your situation and the install ID from jack telemetry status. We review your objection and reply by email. We delete what we hold under your install ID if you ask.
Where it goes and how long we keep it
Events travel through a relay on our own domain to PostHog, and crash reports to Sentry, both in their EU regions. Your IP address is used only to work out your country and region, then discarded. We keep usage events for one year and crash reports for 90 days. We never sell this data, share it for advertising or use it for anything but the purposes on the legitimate interest assessment.
Legal basis
Our legitimate interest in supporting you and keeping Jack Runtime working (GDPR Article 6(1)(f)). The legitimate interest assessment weighs that interest against yours. Who we are, and the rest of how we handle personal data, is in the privacy policy.
Your rights
You can ask for a copy of what we hold, and to correct, delete or restrict it. Email [email protected] and we will answer within one month. You can also complain to the Norwegian Data Protection Authority,Datatilsynet, or the authority where you live.
Changes
A new event or property appears on this page before a version sends it, and the date above changes. Every event carries schema_version, so old and new versions are told apart.