<!-- Over to You privacy policy -->

# Over to You privacy policy

Updated 2026-11-21

What the Over to You apps and this website handle, where it goes, where it stays and how to remove it. Effective 2026-11-21.

**The short answer**

Over to You has no account and no sign-in. It has no analytics, no advertising and no tracking. The one piece of data about you that leaves your devices for a server of the project is the notification token of your iPhone, and it exists only so the push server can wake your phone.

What an agent asks and what you answer travels between your iPhone and your Mac, sealed on one device and opened only on the other.

## What the apps handle

Three kinds of data, and where each one goes.

- **Pairing keys.** Pairing by QR code makes a key on the iPhone and a key on the Mac. Each keeps its own key and the other’s public key. The iPhone keeps them in its keychain, readable only on that iPhone and not copied to a backup or another device. The Mac keeps its key and the list of paired phones in the login keychain. None of this is sent to a server of the project.
- **Your iPhone’s notification token.** The iPhone app asks Firebase Cloud Messaging (a Google service, which in turn uses Apple’s push service) for a token that names that phone for notifications. The iPhone sends the token to your Mac when you pair. The Mac saves it with the phone’s name and pairing date in a file in its support folder (`~/Library/Application Support/OverToYou`). The token is the only data about you that the Mac sends to the push server.
- **The steps themselves.** The question an agent asks, your answer, a key you type, the view of your Mac, files and command output go between the iPhone and the Mac. Both ends seal every frame with a key they agreed on at pairing. They do not go to the push server.

## The push server

When a step waits for you, the Mac sends your phone’s token to a small server at `push.overtoyou.dev` (hosted on Vercel). The server asks Google’s Firebase Cloud Messaging to deliver one notification to that token. Google and Apple carry it to your phone under their own terms.

The message text is fixed in the server’s code: the title is the product name and the body reads “A step is waiting for you”. A caller can choose which phone to wake and cannot choose what the message says. The Mac may add a block it sealed for that one phone. The server only passes the block on and cannot open it; the phone can.

The server’s code has no database and no storage, and it writes no log lines of its own. What it sees is the token and, at times, the sealed block, only while it forwards them. The hosting platform may keep its own ordinary request logs. The code cannot rule that out and this page does not state what it keeps or for how long.

## The tunnel

When the iPhone and the Mac cannot reach each other directly, for example when you are away from your home network, the connection goes through a relay at `tunnel.overtoyou.dev` (a Cloudflare Worker). The relay carries bytes that the iPhone and the Mac have already sealed. It holds no key for them, and its code does not decrypt, change or store them.

To route a connection it uses a room name that is a hash of the Mac’s secret, and it uses the network address of the connecting device to limit how often one address can connect. Its code does not save that address. Cloudflare may keep its own ordinary logs, which this page does not describe.

## Analytics, advertising and tracking

There are none. The iPhone app includes only the Firebase Cloud Messaging part of Firebase, and Firebase Analytics is switched off in its configuration. The apps include no advertising and no other analytics or tracking code. The iPhone app does not use the App Tracking Transparency prompt because it does not track you.

## Where your data stays

- On the iPhone: the pairing keys and the key that opens sealed notifications, in the keychain. The app does not use a cloud account.
- On the Mac: the keys and the list of paired phones in the login keychain, and each phone’s name, pairing date and notification token in `~/Library/Application Support/OverToYou`.
- On the push server and the tunnel: nothing is kept by the code of either one.

## How to delete your data

- **On the iPhone:** in the app, choose “Unpair this Mac” and confirm. The app deletes the Mac’s pairing and the notification key from the keychain. Deleting the app removes the rest.
- **On the Mac:** in the menu bar app, choose “Remove” beside the phone. That ends its open sessions and drops what the Mac kept of it, including its notification token. To remove everything, quit the app and delete the folder `~/Library/Application Support/OverToYou`.
- The notification token also lives with Google and Apple for as long as the phone has the app installed. Deleting the app on the iPhone ends that.

## This website

- It sets no cookies.
- It loads no third-party scripts, analytics or fonts. The pixel font is served from this site.
- It keeps nothing in your browser. Its notify-me form is closed today, so the site collects nothing you type.
- The host that serves the pages (Vercel) may keep ordinary access logs, such as the network address and the page requested. This page does not state what is kept or for how long.
- Links to other sites lead to pages with their own rules.

## Children

Over to You is a tool for people who run coding agents. It is not directed at children, and it does not knowingly collect data from them.

## Changes

This policy is effective 2026-11-21. A later version replaces this one on this page with a new date. It describes pre-release builds that are not in the App Store yet.

## Contact

Questions or requests about your data: [nutiverse@outlook.com](mailto:nutiverse@outlook.com). More help is on [Support](https://overtoyou.dev/support/).

## Related

- [Support](https://overtoyou.dev/support/)
