PALEO

Legal

Privacy Policy

Last updated: November 4, 2026

This Privacy Policy explains what information the Paleo website at paleo.build (the “Site”) and the Paleo desktop application for macOS (the “App”) collect, how it is used, and the choices you have. The Site and App are operated by Jordan Zietz, San Francisco, California, USA (“Paleo”, “we”, “us”). Contact: jordan@zietz.com.

This policy is modeled on the structure of Conductor’s Privacy Notice and its privacy documentation, adapted to Paleo’s local-only design. Paleo is not affiliated with Melty Labs, Conductor, Meta, Anthropic, OpenAI, GitHub, or Apple.

The short version

  • The App has no accounts, no servers, and no analytics. Your repositories, prompts, chats, terminal history, and settings stay on your Mac.
  • Your prompts and code go directly from your Mac to the model provider you configure (Anthropic or OpenAI) under your own account and their privacy policies. We never see them.
  • If you connect GitHub, the App talks to GitHub from your Mac with a token stored in the macOS Keychain.
  • We do not sell, share, rent, or train on your data. We cannot: we do not have it.

1. The Site

The Site is a static website hosted by Vercel. Like any web host, Vercel’s infrastructure records standard server logs (IP address, user agent, requested pages, timestamps) for security and operations; see Vercel’s privacy policy. The Site does not set tracking cookies, does not run third-party analytics, and does not have forms or accounts. If we add analytics in the future, we will update this policy before doing so.

2. The App: data stored on your Mac

The App stores the following on your computer and nowhere else:

  • Repositories and workspaces: git worktrees under ~/paleo/ (or the locations you choose), plus any directories you import from Conductor.
  • Chats and session events: the messages and agent events for each workspace, in a local SQLite database under ~/Library/Application Support/com.zietz.paleo/.
  • Settings: in that same directory and in ~/.paleo/settings.toml and your repositories’ .paleo/ files.
  • Terminal history, attachments, drafts, and caches, also under the Application Support directory. Terminal history is encrypted with a key kept in the macOS Keychain.
  • Credentials: GitHub tokens and any API keys you enter are stored in the macOS Keychain or in environment variables you configure, and are used only from your Mac.
  • Agent binaries and logs: downloaded agent programs and local diagnostic logs, which you can export or delete.

Anyone with access to your macOS user account can access this data. Deleting the App’s directories deletes the data; there is no copy anywhere else.

3. The App: where network traffic goes

The App makes network requests only to services you have chosen to use:

  • Model providers. When you run an agent, your prompts, relevant files, and tool results are sent by the agent program directly to Anthropic (Claude Code) or OpenAI (Codex) using your own credentials. Their use of that data is governed by their policies: Anthropic, OpenAI. Chat titles and branch names are generated by the same provider from your first message.
  • GitHub. Cloning, fetching, pushing, pull requests, checks, and review comments are requested from GitHub using your token; see GitHub’s privacy statement.
  • Vendor downloads. Agent binaries are fetched from their vendors’ official channels (for example GitHub Releases, Anthropic’s installer, or the npm registry); those servers see your IP address.
  • Update checks. The App periodically requests a small static file from our update host to see whether a new version exists. That host’s logs may record your IP address and the App version. No identifier is sent.
  • MCP servers and other tools you configure yourself.

We do not operate a relay or proxy for any of this traffic, and we do not receive copies of it.

4. GitHub App

Connecting GitHub uses a GitHub App registration named “Paleo”. GitHub shows you the permissions before you authorize, the resulting token is stored in your Keychain, and you can revoke it at any time at github.com/settings/applications. We do not receive the token and do not receive webhooks.

5. Import from Conductor

The App can read your existing Conductor data (repositories, workspaces, chats, settings) from your Mac to migrate it into Paleo. This happens locally and the data is copied only to the Paleo directories listed above.

6. Children

The Site and App are not directed to children under 16, and we do not knowingly collect information from them.

7. Security

Releases are code-signed and notarized with Apple. Secrets are kept in the Keychain. Because all data is local, the security of your data depends on the security of your Mac; keep backups and use FileVault.

8. Your choices and rights

  • Delete all App data by deleting the App, ~/paleo/, ~/.paleo/, and ~/Library/Application Support/com.zietz.paleo/, and removing Paleo’s Keychain items.
  • Revoke GitHub access in your GitHub settings; remove provider credentials in the App’s settings.
  • Residents of California and other U.S. states with privacy laws have rights to access, correct, delete, and port personal information. Because we hold no personal information about App users, there is nothing for us to access or delete; for the Site, hosting logs are retained by Vercel for a limited period and are not accessible to us in identifiable form. We do not sell or share personal information as those terms are defined under the CCPA. You may send requests to jordan@zietz.com.

9. Changes to this policy

We may update this policy from time to time. We will post the new version on the Site and change the “Last updated” date; material changes take effect when posted.

10. Contact

Privacy questions or requests: jordan@zietz.com.