Your login alone isn’t enough.
A new controller needs approval on the Mac. Every new session also needs the machine password and a fresh authenticator or recovery code.
Remote access reaches real files, signed-in apps and powerful tools. Steerable separates who you are, which device you approved and whether this session is allowed to control your Mac.
Your files. Your signed-in apps. Your agents. We protect the connection with specific checks you can understand and control.
A new controller needs approval on the Mac. Every new session also needs the machine password and a fresh authenticator or recovery code.
Screen and control traffic is encrypted between paired devices. A TURN relay forwards that encrypted traffic; it is not the endpoint that decrypts the session.
Stop Steerable Copilot, end a session or revoke a controller. An approved device gets only its granted access—not permission to every machine.
Steerable Copilot can send task-related screen images and app text to your chosen provider. That is separate from remote-session encryption. Your other agents follow their own permissions and provider policies.
Screen frames and control input travel through encrypted WebRTC between your paired devices. Cloud may use a relay. Local keeps that traffic on the permitted LAN.
Your phone ↔ your MacAccount identity, authorization and connection metadata support setup and session access. Local mode still requires platform sign-in and fresh authorization.
Account + connection servicesCopilot can send relevant screen images and app text for a requested task. The provider’s terms and your configuration govern processing and retention.
Your Mac ↔ your AI providerA new controller is approved on the target Mac with a matching pairing code. Trusted controllers reconnect under the policy you chose. New sessions still require the machine password and a fresh authenticator code, or a one-use recovery code.
Saved API keys for Steerable Copilot are stored in macOS Keychain. Provider connection management stays on the desktop; remote phone controls do not return those saved keys. Provider accounts can also have local runtime records.
Stop Steerable Copilot and continue manually. It also yields when you start using its target app. End a remote session or revoke a controller when access is no longer needed. Stopping a task does not undo actions already completed.
If you use Codex, Claude Code, OpenClaw, Hermes or another agent through the remote desktop, that agent still follows its own permissions, tools and provider policies. Steerable protects the remote-access path; it does not automatically constrain every action a third-party agent can take.
Talk through your setup or report a security concern.
These are design explanations, not a claim of independent certification.