What data does Reins collect?

None. There is no Reins server, no account, no analytics, no crash reporting and no telemetry in the app or the daemon. We can't see your sessions because nothing of yours passes through anything we operate.

Where does my data go?

From your machine to your paired phone over a connection you control — SSH for the handshake, then an encrypted transport channel keyed through it — and nowhere else. Transcripts, commands and working-directory paths are read from your own disk by a daemon running as you. Your phone also keeps a capped local cache of recent sessions, commands and decisions in its secure store so history survives a restart; Revoke does not clear it, deleting the app does.

What are the exceptions?

Three. Voice input uses your phone's built-in dictation, so audio is transcribed by Apple or Google before the text reaches your machine — it is on by default, so switch it off in Machine → This phone if that matters. The pairing screen browses for your machine over mDNS, which puts a multicast query on your local network while that screen is open. And if you reach your machine over Tailscale or a VPN, that provider is in your network path; Reins adds no third party but your network layer might.

What about this website and the early-builds list?

The site is static, self-hosted, and loads nothing from third-party origins. The early-builds list stores your email address and nothing else; it is used to send you a build link and deleted when you ask.

What about the app stores?

Apple and Google sign and distribute the binary and see the install like any other app. That is true of every app; it is not part of the data path.

Last updated September 2026.