Privacy

Last updated

J5 Code is open-source software maintained by Jackson Miller. It runs on your own machines. There is no hosted J5 service and no J5 account, so your projects, conversations, and files are never sent to the maintainer. They leave your machines only when you run an agent, as described below.

Usage data

The J5 Code server sends usage events to PostHog, an analytics service, so the maintainer can see how the software is used. Events are stored in the United States and kept for 14 days.

The events are:

  • the server starting, with a count of your threads and projects;
  • a client connecting, with the kind of client (web, desktop, or mobile), its version, its operating system, the browser name on web, the device model and operating system version on mobile, and how it connected;
  • a thread starting, and a turn being requested;
  • a turn starting, with who asked for it (you, an agent, or J5 Code itself), where the request came from (a client, an agent tool, or the server), whether a scheduled task or a background wake-up started it, whether it is the thread's first turn, and whether the thread was started by an agent or is a seat in a Crew;
  • an ask ending, with how it ended (answered, withdrawn, or dropped), the kind of participant that asked and that was asked (a person, an agent, or a script), its urgency, and how long it was open;
  • a playbook run starting or ending, with the number of steps, how many steps name a persona, whether a Crew runs it, and at the end whether it completed or was cancelled, the step it reached, and how long it ran;
  • a Crew roster being approved or declined, with the number of seats asked for and approved, how many seats you added, removed, renamed or changed, whether it follows a playbook, and how long the decision took;
  • a Crew's seats launching, with the number of seats, how many use a persona, a worktree or full access, how many different models they use, and how many failed to start;
  • every fifteen minutes, counts of your open threads, threads that are working, working threads an agent started, queued turns, live Crews, the seats in the largest Crew, and asks waiting on you and on agents;
  • a turn finishing, with the provider, model, reasoning effort, permission mode, result, duration, and token totals.

Each event also carries the J5 Code version, the server's operating system and processor architecture, and the WSL distribution name if there is one.

If you set J5CODE_TELEMETRY_TAG in the server's environment, its value is sent with every event. It is unset unless you set it.

Events are tied to an identifier: a one-way hash of your Codex account ID, or of your Claude user ID if there is no Codex account, or of a random ID created on your machine if there is neither. The original ID is never sent. IP addresses are not stored.

Events never include prompts, responses, file contents, file or project names, authentication tokens, or conversation IDs.

To turn this off, set T3CODE_TELEMETRY_ENABLED=false in the server's environment before starting it.

Other connections J5 Code makes

  • Update checks. J5 Code checks GitHub for new releases and downloads them from there. GitHub sees the request, under its own privacy policy.
  • Your agent providers. When you run an agent, your prompts and code go to the provider you chose (such as OpenAI, Anthropic, or Cursor) through that provider's own tool, under your account and their terms. J5 Code's maintainer never receives them.

The mobile app

The mobile app connects to J5 Code servers you add and stores those connection details on your device. It contains no analytics and sends nothing to the maintainer.

Contact

Questions or requests about this page: hello@j5.codes.