There is no Orbit cloud
Kno2gether Labs doesn’t run a server for your data, and there’s no Orbit account. The apps talk to your own Orbit Server only if you pair one, and we never receive your data.
- None of the three projects include analytics, advertising or crash-reporting libraries.
- Orbit Health keeps everything on your phone unless you pair a server. OrbitWalker’s screens, browser and recordings run on your phone.
- Orbit Server makes outside requests only to the AI and voice providers you configure, and for its HTTPS certificate. It has no telemetry and no update check.
What leaves your phone, and when
| What | Where it goes | When |
|---|---|---|
| “Hey Orbit” | Nowhere. It’s detected offline on the phone. | While Listen for “Hey Orbit” is on |
| Wake-word model | Downloaded once from the Vosk project, then checked against a pinned SHA-256 before use | The first time you turn “Hey Orbit” on |
| What you say to Orbit | Turned into text by Android’s speech recogniser, then sent as text to your server | After the wake word, the mic or the shortcut |
| Screen context | Your server: a text list of open screens (app name, position, size), up to 8 recent apps, your installed apps’ names, the background and whether you’re recording | With each request to Orbit |
| Ring data | Your server, only the groups you allow | After each ring sync, if paired |
| Ask tab questions | Your server | When you ask |
| Update check | GitHub, carrying only Orbit Health’s version number | At most once a day, unless you turn it off |
| Web pages | The sites you visit in Orbit Browser, like any browser | When you browse |
OrbitWalker asks Android for on-device speech recognition when the phone has it. If it doesn’t, the phone’s standard recogniser is used, and that may use its maker’s online service.
The agent never receives screenshots, pixels or anything inside your apps.
What your server sends to providers
When you ask Orbit something, your server calls the AI provider you configured, with your key. That request includes your question, the recent conversation, the results of any ring-data tools the agent used and, for OrbitWalker, the screen context above. For a spoken reply, your server sends the answer text (up to 1,500 characters) to the voice provider you picked.
Those providers receive the request text and the answer text, and handle them under their own terms. We don’t control them. To keep everything on your own machines, point the agent at a model you run yourself through an OpenAI-compatible server (for example Ollama), and use the phone’s voice.
Keys, passwords and tokens
- Provider keys are encrypted at rest with AES-256-GCM, using a master key the server creates on first run and keeps in its data folder. They are never shown again. Changing the provider or host deletes the saved key, so it is never sent to a different host.
- No default password. First-run setup uses a one-time code printed on the server’s console, valid for 24 hours and stored only as a hash. The admin password is stored as a bcrypt hash.
- Pairing codes are random, work once and expire after 10 minutes.
- Per-device tokens: each paired phone gets its own token, stored on the server only as a hash. You can revoke any device from the dashboard.
- Agent tokens for MCP and the data API have scopes, are shown once, are stored as hashes and can be revoked at any time.
- On the phone: Orbit Health encrypts its server token with a key in the Android Keystore. OrbitWalker keeps its server token in app-private storage that’s excluded from backups. It isn’t separately encrypted.
- The server’s database isn’t encrypted at rest. It’s protected by file permissions: a non-root user, and a data folder only that user can read. Use disk encryption on the machine if you need more.
Connections
- The apps talk to your server over HTTPS only. Pairing links must be HTTPS, and Orbit Health refuses plain HTTP everywhere.
- A self-signed server is pinned: the phone trusts only that exact certificate. A server with a public or Tailscale certificate is trusted for its exact name only.
- If the server’s certificate changes, Orbit Health stops sending and asks you to pair again.
- The recommended setup keeps the server off the public internet entirely, reachable only over your Tailscale network.
Dashboard protections
- Session cookies are
Secure,HttpOnlyandSameSite=Strict. Sessions end after 30 minutes idle or 12 hours in total. - Every form submission needs a CSRF token and a same-origin check, sign-in included.
- Rate limits apply to failed sign-ins (5 per 15 minutes), setup attempts, pairing, the device APIs, the agent and tokens.
- A strict Content Security Policy is in place. The dashboard loads nothing from other sites and can’t be framed.
- The access log records every read of your data by the agent, MCP clients, the data API and dashboard exports. It records what was read, never the values, and denied attempts too.
On your phone
- Orbit Health stores readings in an encrypted database whose key is protected by the Android Keystore. It is excluded from Android backup and device transfer. App lock is on by default. Estimated sleep never leaves the phone.
- OrbitWalker recordings never include the in-glasses keyboard (or the pointer while it shows), notification cards, the recording indicator, the agent’s caption or the Orbit character. Notification cards can hide message contents.
- Permissions are asked for when needed: the camera for mixed-reality recording, the face bubble and scanning a pairing code; the microphone for “Hey Orbit”, speaking to Orbit and recording audio; the calendar only if you turn on the next event in the dock.
Open source
Anyone can read the code that makes these promises. All three projects are open source under the Apache-2.0 licence: OrbitWalker, Orbit Health and Orbit Server. App releases publish SHA-256 checksums, and Orbit Health checks its update downloads against them and its signing key.
Found a security problem? Report it privately through GitHub (Security, then Report a vulnerability) on the right repository, not in a public issue.
What we don’t claim
- We don’t claim an independent security audit.
- We can’t control what AI and voice providers do with the text your server sends them. Their own terms apply.
- Android’s speech recogniser, Android System WebView (which Orbit Browser uses) and Google’s on-device ML Kit (used for mixed-reality cut-outs) are system or Google components with their own behaviour.
- A server is only as private as you keep it. Anyone with your dashboard password, a backup or root on the machine can read your data.
- In the Tailscale setup, Caddy gets access to the host’s Tailscale socket for certificates. The docs show how to avoid that.
- If the ring’s vendor app stays installed, it may still upload your data. Orbit Health can’t stop that.
- Orbit Health is a wellness app, not a medical device.