How Axon uses your accounts, where your data lives, and how to take back control at any time.
Every integration is read-only. Axon requests the minimum permissions needed and cannot modify, delete, or create anything in your accounts.
Search, list, and read email messages and metadata from the command line.
Axon never sends, modifies, or deletes emails.
Search for files, read document content, and export Google Docs, Sheets, and Slides as text.
Axon never creates, modifies, or deletes files.
List and search calendar events to view your schedule and upcoming meetings.
Axon never creates, modifies, or deletes events.
Search messages, read channel history, browse threads, and list users in your workspace.
Axon never posts messages, creates channels, or modifies workspace settings.
Search pages, read content, and query databases in your workspace.
Axon never creates, edits, or deletes pages or database entries.
View contacts, deals, leads, and tasks in your CRM.
Axon never creates, updates, or deletes CRM records.
Clone repositories, list branches, view commits, and check status across your repos.
Axon never pushes code, creates PRs, or modifies repository settings.
Axon is a local command-line tool. When you run a command, it calls each service's API directly from your machine. Nothing passes through an Axon server — because there isn't one.
API calls go straight from your device to each service. No proxy, no relay, no man-in-the-middle.
OAuth tokens live on your filesystem at ~/.axon/. Never transmitted anywhere.
No analytics, no telemetry, no usage tracking, no crash reporting. We don't run servers that receive your data.
Axon includes built-in domain filtering so you control whose content enters your workflow. When enabled, only emails, Drive files, and calendar events from approved domains are shown — everything else is excluded.
Approve trusted domains. Only content from these senders is displayed.
Block unwanted domains. Content from these senders is always excluded.
Applies to Gmail (by sender), Drive (by owner), and Calendar (by organiser).
Manage domains interactively with axon email domains, through .axon/config.yaml, or from the web UI.
You're always in control. Remove Axon's access from each service's settings, or delete the local token files from your machine.
Google Account Permissions → find Axon → Remove Access
Workspace settings → Manage apps → remove Axon
Settings → Integrations → Connected apps → remove Axon
GitHub Applications → revoke Axon's access
You can also delete token files directly from ~/.axon/ to remove all stored credentials from your machine.