Your Mac, Your Data
Privacy & Local Data
Understand what AskTerminal reads, what it changes, and which network connections come from the command-line tools you choose to run.
Local-first by design
AskTerminal organizes local project folders and the session history already maintained by Claude Code and Codex. Core project, terminal, planning, approval, and analytics features do not require an AskTerminal-hosted backend.
Data the app uses
| Data | Why it is used |
|---|---|
| Project folders | Open terminals, browse files, display Git state, and associate sessions with a project. |
| Claude Code and Codex history | List sessions, resume work, show conversations, and calculate analytics. |
| AskTerminal app data | Remember projects, plans, Quick Agent preferences, and app state. |
| Agent configuration | Show and manage project instructions, skills, agents, and approval hooks. |
Changes AskTerminal can make
- Register project folders and save app preferences.
- Create or update project plans, skills, agents, and instruction files when you edit them.
- Install or remove Claude Code and Codex hooks when you choose those actions in Settings.
- Run terminal and Git commands that you initiate or approve.
Network activity
Claude Code, Codex, Git, package managers, and commands launched inside a terminal may connect to their own services. Their privacy policies and account settings apply to that traffic. AskTerminal’s local-first design does not make third-party CLI traffic local.
Remove access
Uninstall hooks under Settings → Hooks. Remove projects from your normal workflow and delete AskTerminal-created project data only when you no longer need its plans or configuration. Removing AskTerminal does not automatically delete Claude Code or Codex history owned by those tools.