Your data.
Your choices.

1. What this notice covers

This notice describes the someorbit website, local playground and supplied companion integrations. It reflects the current development preview. A separately hosted or modified installation may use different logging, storage or services; its operator is responsible for explaining those changes.

Reading these pages does not require an account. The supplied website has no advertising cookies, payment collection or customer registration. Optional local progress measurement is described below.

2. Conversations and connected agents

Messages, replies and recent conversation context are used to generate replies and animate the avatar. The supplied interfaces keep bounded conversation history in memory by default. If you enable Remember on this computer, the local host saves the last 40 messages per Playground or desktop local conversation, up to 8,000 characters each, along with shared avatar preferences and local model connection settings. Resume is explicit and does not send or speak messages. API credentials, audio recordings and connected-agent histories are not saved by this feature. The file is under your operating-system user account; anyone with access to that account may read it.

When you connect a model, messages and relevant context are sent to the configured Ollama or OpenAI-compatible endpoint. That endpoint may run on your device or be a remote service. Optional expression analysis also sends text and recent context to its configured model. The provider's own handling and retention rules apply.

The installed desktop app checks standard Ollama, LM Studio and Hugging Face model folders using bounded, read-only file names and metadata. It does not read model weights, search the whole disk or upload the results. Detected files are shown separately from models available through a running local service. Discovery runs at startup, when returning to the app and while model settings are visible.

In an MCP integration, your host application exchanges explicitly submitted messages and replies with the companion. The companion does not automatically import your entire host conversation. The host may keep its own history independently.

3. Microphone and voice

Microphone features require you to start them and grant the relevant permission. Audio is used to transcribe speech; text is used to generate spoken replies. The supplied local Windows and installed local voice paths process audio in memory and do not intentionally save recordings during normal use. If you configure a local Whisper-compatible service, audio is sent to that loopback service; its own recording and retention settings apply. There is no automatic cloud transcription fallback.

Browser speech recognition or voices can depend on browser or operating-system services, including online services. Those providers may process audio or text under their own policies. Local operation depends on the speech path and model you choose.

Use Stop, close the interface or revoke microphone permission in your browser or operating-system settings to end capture.

4. What can remain on your device

• Accessibility preferences: the renderer can save motion and off-state preferences in browser storage under someone:motion and someone:off.
• Shared appearance and reply settings: display name, avatar and related settings are held in the local server's memory. They can survive a page reload while that server remains running; they reset when it restarts unless Remember on this computer is enabled. Saved settings can then be restored on startup.
• Optional voice installations: installed voice models, runtime files and registration metadata remain on disk until removed. Metadata can include local file paths, model identifiers, licence information and file hashes. File paths can contain your operating-system username.

The supplied application has no routine transcript or recording log. Your model provider, host application, browser, operating system or administrator may keep separate records. Developer diagnostics can deliberately save test evidence; those tools are separate from normal conversation use.

5. Your controls

Choose your provider before sending content, and review its privacy policy. Avoid entering information you do not want that provider to receive. Use a local model and local speech path when you need processing to stay on your device.

Use Delete saved data or turn off Remember on this computer to delete saved conversations and settings for both local interfaces. Closing the interface releases in-memory conversation state but does not delete an opted-in saved file. Restarting the local server clears unsaved shared settings. Clear this site's browser data to remove saved accessibility preferences. Remove optional voice files through your local installation tools if you no longer need them.

These actions do not delete records held by a connected provider or host. Use that service's data controls or request process for access, correction or deletion of its records. Rights and available request procedures depend on the service and applicable law.

Website and desktop downloads

Cloudflare hosts this website and delivers desktop installers from R2 storage. Requests include normal connection information such as your IP address, requested file and browser headers. Cloudflare processes this information to deliver and protect the service. Sampled operational logs help diagnose download failures. The hosted chat example uses authored replies in your browser and does not send messages to a model or collect usage reports. Your local desktop conversations and model files are not uploaded with download requests.

Improve someorbit

Usage reports help us understand what works and where the app needs improvement. Sharing is on by default for new installations when a report service is available. You can switch it off in Playground Preferences or desktop Settings → App. It is separate from saving conversations, and the app works without it. This preview sends reports only to a local service on your computer; no hosted collection service is enabled.

Reports contain daily app and supported website openings, download interest, connection setup/use counts, completed reply and failure counts, and first-use/return dates. They never contain your messages, voice recordings, name, URLs, model details or credentials. A random report ID keeps updates together; it does not identify a person.

Reports send automatically while the app is running. If the service is unavailable, the app retries later. Turning sharing off stops counting, removes the local report and requests deletion from the backend. If disconnected, a small deletion request stays on this computer until it can be delivered. Re-enabling starts a fresh report. Existing local-only reports are not shared automatically, and an existing off choice is preserved.

Daily counts cover up to 90 days. The local backend removes report content after 90 days without an update when it next processes a request. Minimal deletion receipts retain a random ID and a hashed authorization token so delayed uploads cannot restore deleted reports. The admin can see totals and delete reports. Anyone with access to your computer account can read its local files. Older manually imported reports must be deleted separately by their recipient.

The admin panel can also hold manually entered aggregate evidence from a website, release host, MCP directory or billing system. It does not identify individual customers or implement payments. Download interest and a prepared MCP file do not prove installation. Unknown market metrics remain unmeasured.

App updates

The desktop app includes update support. This preview has no configured update host and makes no external update requests. Once official hosting is enabled in a future release, automatic checks and downloads can be disabled in Settings → App. Installation requires your restart action. Updates cover the app and bundled avatars; they do not upload conversations, recordings or model files.

An enabled update service receives normal connection information, including your IP address, update request and a randomly generated staging identifier used by the update library. That identifier, update preferences and downloaded installers are stored under your operating-system account separately from Remember. Turning off automatic updates stops scheduled checks; a manual check still contacts the service. The service operator may keep request logs. Browser and MCP views read release status from your local app.

6. Changes to this notice

This notice will be updated when the supplied product's data handling changes. The date above identifies this version. Review the notice supplied with any future release or independently operated installation.

For product use and licence information, read the Terms & Conditions.