Privacy

Everything runs on your machine, and you don't need an account. Only Satura Remote does. There's no telemetry and no crash reporting.

#On your machine

Frames from the Unity editors move to the app over a shared GPU texture. Everything else goes over local loopback.

#What the app itself sends

The app goes online to check GitHub Releases for updates.

#What comes from what you run

Other traffic comes from what you run:

• Unity installs the SDK from the Satura Space repository on GitHub.
• Your agents talk to their providers, under your own subscriptions.
• The MCP server downloads Unity's C# reference source from GitHub and reads Unity's Scripting Reference when an agent asks for them.
• Dashboard tiles fetch the URLs they're written to fetch.
• The Kimi usage meter asks Kimi's API with your own Kimi login.

#Satura Remote

Satura Remote stays off until you turn it on to pair a phone. From then on, the app connects to the hosted relay. Everything between your phone and your computer is end-to-end encrypted, so the relay can't read your terminals, code, files, prompts or the game stream. It still sees routing metadata such as your account email, IP address, connection times and message sizes. See Satura Remote and Security.

#Secrets in your project

Dashboard secrets live only in .sspace/dashboard/secrets.json, inside the gitignored .sspace/ folder. When an agent reads a dashboard, secrets come back masked.

For files with local-only values, such as a localhost URL or a key, mark them never-commit in the Git panel so your edits stay out of commits.