TrekWhat Trek sends, and what it never does.
Trek asks once whether it may share anonymous usage data. Say no and it sends nothing, except feedback you choose to send. Either way it never sends your prompts, code, file names, paths, transcripts, keys or account emails.
The question Trek asks
On the first launch after setup, Trek asks whether it may share anonymous usage data. If you used an earlier version, it asks you once too. You can change your answer at any time in Settings, Privacy, and that page shows exactly what was sent last.
- With a yes, Trek shares anonymous usage counts (how often Trek opens, which agents and tools are used), crash and error reports, and the app version, operating system and architecture.
- Trek never shares prompts, code, file names, paths, transcripts, keys or account emails.
- With a no, nothing is sent, ever, except feedback you send yourself.
Nothing is sent before you answer. Nothing is sent if the DO_NOT_TRACK environment variable is set; Trek then doesn't ask, and the Privacy page says why.
Where it goes
Usage data, crash reports and feedback go to PostHog, on its US cloud (us.i.posthog.com). The key built into Trek can only add events. It cannot read them.
What is sent, exactly
Every usage event carries the app version, the update channel (stable, beta or nightly), the operating system and its version, and the architecture. These are all the events there are:
| Event | When, and what it adds |
|---|---|
| Install | The first launch after a yes, once. It says whether Trek was already set up on this computer. |
| App opened | A launch, at most once a day. |
| App updated | The first launch of a new version, with the old and new version numbers. |
| Feature used | The day after: one count for each agent you messaged and each tool panel you opened that day. The names are Trek's own words, such as claude-code or terminal, never anything you typed. An agent you added yourself is counted as "other". |
| Crash | The launch after a crash: the error message, where in Trek's own source it happened, and a backtrace. |
| Feedback | Only when you send feedback. See below. |
Who you are to Trek
A random install id, made the first time you say yes. Nothing else about you or the install is known. Each event tells PostHog not to make a profile of a person and not to look up a country or city from the address it came from. Reset in Settings, Privacy makes a new id and drops whatever was waiting to be sent under the old one.
What is removed before a crash report or a log is sent
- Secrets you gave an agent during the run.
- Anything shaped like a key or a token, including private keys and passwords inside web addresses.
- Email addresses.
- Your project folders and any other path on your disk, apart from system locations such as
/usror/Applications. Your home folder becomes~.
Feedback
Help, Send Feedback opens a form: what happened, whether it is a bug or an idea, an optional email for a reply, and Include diagnostics, which is on by default. The form says in a line what it will send, and shows all of it on request before anything goes. Sending it is the consent, so it works even if you said no to usage data.
With diagnostics, feedback carries the app version, operating system and architecture, up to 20 recent warning and error lines, and the last 200 lines of Trek's log, cleaned as described above. Without diagnostics it carries none of that. If you said no to usage data, feedback is sent under a new random id each time, so it can't be tied to anything.
The form can also open a new issue on GitHub with your message and diagnostics filled in. It never includes your email there, because an issue is public.
What stays on your computer
In a telemetry folder in Trek's data folder: your answer, the install id, today's counts, events waiting to be sent (at most 500; each is dropped after five failed tries or a week), and a copy of the last request exactly as it was sent. A crash also leaves a report in the data folder. Until you answer the question it waits there; with a yes the next launch sends it, and with a no it is deleted.
The iPhone app
Trek for iPhone has no usage data and no crash reports. It has the same feedback form, which sends your message and, with diagnostics, the app's version, the iOS version and the architecture.
What else Trek connects to
- Your agents and models. Your prompts and code go to the agents and model providers you choose, through their own tools or your API keys, as they do in a terminal. Trek never reads or stores the logins of the agent CLIs it drives.
- Updates. Trek checks its releases on GitHub for a new version of itself, and public package feeds for new versions of your agents' command-line tools.
- Your phone. The iPhone app connects straight to your computer over your Wi-Fi or Tailscale. No Trek server sits in between. Push notifications go through ntfy, only if you turn them on.
This website
This site sets no cookies and carries no analytics, trackers or third-party fonts. Its pages, type and pictures all come from this domain, which is hosted on Cloudflare; like any host, Cloudflare receives the request your browser makes in order to answer it.
The home page makes one request elsewhere: your browser asks GitHub's public API for Trek's latest release, so the download button can point at the right file. That request goes to GitHub and is covered by GitHub's own privacy statement. With JavaScript off it isn't made, and the button leads to the release page.
Questions
Write to support@trekdesktop.com. The full technical account, with every property of every event, is in docs/PRIVACY.md in the repository, and the code that sends it is in crates/trek-telemetry.
Last updated 11 November 2026.