Sesh

Privacy Policy

Updated October 2, 2026

Sesh is built so your work stays on computers you own. This page says what data the Sesh apps, the Sesh service on your machines, and this website handle, and where it goes.

No Sesh account, no analytics

You don’t sign up for Sesh. The apps and the Sesh service have no analytics, no advertising identifiers and no tracking, and they don’t send crash reports to us. Apple shares crash reports with developers only if you turn that on in your device’s privacy settings.

Your code and sessions stay on your machines

Agents run on computers you own. Your code, the conversations with agents, their commands and their changes are stored on those machines and travel only between them and your own devices, over connections encrypted with each machine’s certificate. They never pass through a server run by Sesh.

Each device pairs with a machine using a one-time code, and you can unpair any device from the machine.

The agents you choose

Sesh runs agents such as Claude Code, Codex, Cursor and Gemini CLI with your own accounts or API keys. Those agents send your prompts and code to the companies that make them, under those companies’ terms and privacy policies, exactly as they do when you run them yourself. Sesh doesn’t add anything to what they send.

iCloud

If you use iCloud, the list of your machines, the tokens that let your devices connect to them, and your appearance, theme, notification and New Session preferences sync between your devices through your iCloud account and iCloud Keychain. Apple stores this data; Sesh can’t read it.

Notifications

When your phone or Mac isn’t connected, your machines can notify it that a session needs approval, finished or failed. Those notifications go through Sesh’s push relay to Apple’s push service.

Notifications are encrypted on your machine with a key that only your device has, so the relay and Apple see only ciphertext. Even decrypted, they name the machine and the session and never contain agent text, code or commands.

The relay keeps your device’s Apple push token and a hashed secret so it can deliver notifications, and counts how many it delivers each hour to enforce a limit. It drops a device when Apple reports its token is no longer valid.

Updates and the agent registry

To check for and install updates, the Sesh service downloads release files from GitHub. When you browse agents to add, it downloads the public Agent Client Protocol registry. These are ordinary downloads that send nothing about you beyond what any web request does.

Purchases

The subscription is sold through the App Store with your Apple Account. Apple handles payment; Sesh only learns whether your subscription is active, and never sees your name, email or payment details.

This website

sesh.codes uses no cookies and no analytics. Like any web host, the provider that serves it may keep standard request logs, such as IP addresses, for a short time to run and protect the site.

Changes and questions

If this policy changes, the new version will be posted here with a new date.

Questions about privacy go to Sesh’s issue tracker on GitHub.