Privacy

The short version: your screen and your keystrokes travel only between your own devices, encrypted end to end with keys that never leave them. When you use the assistant, what it needs for a task goes to the model you chose. We cannot read any of it.

What stays on your devices

Screen video, pointer and keyboard input, your task history, the assistant’s memory and your schedules are stored on the computer you control and sent only to devices you have paired, encrypted with keys generated on your devices during pairing. The exception is what the assistant needs for a task, which also goes to the model you chose for it (see The assistant, below).

What the relay sees

When you are away from your own network, traffic goes through our relay so the two devices can find each other. The relay forwards encrypted bytes. It sees the size and timing of those bytes, the IP addresses of the two ends, and a random routing token that lets it match one connection to the other. It cannot decrypt anything, and the code that forwards is structurally unable to reach the code that does crypto — a test fails the build if that ever changes.

What the relay keeps, and for how long: the routing token stays in its memory while a connection waits for the other end (up to two minutes at a time) and while the two are connected, and is dropped when they disconnect or the wait runs out. To stop one address from flooding it, the relay counts each IP address’s recent connections in memory and deletes that count at its first clean-up after the address has gone 10 minutes without connecting (clean-ups run at most every five minutes). The relay writes none of this to disk, and nothing it logs contains an IP address or a token. The web server in front of it, which handles the connection’s TLS encryption, keeps no access log. Its error log records a request, with the IP address it came from, only when it cannot reach the relay at all, for example while the relay restarts.

What we collect

The Android app

The Android app is on Google Play (version 1.0.0). This section describes that version.

This website

poketpc.com uses Google Analytics to count visits and Google AdSense to show ads. Both set cookies and receive your IP address and browser details under Google’s own terms; see how Google uses information from sites that use its services. In the EEA, the UK and Switzerland you are asked first, and nothing is stored until you agree; elsewhere you can opt out of personalized ads at Google’s ad settings, and a browser that sends Global Privacy Control never gets personalized ads here. None of this runs in the web client, which lives on a different site.

The assistant

The assistant runs on your computer, with the model you pick there: your Claude subscription through Claude Code, the Claude API or xAI’s Grok with your own key set up on that computer, or a local model in Ollama. With a cloud model, your prompts, the assistant’s memory and the screenshots it needs go to that provider (Anthropic or xAI) under your account and their terms; with Ollama they stay on your computer. We do not receive them, and we do not resell model usage.

Your control

Every paired device is listed on the computer and can be revoked there, which immediately cuts any live session. Deleting the helper app leaves its data behind. To remove it, also delete the folder ~/Library/Application Support/PocketMac, the file ~/Library/Preferences/com.innoedge.pocketmac.helper.plist and, in Keychain Access, the items whose name starts with com.innoedge.pocketmac. If you gave the assistant a notes folder, it also wrote a briefings folder and followups.md there. The assistant cannot write files unless you give a task that reach, and what it is allowed to do is bounded before it starts.

Contact

Questions or a deletion request: support. This page changes when the product does; the date below is the last change.

Last updated 9 October 2026 · Innoedge Technologies Limited