Sesh

Privacy Policy

Updated November 5, 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, encrypted end to end. Sesh never stores them on its servers.

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

Sesh’s connection relay

Your devices find each machine by its Sesh ID, a public key that only that machine can answer to. They connect directly whenever the networks allow. When they can’t, for example from a phone on cellular to a computer behind a home router, the encrypted traffic passes through Sesh’s relay. The relay also tells each device and machine its public internet address, so they can try to connect directly.

The relay can’t read what passes through it: the connection is encrypted between your device and your machine. It sees the Sesh IDs and IP addresses of the two ends and how much data they exchange, and keeps no copy of the traffic. It counts usage in aggregate to run the service, and its host may keep standard request logs, such as IP addresses, for a short time.

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. Your device decrypts them to show the machine, the session and a short line: what an approval is for, the start of the agent’s reply, or the error.

Live Activities on iPhone are updated the same way while Sesh is closed, but Apple’s system reads those updates directly, so they can’t be encrypted. They carry only counts and states (how many sessions are working or waiting), random IDs and generic words like “A session needs your approval”: never names, code, commands or agent text. Your iPhone fills in the names itself. You can turn Live Activities off in Settings → Notifications.

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.

Apple Watch

Apple Watch can’t open the encrypted connections your other devices use, so it reaches your machines through Sesh’s push relay instead. Each machine keeps a connection open to the relay, and the watch sends its requests there over HTTPS.

Requests and answers are encrypted on the watch and on the machine with a key made from the watch’s pairing token, so the relay sees only ciphertext. It sees each machine’s Sesh ID and IP address and when requests are made, and keeps no copy of them.

Updates, agents and themes

To check for and install updates, the Sesh service downloads release files through sesh.codes, which hands the download to GitHub, where they are stored. When you browse agents to add, it downloads the public Agent Client Protocol registry. When you pick a theme from the gallery, the app downloads it from Open VSX. These are ordinary downloads that send nothing about you beyond what any web request does.

Purchases

Sesh is free and sells nothing, so it takes no payment 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 feedback page.