Privacy
Version 1.6. Last updated 10 November 2026.
Your code, your prompts and your agent transcripts never leave your Mac. CrewTower reads a great deal locally and sends almost none of it anywhere.
Three features make network requests, and this page lists all three: the optional usage meter, which talks to Anthropic using your own Claude Code login; the free trial and license activation, which talk to us and to our payment provider; and update checks.
The optional Claude Code plugin behind Tell Claude, off until you turn it on, talks only to the app on your Mac and makes no network request. The Claude Code plugin below says what it sends and does.
In the app there is no analytics, no crash reporting, no account, no advertising and no tracking of any kind. Our servers do count three things without naming anybody: a trial starting, a license being activated and the app being downloaded; What our servers count below says exactly what each count holds. This website counts visits and records how its pages are used without naming anybody, and uses Google Analytics cookies only if you allow them; the section further down called this website says exactly what that means.
Who this is
CrewTower is made and sold by Said Altan, an individual based in Ontario, Canada. For anything on this page, including a request to see or delete your data, write to support@crewtower.app.
Payment is not handled by us. Polar is the merchant of record for every purchase; see Buying the app below.
What the app reads on your Mac
CrewTower's job is to watch coding agents, so it reads a lot of what those agents do. All of it stays on the machine. None of it is transmitted anywhere by us, and none of it is written anywhere except inside your own home folder.
| What | Where it comes from |
|---|---|
| Hook events: session ids, the working directory, your prompts, tool names and the full tool input, such as the command a shell tool wants to run | The agent sends these to a Unix socket in ~/Library/Application Support/CrewTower, readable only by your user account |
| Agent transcripts: assistant replies, tool activity, context usage, session titles | Read-only tailing of the JSONL files your agent already writes on disk |
| Your agents' hook configuration, plus a backup of each file before it is changed | ~/.claude/settings.json, ~/.codex/hooks.json, ~/.cursor/hooks.json, ~/.gemini/settings.json, ~/.qwen/settings.json |
| Session state so the panel survives a restart, including working directories and the last line of activity | Written to sessions.json in the same support folder |
| A list of running processes: process ids, terminal device, and parts of the command line | /bin/ps, matched locally against a fixed list of agent names, so an agent with no hooks still shows up |
| Your Claude plan name, shown in the usage strip | ~/.claude.json |
| Your license key and license token | Two plain files in the support folder |
| Only if you turn on the Claude Code plugin: the session details listed in the next section | The plugin sends them to a second Unix socket, bridge.sock, in the same support folder |
CrewTower does not read your source files. It sees a file's contents only in the narrow case where an agent is asking you to approve writing them, because that is the text you are being asked to approve.
The Claude Code plugin, if you turn it on
Sending a Claude Code session its next prompt from the notch, stopping it, compacting it and showing its context breakdown need a small Claude Code plugin, crewtower-bridge, whose code is a Claude Code mod. It is off until you turn it on, from the offer on a Claude card or in Settings > Integrations.
Turning it on copies the plugin from the app into ~/Library/Application Support/CrewTower/mod and runs your own claude command line to install it for your user account: claude plugin marketplace add with that folder, then claude plugin install crewtower-bridge@crewtower --scope user. Claude Code records the install in its own settings; CrewTower does not edit them for this. New Claude Code sessions, in the terminal and in Claude Desktop's Code tab, then load it.
Inside each session the plugin sends CrewTower:
- When the session starts and ends: its working directory, model and Claude Code version, which terminal it runs in so Jump can find it, and where the plugin itself is installed.
- The first 300 characters of each prompt, and the first 300 and the last 800 characters of each of Claude's answers.
- The name of each tool Claude calls and whether the call was allowed, denied or asked about, and when a permission prompt opens and is answered.
- The context, usage and cost figures Claude Code reports for the session, and, when you open the breakdown, Claude Code's own breakdown of the context. To estimate how much of it is tool output, the plugin reads the session's messages where they are and sends only a token count.
- If something inside the plugin fails, a short error message.
All of it goes to the Unix socket bridge.sock in the support folder. That socket can be opened only by your user account, and every request has to carry the secret in bridge.secret, a file only your account can read, which CrewTower writes anew each time it starts listening. The plugin's one network call is addressed to that socket, so it sends nothing over the network and nothing it sends leaves your Mac.
In the other direction, the plugin does only what you press on a card: it submits the prompt you typed to that session as yours, through Claude Code's own mods API rather than as keystrokes; it stops the running turn; it compacts the conversation; or it measures the context. It never answers a permission prompt. Your hooks, and you, still decide those.
Turning it off runs claude plugin uninstall and claude plugin marketplace remove and deletes the plugin's folder; so does Remove CrewTower in Settings. You can read the plugin before turning it on: it is one TypeScript file, hooks/register.ts, inside CrewTower.app/Contents/Resources/BridgeMod/crewtower-bridge, and claude plugin validate on that folder lists every event it hooks and every call it makes.
What leaves your Mac
1. The usage meter, to Anthropic. Optional.
If the usage strip is on, which it is by default, CrewTower shows how much of your Claude subscription window you have left. To do that it reads Claude Code's own login token from ~/.claude/.credentials.json, or from your login keychain by running /usr/bin/security find-generic-password -s "Claude Code-credentials" (if you set CLAUDE_CONFIG_DIR, from the same places Claude Code then uses: that folder's .credentials.json and the keychain item Claude Code names after it), and calls api.anthropic.com/api/oauth/usage with it about every five minutes. CrewTower never refreshes, renews or rewrites that token. When it has expired, CrewTower sends nothing at all and waits for Claude Code to renew it, which Claude Code does the next time you use it.
Said plainly: the app uses your existing Claude Code credentials, on your behalf, against the same Anthropic servers the Claude Code CLI already talks to. Those credentials never reach us and are never written anywhere new. What Anthropic does with the request is covered by Anthropic's privacy policy.
You can switch the usage strip off in Settings, and then none of this happens. If you pick Codex as your usage source instead, CrewTower asks a codex app-server process on your own machine (the copy inside the ChatGPT app, or the Codex CLI) over local JSON-RPC and makes no request of its own.
2. The free trial, license activation and renewal, to us.
When you start the free trial, when you activate, and at most once a day afterwards, the app sends some of these to license.crewtower.app:
- Your license key. It is not sent for the trial, which needs none.
- A device hash. This is your Mac's hardware identifier (
IOPlatformUUID) combined with a fixed secret and put through SHA-256. The identifier itself never leaves your Mac and the hash cannot be turned back into it. - A label for the activation, which is your Mac's name as it appears in Sharing settings. This is often a person's name, for example "Said's MacBook Pro". It exists so that a support email about a lost machine can be matched to the right activation. It is sent only when you activate.
- The version of CrewTower you are running and its build number.
- Whether the app was installed with Homebrew or by hand: the word
homebrewordirect, worked out on your Mac by checking whether Homebrew's own record of the install points at the app. It is sent only when the trial starts and when you activate.
That request is handled by a small Cloudflare Worker of ours. For a trial it signs a token that runs out 72 hours after this Mac's trial began. For a license it forwards the activation to Polar, signs a short-lived token and returns it. The token is signed proof that this license belongs to this Mac, it contains the device hash, it lives on your Mac, and it lets the app confirm your license offline for up to three weeks if we are unreachable.
The Worker writes down two things. The first is when this Mac's trial started: the device hash, the time the trial began and whether the app was installed with Homebrew or by hand. That is what keeps the trial to one per Mac, even after a reinstall, so it is kept with no expiry date. It holds no key, Mac name, email address or IP address.
The second is which version of the app your license last ran: the version, the build number and the day it was last seen, stored against your license's activation. It is associated with your license, so we can see which version a given customer is on, and we use it only to know how many people have moved to the newest release and who an old version's bug may still affect. The Worker stores no key, device hash, Mac name, email address or IP address with it, and the record is deleted after 90 days in which your license does not check in.
Our Worker does not log request bodies. Cloudflare necessarily processes the request itself, including your IP address, as our hosting provider.
The Worker also counts trials and activations in PostHog; What our servers count below says what that count holds.
This one is not optional. It is what a paid license is, and what a trial is.
3. Update checks, to our download host.
CrewTower checks about once a day whether a newer version exists, using Sparkle, the standard update framework for Mac apps. It fetches dl.crewtower.app/appcast.xml, which is a static file on Cloudflare R2.
Sparkle's optional "anonymous system profiling" is switched off, so no report about your machine is sent. What the request unavoidably reveals is what any web request reveals: your IP address, and a user agent string naming the app version and your system's Darwin version.
When an update is installed, Sparkle downloads it from the same host. A download of the full app is counted like any other download, as described next.
What our servers count
We count how many people start the trial, how many go on to buy, and how many download the app, so we can tell whether the trial and the website are working. The counting happens on our servers, after the request has already been answered, and never slows down or holds up a trial, an activation or a download. The counts go to PostHog, the same service that counts visits to this website.
- A trial starting. Sent once per Mac, the first time that Mac starts its trial, never again after a reinstall. It carries the device hash and, if the app said, whether it was installed with Homebrew or by hand.
- A license being activated. Sent once per activation. It carries the device hash, whether the app was installed with Homebrew or by hand if known, whether this Mac had a trial, and if it did, whether the trial had run out and how many hours had passed since it began.
- A download of the app. Sent when a download of the CrewTower disk image from
dl.crewtower.appstarts, from a browser, through Homebrew or as an update; downloads by crawlers, link previews and scripts are not counted. It carries whether the download came through Homebrew or not, whether a browser, Homebrew or the app's updater made it (read from the request's user agent, which is not stored), the version downloaded, and, for an update Sparkle downloads, that it is an update. It carries no device hash: each download gets a random identifier of its own, so two downloads can never be linked to each other or to anyone.
Because a trial and an activation from the same Mac carry the same device hash, we can see that a trial was followed by a purchase. That is the purpose of it. The device hash cannot be turned back into your Mac's identifier, and it is never joined to your name, email address or license key. PostHog is told not to build a profile around it. Your IP address is not passed on to PostHog with any of these counts.
Buying the app
Purchases go through Polar, which acts as merchant of record. In their own words, you buy the product from Polar, not from us. They collect your email address, billing address, tax details and payment card information at checkout, and they handle sales tax and VAT. See Polar's privacy policy and their buyer terms. Polar uses Stripe to process cards.
We never see your card details. As the seller behind Polar we can see the order record in their dashboard, which includes your email address, your country and the license key issued to you, and after activation the device hash and Mac label described above.
Who else is involved
- Cloudflare hosts this website, the license Worker, the update files and the Worker that counts downloads of them.
- Polar, and Stripe behind it, handle payment and issue license keys.
- Anthropic, only if the usage strip is on, and only with credentials you already gave to Claude Code.
- PostHog counts visits to this website, and receives the trial, activation and download counts our servers send, described in What our servers count. The app itself never contacts it.
- Google, through Google Analytics, also counts visits to this website, and only to this website. It sets cookies only if you allow them in the banner, and it receives nothing from the app.
That is the entire list. Nothing you do inside the app is sent to anyone for advertising or profiling, and nothing about how you use it is counted: the only counts are of a trial starting, a license being activated and a download, described above.
How long anything is kept
Our license Worker keeps two things: when each Mac's trial started, with its device hash and how the app was installed, with no expiry date, because forgetting it would hand that Mac a second trial; and the app version your license last ran, with its build number and the day, for 90 days after your license last checks in. Everything else in a request it holds only for as long as it takes to answer it. Ask us and we will delete your Mac's trial record. Your activation record, which is the key, the device hash and the Mac label, lives with Polar for as long as the license does. Delete your license files or delete the app and the copies on your Mac are gone.
If you want the activation record removed, write to us and we will remove it. Removing it means the license stops working, so we will normally suggest doing it as part of a refund.
Your rights
Under Canada's Personal Information Protection and Electronic Documents Act you can ask what personal information we hold about you, ask for it to be corrected, and challenge how we handle it. If you are in the European Union or the United Kingdom you additionally have the rights the GDPR gives you, including access, correction, deletion, restriction, portability and objection.
Either way the address is the same: support@crewtower.app. There is one person reading it, so please say what you want in plain words and it will get done.
The legal basis for the license data is that we cannot deliver a paid license without it. The legal basis for the usage meter is your choice to leave it on. The legal basis for the trial record and for the counts in What our servers count is our legitimate interest in giving each Mac one trial and in knowing whether the trial and the website lead to purchases; none of it names you.
Children
CrewTower is a developer tool sold to adults. It is not directed at children and we do not knowingly collect anything from them.
This website
The site sets no cookies unless you allow them. Cloudflare, as the host, processes requests to the site, and the one thing loaded from anyone else's domain is Google's analytics script, described below.
It does count visits. We need to know whether anybody is arriving and whether the people who arrive get as far as downloading, and there is no way to know that without counting. The counting is done twice, by PostHog and by Google Analytics.
Google Analytics works like this. When you first arrive, a banner asks whether to allow its cookies. Until you answer, and if you decline, it sets no cookies and receives only anonymous pings that are not tied to you across pages or visits. If you allow, it sets its usual _ga cookies so your visits can be counted as one visitor, and Google receives the pages you view, which browser and country the request came from, and which site you arrived from. Your choice is kept in your browser and you can change it by clearing this site's data, which brings the banner back.
PostHog is set up like this:
- No cookies. The one identifier involved is a random string kept in your browser's local storage so that four pages read in a row are counted as one visit rather than four. It is not a name, it is never sent to anyone else, and clearing site data removes it.
- Your browser never contacts PostHog. The counting requests go to
crewtower.app/ingestand this site passes them on. - Your visit to this website is recorded and can be played back. That means the pages you looked at, how far down each one you scrolled, and what you clicked, redrawn afterwards from the page itself. It is not a video and it is not your screen: nothing outside this site's own tab is in it, and there is no camera, no microphone and no keystroke log. There is also nothing on this site to fill in, and any field that ever appears here is blanked out before the recording leaves your browser.
- No profiles and no accounts. What is stored is which pages were viewed, how they were used, which browser and country the request came from, which site you arrived from, and whether the Download or Buy button was clicked. Your IP address is passed on so that the country can be worked out from it. None of that is a name, and none of it is joined to anything.
- If your browser sends Do Not Track, nothing is counted at all.
This is the website only. The app on your Mac reports nothing to PostHog or Google; what our servers count about trials, activations and downloads is described in What our servers count.
Changes
This page is dated and versioned. When it changes, the date at the top changes with it, and the previous wording stays in the site's public git history. If a change materially widens what we collect, we will say so in the app's release notes rather than quietly editing this page.