Skip to content

Latest commit

 

History

History
91 lines (65 loc) · 3.62 KB

File metadata and controls

91 lines (65 loc) · 3.62 KB

Privacy Policy

Last updated: 5 August 2026

pew2 is an app for controlling coding agents that run on your own computer. This policy covers the pew2 iOS app and the pew2 command line tool.

The short version: pew2 has no accounts, no analytics, and no servers that store your data. Nothing you type or receive is readable by anyone but you.

What is collected

Nothing.

There is no account to create, no email address to hand over, no analytics SDK, no crash reporter, no advertising identifier, and no tracking of any kind. The developer of pew2 has no database of users, because there is no way to become one.

Where your data lives

Your conversations, your code, your files, and your agent API keys stay on the computer running the pew2 command line tool. That is your machine. The app is a window onto it.

The app itself stores very little on your phone, and all of it in the iOS keychain: the details needed to reconnect to your computer, an identifier for this device so your computer can tell it apart from your other ones, and which agent you used last. Your conversations are not copied onto the phone; they are read from your computer each time you open the app. Deleting the app removes everything it stored.

How the connection works

When your phone and your computer are on the same Wi-Fi, they talk directly and nothing else is involved.

When they are not, traffic passes through a relay so the two can find each other. Everything is encrypted end to end before it leaves your phone, using XChaCha20-Poly1305, with a key created during pairing that never leaves your two devices. The pairing key travels in the fragment of the pairing link, the part of a URL that browsers and servers never send onward.

The relay therefore cannot read your messages. It sees encrypted blobs, their size, their timing, and a room identifier derived one way from your pairing token so that it cannot be reversed back into the token. It stores none of it. If you run your own relay, which pew2 supports, even that goes to a server you control.

Permissions the app asks for

Each of these is used only for the thing it says, and everything they produce goes to your own computer over the encrypted connection described above.

  • Camera. To scan the pairing code shown by your computer, and to take a photo to send to an agent.
  • Photos. To attach an image to a message, and to save an image an agent sends you.
  • Microphone and speech recognition. To dictate a message, while the microphone button is held. On iOS the app requires Apple's on-device recogniser, so the audio is turned into text on the phone itself and is not sent to Apple for transcription.
  • Notifications. To tell you when an agent has finished or is waiting on you. Notifications are generated by your own computer, and are delivered locally rather than through a push service.

You can refuse any of these and the rest of the app still works.

Children

pew2 is a developer tool and is not directed at children.

Third parties

pew2 has no third party SDKs and shares nothing with anyone, because it collects nothing to share.

The coding agents you connect to pew2 are separate programs, run by you, on your computer, under their own terms and their own privacy policies. What you send to Claude Code, Codex, Gemini, or any other agent is governed by whoever makes that agent. pew2 passes your words to the agent you chose and does not keep a copy.

Changes

If this policy changes, the updated version will appear at this address and the date at the top will change with it.

Contact

Questions, or anything that looks wrong, at https://github.com/KenKaiii/pew2/issues.