What the app reads and stores locally
Pax configuration and records primarily live in the directory below. Original CLI logs belong to the corresponding tools and are stored separately.
Error logs are stored separately in ~/Library/Logs/Pax Connect/, including paxd.log. Onboarding progress and display preferences use the macOS preferences system (UserDefaults), outside the application-support directory above.
~/Library/Application Support/Pax Connect/- AI usage and sessions
- Pax reads supported tool logs and stores analysis fields such as request times, models, tokens, costs, session identities and confirmed subagent relationships. The session catalog keeps titles. An untitled Claude session can include a preview of up to 160 characters from the latest user message. Complete prompt and response bodies are not stored.
- Network records
- Pax stores connections, app or process attribution, destination domains/IPs, traffic, routes and matched rules from the collection period. Diagnostic records can also contain exit, DNS, region, system language and time-zone information.
- Connection and API credentials
- Saved connection settings, subscription URLs and API profiles may contain credentials. Pax keeps these in local private configuration files. Explicitly applying a profile writes its service URL and key to the target CLI configuration. Ordinary lists do not show complete API keys. File permissions restrict access; they are not an encrypted vault.
Which features send external requests
| Feature | Network and data scope |
|---|---|
| AI usage collection | Reads local logs without an extra Pax statistics gateway. Your AI provider still handles your original AI requests under its own terms. |
| Subscriptions, rules and icons | Contacts configured subscription sources, relevant rule-update sources or website-icon sources. Recipients can see the corresponding requests. |
| Measurements and diagnostics | Contacts test destinations, IP information services, DNS, STUN or public service endpoints. Recipients may observe the probe's exit IP and other network information. |
| Model catalogs | Queries the API service address you saved using its required credentials. A readable catalog does not establish model access. |
How long records stay
- AI request details
- Request details and session analysis are retained for 93 days. Hourly usage totals and necessary deduplication records are retained long term, so aggregate history can outlast individual request details.
- Network history
- Network logs follow the retention setting, with a default of up to 24 hours. Traffic and related historical aggregates are retained for up to 30 days. Short-lived collection files are cleaned as processing advances.
- Configuration and diagnostics
- Connections and profiles remain until you delete them or remove local data. Diagnostics can restore the previous result with its timestamp. Reopening a stored result does not automatically run a new check.
What this website handles
These pages do not implement account sign-in, data-submission forms, advertising scripts or behavioral analytics. They do not set cookies for advertising or behavioral analysis.
The hosting service may still process IP addresses, browser information and basic request logs while serving pages. External links and file downloads also send requests to their providers. These infrastructure requests should not be described as zero logging.
Browsing product information does not give the website access to your Mac's Pax data, CLI logs or API keys. This notice will need to reflect any future subscription forms or analytics tools.
How to remove local data
Quit Pax with ⌘Q
Closing the window is not quitting. Exit the app and its managed background processes before handling data files.
Remove the app and data as needed
Deleting the app alone does not delete configuration or history. To remove Pax's main configuration and history, use Finder's Go to Folder to locate the application-support directory above. It contains credentials and records; decide whether to back it up before deleting it.
Check separate logs and preferences
For complete removal, also handle error logs in ~/Library/Logs/Pax Connect/ and the Pax onboarding preferences managed separately by the macOS preferences system. Removing application support alone does not clear these records.
Handle source logs and backups separately
This does not delete Claude Code, Codex or DeepSeek configurations or original logs, or backups you made elsewhere. If original logs remain, Pax may collect them again after it is restarted.