Peck Privacy Policy
Last updated: November 11, 2026
DEVLIN.AI LLC ("we", "us") makes Peck: the desktop app, the iPhone app and the optional relay. This policy explains what information Peck handles, where it goes and who is responsible for it.
In short: Peck has no account with us, and no tracking or analytics. It sends nothing to us unless you turn on remote access, and even then we can't read your messages. Peck does send your work to the services you use it with, like your AI provider and GitHub. Those services handle it under their own privacy policies, not this one.
1. What Peck stores on your computer
Peck stores your code, your prompts and chats, your agents' output, your settings, and your keys and sign-ins on your computer: in Peck's folders, in the containers it runs and in your operating system's keychain. We don't receive copies of any of this.
Your information leaves your computer only in the ways described in sections 2 and 3, and the main ones are your choice. For example, when an agent works on your code, the agent sends that code and your prompts to your AI provider.
Peck has no telemetry or analytics. It has no usage tracking, no crash reporting service and no advertising identifiers.
2. Services you connect: they receive your information, not us
When you use Peck with these services, the information goes directly from your computer to the service. Each one handles it under its own terms and privacy policy. We don't receive it, and we don't control what the service records or how long it keeps it.
- Your AI provider (for example Anthropic for Claude Code, OpenAI for Codex, or a cloud platform or gateway you chose). Your agents send the provider your prompts, the code and files they read, their tool output and anything else they work on, under your account. The provider may record and keep this. That depends on your account type and its settings, and if your account is managed by your organisation, the organisation may be able to see it too.
- GitHub, if you connect it: to sign you in, clone and push your repositories and show pull request status, under your GitHub account.
- Tools you or your agents add, such as MCP servers and plugins. They
receive whatever the agent sends them. One of them is on by default:
Context7 (
mcp.context7.com), a documentation lookup service. An agent may send it the names of software libraries and its questions about them. You can turn it off in Settings → Claude setup, or for one project in that project's settings. - Hosting and database services you link, such as Vercel or Supabase.
- Websites and package registries your projects use. Your workspaces reach the sites your projects need (such as npm and Debian/Ubuntu package archives) and the domains you approve.
If you add a devlin.ai service as a tool, that is governed by devlin.ai's own privacy policy.
3. What reaches us or our providers
Updates and downloads. Peck downloads its updates and engine files from
GitHub Releases (github.com/Devlin-Peck/peck-releases), and container
images from Docker and Ubuntu image hosts. To set up your workspaces'
firewall, it also fetches GitHub's public list of its network addresses, and
Stripe's if you allow Stripe for a workspace; it sends no sign-in with these
requests. These hosts see your IP address and what was downloaded. We don't receive individual download records.
The relay, only if you turn on remote access. Remote access is off by default. While it's off, Peck never connects to the relay. When you turn it on, your computer and your paired phones or computers connect through a relay we run on Cloudflare.
- Messages are end-to-end encrypted. Neither the relay nor we can read them.
- What the relay sees: the device identifiers it uses to route messages, when devices connect, how big messages are and whether a message carries file data.
- What the relay stores, for each computer: the identifier it routes that computer's messages by, the identifiers of devices you have revoked and hourly counts of file traffic for the last 24 hours.
- IP addresses: Cloudflare sees each connection's IP address and timing, as any web host does. The relay keeps Cloudflare's request logs for a sample of 1 in 100 requests, which include IP addresses. Our own code never records IP addresses.
Our website. The website at peck.devlin.ai is hosted on GitHub Pages.
GitHub may log visitors' IP addresses. The site has no analytics or cookies
of its own.
When you contact us. If you email us, we keep your email and our replies for as long as we need them to deal with your message and keep records.
4. The iPhone app
The Peck iPhone app has no analytics or tracking. It connects only to your own computers, through the relay, and its messages are end-to-end encrypted. Apple may collect information under its own policies, for example App Store downloads, and crash reports if you've agreed to share them with developers.
5. If your organisation manages your computer
Your employer or organisation may set up Peck through a policy file. It may also collect Peck's activity log, which Peck keeps on your computer for 12 months. The log records events such as approvals, device pairings, requests from your paired devices and workspaces created or removed. It records what happened, not what you or your agents wrote. It holds no prompts, chat text or secrets.
Your organisation may also be able to see your work in other ways that Peck doesn't control. For example, an organisation-managed AI provider account (section 2) or the organisation's own monitoring of its computers and network. All of that is your organisation's responsibility, under its own policies.
6. How we use information, and our legal basis
We use the limited information described in section 3 only to provide and secure the relay and our website, to fix problems and to answer your messages. Our legal basis, where the law requires one, is providing the service you asked for and our legitimate interest in keeping it working and secure. We don't sell or share personal information, and we don't use it for advertising.
7. Where information is processed
We're based in the United States, and our providers (Cloudflare and GitHub) may process information in the United States and other countries.
8. Security
We protect what we hold: encryption in transit, end-to-end encryption for relay messages and as little data as possible. No system is perfectly secure. To report a security problem, write to security@devlin.ai.
9. Your rights
Depending on where you live, you may have the right to know what personal information we hold about you, and to have it corrected or deleted. Because Peck sends us almost nothing, there is usually nothing to find. For information your AI provider, GitHub or another service holds, contact that service. To make a request to us, write to legal@devlin.ai. We'll answer within 30 days, and we won't treat you differently for asking. You can also complain to your local data protection authority.
10. Children
Peck is not intended for anyone under 18, and we don't knowingly collect information from children.
11. Changes
When we change this policy, we'll update the date at the top and describe the change in Peck's release notes.
12. Contact
DEVLIN.AI LLC, 4821 NE 16th Ave, Portland, OR 97211, United States · legal@devlin.ai