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 October 1, 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. This website, usespaces.dev, counts visits; the “This website” section explains exactly what it records.
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 the Spaces apps or the daemon. They contain no analytics, no usage tracking, and no third-party SDK phoning data home, and they 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.
usespaces.dev uses PostHog, a product analytics service, to count visits, so the developer can see which pages and links bring people to Spaces. It records the pages you view, the site that sent you, campaign tags and ad click IDs in the link (such as utm_source or gclid), which Download link you clicked, and your browser and device type. It does not record your IP address or your location.
The site sets no cookies and stores nothing in your browser. PostHog tells visits apart with a hash of your IP address and browser that changes every day, so visits on different days cannot be linked to each other. There is no session recording, no click tracking beyond the Download links, and nothing you type is recorded. If your browser sends Do Not Track or Global Privacy Control, the site does not load PostHog at all, and blocking it with a content blocker does not change how the site works. PostHog processes this data in the United States.
None of this applies to the Spaces apps or the daemon.
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.