The short version

Axon runs on your computer. Your data stays on your computer. We don't collect, store, or transmit any of your data to our servers — because we don't have any.

Data Access

What Axon can read

When you authorize Axon with a service, it gains read-only access to that service on your behalf. Here's what each integration can see:

  • Gmail Messages and metadata read-only
  • Google Drive File listings and content read-only
  • Calendar Events and schedules read-only
  • Slack Messages, channels, users read-only
  • Notion Pages and databases read-only
  • HubSpot Contacts, deals, leads, tasks read-only
  • GitHub Repository access read-only

All integrations are read-only. Axon cannot send emails, modify documents, delete files, create calendar events, or post messages on your behalf.

Storage

Where your data lives

Everything stays on your local machine. Axon has no server component — no backend, no database, no cloud service that receives your data.

  • OAuth tokens

    Stored at ~/.axon/ on your filesystem. Never transmitted to any server.

  • Fetched content

    Emails, documents, and messages are saved to a local temp/ directory only when you explicitly request it.

  • Configuration

    Stored locally at ~/.axon/config.yaml. Your preferences never leave your machine.

Collection

What we collect: nothing

Axon does not collect, transmit, or store any user data on external servers.

No analytics
No telemetry
No crash reports
No third-party sharing
No advertising
No cookies
Communication

How Axon talks to external services

When you run an Axon command, it makes API calls directly from your machine to the relevant service. There is no intermediary server. Axon does not proxy, intercept, or log these calls.

Authentication

OAuth and authentication

Axon uses OAuth 2.0 to authenticate with Google, Slack, HubSpot, and GitHub. Here's how the flow works:

1

Axon opens your browser to the service's login page

2

You sign in and grant read-only permissions

3

The service returns an OAuth token to Axon

4

Axon saves the token locally on your machine

You can revoke access at any time from each service's settings:

You can also delete token files from ~/.axon/ at any time to remove credentials from your machine.

AI Assistants

Use with AI coding assistants

Axon is designed to be used alongside AI coding assistants such as Claude Code, Cursor, or Codex. When an assistant runs Axon commands, the output is displayed in your terminal and may be read by the assistant as part of your conversation.

This is your choice and under your control. Axon itself does not transmit data to any AI provider — it prints output to your terminal, and what you or your tools do with that output is governed by your relationship with those tools.

Additional

Other information

Children's privacy. Axon is a developer tool and is not directed at children under 13. We do not knowingly collect any personal information from children.

Changes to this policy. If we update this privacy policy, we will post the revised version at this URL with an updated date. Since Axon is a local tool with no data collection, changes are expected to be infrequent and minor.

Contact. If you have questions about this privacy policy, email support@axoncli.com or visit our about page.