No accounts, no sign-in
Spaces does not ask you to create an account or sign in. There is no developer-operated identity system behind the app.
Effective July 16, 2026. Spaces (the macOS app, the iOS app, and thespacesddaemon) is built so your terminal and workspace data never has a reason to leave your own devices.
Spaces does not ask you to create an account or sign in. There is no developer-operated identity system behind the app.
The developer collects no personal data from Spaces. There is no analytics, no usage tracking, and no third-party SDK phoning data home. The apps and the daemon do not report what you run, what you type, or which projects and workspaces you have.
Terminal output, workspace state, and everything else Spaces manages flows directly between your own devices — for example, your iPhone and your Mac, or your Mac and a remote Linux box you control — over a TLS connection pinned to that device's certificate. None of it is routed through, or stored on, servers operated by the developer. Pairing only ever connects to a device you chose to pair.
When you pair a device, Spaces stores the resulting credentials locally on that device only: in the iOS Keychain on iPhone, and in owner-only local files on Mac and Linux. Credentials are never uploaded anywhere and are removed when you unpair a device.
The iOS app requests camera access for one purpose: scanning the pairing QR code shown on your Mac or Linux device. Scanning is processed entirely on your iPhone — no image or video is stored or transmitted anywhere.
The iOS app's subscription is purchased and managed through Apple via the App Store. Apple handles payment; the developer never receives your payment details.
If this policy changes, the update will be published on this page with a new effective date.
Questions about this policy? Start a discussion on GitHub.