Notch Crew

Privacy Policy

Last updated October 29, 2026. Notch Crew is made by tastedev, Republic of Korea ("we").

What stays on your Mac

Notch Crew reads the local session files and processes of the coding agents you run (Claude Code, Codex, Gemini CLI, OpenCode, Antigravity CLI, Pi, Hermes Agent, Cursor CLI, Ollama) to show their status, and the usage limits Claude Code gives its status line and Codex writes in its session files. To see what an agent asks, or which mode it is in, it also reads the text its terminal shows (its own windowless sessions, tmux, cmux, herdr, iTerm2 and Terminal), on your Mac. Messages between the sessions of a crew go from one to the other on your Mac. When you set up a crew with a Claude Code member, the app reads whether Claude Code has been let into the crew's folder from the trust marks in Claude Code's own ~/.claude.json; it reads nothing else there and saves nothing of it. Your conversations, code, file paths and tool arguments stay on your Mac. We never receive them. To read limits now (↻ in Usage, and Codex's when Usage opens and what it shows is older than five minutes), the app runs that agent's own usage command with no window: the agent asks its provider with your account, as when you run the command yourself, and nothing of it comes to us. When you press Update… beside an agent, the app runs that agent's own update command the same way, with no window: it downloads from where the agent is published, as when you run the command yourself, and what it prints stays on your Mac in ~/Library/Logs/Notch Crew.

If you add Claude Code accounts in Settings › Agent Accounts, each account is a folder on your Mac, ~/.notch-crew/claude-<id>, that the app makes, links your shared Claude Code settings into and checks before each use. You sign in to an account in Terminal, between Claude Code and its provider. To tell whether an account is signed in, the app runs Claude Code's own status command for it and keeps only whether and how it is signed in, with the email and plan Settings shows, which it does not save. Before an account signs in again or is removed, the app looks for running programs of yours that use its folder, reading only that one setting of theirs; removing an account signs it out where it can and moves its folder to the Trash. The app saves your accounts' names and folders, a list of those folders that its status line script reads, each account's last usage limits in its own folder (~/Library/Application Support/Notch Crew/usage) and, until an account's first sign-in finishes, that account's ID. It never reads, saves or sends a password, token or key.

If you open the Artifacts tab, the app builds a local index of artifacts your agents created (pages, files and images named in session logs) in ~/Library/Application Support/Notch Crew/artifacts/index.json. It contains paths, titles and session titles from those logs, not the conversation text. The list is rebuilt from logs on this Mac only; nothing is sent to us.

If you use boards in the main window, the tiles you make (to-do lists, goals and notes) and how each board arranges them are saved on your Mac, in ~/Library/Application Support/Notch Crew (tiles and boards). A board you delete leaves the sidebar but stays in this board history on your Mac, and its tiles stay under Removed Tiles. When you make a crew, the app keeps your last six crew setups for Recently Used in the same folder (crew-recents.json): each one's template text, folder and permission choice, and when you used it. Remove from Recents deletes one from it. The app also keeps a history of the messages it types into agent sessions for you, such as a crew's messages, a lead wake-up and tile notices: it saves each message's length and a fingerprint, not its text (runs). A note you were editing that changed underneath you is kept there until you use or discard it. To bring your windows back when the app restarts it also remembers which windows were open, where they were and what each one showed (such as a board, a crew, a session or a recent item), and to keep your session list in the order sessions began it remembers when each session began or was first seen; these stay in the app's preferences on this Mac, hold no conversation text and are not sent to us. A tile you connect to an agent can be read by that agent, so its text reaches the agent's provider like anything else in that conversation. None of this is sent to us.

Crew lessons are short lines a member proposes, kept in its role's Markdown file on this Mac (~/Library/Application Support/Notch Crew/roles) or in a project's .notchcrew/roles folder. Members are told not to include secrets or quote your messages. Before review or storage, the app removes control and hidden formatting characters from a proposal and masks recognized secret patterns; each proposal is at most three lines of 200 characters each. By default you review each proposal before saving it. You can choose Keep lessons without asking in Settings › Crews for crews with Member Lessons on; it is off by default. The Lessons list shows the saved lines and lets you remove one, keeping up to three previous file versions as local backups first. Project role files can become part of your git working tree; the app does not stage or push them. Role instructions, including saved lessons within the 4,000-character brief limit, reach that agent's provider in later briefs like anything else you tell it. To collect lessons, the app reads the submitted lines and selected role files; it does not read conversation transcripts, credential stores or the process environment. None of this is sent to us.

Kit tiles resolve scoped app data locally while visible and keep resolved source rows and file previews out of saved board documents and agent replies. A kit tile also reads folder listings, git status, and the artifact index for the board's places and sessions.

Using a web view connects the app to that site. An Allow All web view tile can keep that site's sign-in. Turning Allow All off or removing the tile clears it. The board keeps only the address, the allowed list, and the level. None of the page is sent to us. The macOS screen sharing picker is a system window and can stay open after the web view closes.

If you make a workflow on a board, it is saved next to that board on your Mac (in boards): its steps' titles and instructions, done-when items, the files they may read and write, which session does each step, and the board's goal. When it runs, the app types each step's instruction into the session of the member you confirmed, like a crew's messages, so it reaches that agent's provider like anything else in that conversation; the history in runs keeps each instruction's length and a fingerprint, not its text. What members report back is saved with the run in runs: a summary, evidence for each done-when item, commit IDs and declared files, the tests they say they ran and what they couldn't check (a report is at most 1 MB); these are not cleaned up automatically yet. To check a report or a declaration, the app runs git in that member's worktree to read only the commits and files named in it, with git hooks and your git settings ignored; it never fetches or changes anything. To start or resume a run, the app reads which program and version each member runs and which terminal it is in. While a workflow runs, it also reads the list of its screen sessions about once a second, the bottom of a member's screen right before typing an instruction (to see that the input is empty and which permission mode is on), and the last 8 KB of each member's screen every 30 seconds to notice provider problems such as a usage limit; it keeps only what it saw, not the text. None of this is sent to us.

Kept crew decisions

When Keep Decisions is on for a crew, you can review and keep short person decisions on this Mac: a topic key, cleaned question and answer lines, source and confirmation times, delivery status and replacement history. New crews start on; existing crews start off. Material records contain the path you confirm, full SHA-256, size and verification time, not the file contents or an attachment copy. A reported past receipt time is kept separately. Terminal proposals are not saved until you confirm them, and a past approval never permits a new action.

Confirmed records are kept in ~/Library/Application Support/Notch Crew/decisions as one private snapshot per crew, up to 200 records and 512 KiB per crew, 100 crews and 32 MiB in total. Records are not automatically expired or evicted. Decision text is not copied into run history, board history or role files. Current confirmed facts can be sent to that crew's agent for briefs, handoff and context recovery, so they reach the agent's provider like other conversation text. We do not receive them. An app-owned Claude lead may receive an additional per-launch hook configuration containing the app command and crew/seat identifiers, not decision text or a copy of your agent settings.

Remove and Clear replace the snapshot without an app backup or an Undo copy of the deleted text. Crew deletion offers to delete its decision file. Turning the feature off cancels pending decision messages and unconfirmed cards while preserving kept records until you delete them. Already delivered provider context and system backups, including APFS or Time Machine snapshots, cannot be recalled. A failed or unconfirmed delete is reported as such. Fake, quiet and snapshot modes create no decision files.

What the app sends

Payments

Paddle.com is the merchant of record: it takes your payment, handles tax and sends your receipt. See Paddle's privacy policy. We receive the order details (email, country, amount) so we can help you.

This website

notchcrew.com is hosted by Vercel. It sets no cookies. It uses Vercel Web Analytics to count page views and clicks on Download: no cookies and no personal identifiers, and a visitor is told apart only by a hash of the request that is discarded after 24 hours. Each count keeps the page, the referrer, the country and city, and the browser, OS and device type. See Vercel's notes on Web Analytics privacy.

Contact

dev.tastekim@gmail.com