Know what leaves your device.

Terminal input, output and direct file transfers travel over SSH between your device and your chosen host. The native terminal handles this traffic. Terminal previews remain in memory.

Passwords, private keys and passphrases use Keychain on iOS and Keystore-backed storage on Android. Host-key verification checks the identity of the computer you connect to. Changed keys require your review.

Recorded conversations are read from your selected host. Live chat sends requests through SSH to a Codex or OpenCode server on that host. Termcat supplies a Python helper for this connection. Conversations, tool results and images do not pass through Termcat's notification relay or sharing service.

The agent uses the model provider and tools configured on your host. Its own provider settings determine where prompts and attachments go beyond that host. Sending a message, answering a request or stopping a reply acts on the selected agent conversation.

Saved connection details, preferences, commands, work organization and unsent drafts are stored on the device. App locking and credential protection are available in security settings. Removing a local entry does not remove files or stop processes on your host.

When enabled on iOS, sync sends supported settings or connection data to your Apple iCloud account. Credential sync is a separate choice. iCloud availability depends on your Apple account and the app's configured container.

Local speech engines process audio on your device. Downloading a model contacts its download service. If you choose a provider engine, audio is sent to the provider you configure and is subject to that provider's policies.

Optional remote alerts use a paired host integration and a relay. The relay receives event status, routing identifiers and notification enrollment information. Notification payloads exclude SSH credentials, terminal output, prompts and files.

Apple or Google's push service delivers the notification to your device. Closed-app delivery needs a deployed relay and is not available from the public service yet.

Creating a share link uploads the selected file and its metadata to the configured sharing service. This is separate from transferring a file directly to your SSH host.

Anyone with the download link can access the file until it expires or you delete it. Links expire after one day. Files are encrypted in storage; the service can decrypt them to serve an authorized download. Do not treat a share link as a private SSH transfer.

This site does not add analytics, advertising scripts, signup forms or tracking cookies. Fonts and product images are served with the site. A hosting provider may process ordinary request information such as IP addresses to serve pages.

This page describes the current implementation. Public app distribution and service hosting are still being prepared.