InOrbit — Last updated: February 19, 2026
Micah Giszack ("we," "us," or "our"), based in the United States, built InOrbit as a commercial application. This Privacy Policy explains how we collect, use, and protect your information when you use InOrbit ("the App").
By using the App, you agree to the practices described in this policy. If you do not agree, please do not use the App.
InOrbit is designed to minimize data exposure. For foreground conversations, your device sends messages directly to AI models via OpenRouter — they do not pass through our server. When background features are enabled (such as Maestro Mode or scheduled world activity), our server generates AI responses on your behalf and stores the resulting messages to maintain conversation continuity (see Section 3). We do not read, review, or moderate your messages. There is no admin dashboard or content moderation tooling built into InOrbit.
For foreground conversations, your message content is stored on your device and sent directly to OpenRouter for AI responses — it does not pass through our server. When background features are enabled (such as Maestro Mode), messages are sent through and stored on our server to maintain conversation state (see Section 3). Message content is never viewed or accessed by any person. We may access limited server-side metadata (such as timestamps and message counts) for debugging or abuse prevention.
If you are signed into iCloud, your Worlds, messages, participants, and settings are automatically synced across your devices via Apple's CloudKit private database. This sync is managed entirely by Apple and encrypted end-to-end — we have no access to your iCloud data.
| Data Type | Details | Stored Where |
|---|---|---|
| Messages | Text you send in conversations ("Worlds") and AI-generated replies | On your device (sent directly to OpenRouter for AI responses) |
| Conversation Settings | World names, participant configurations, AI Contacts, and preferences | On your device |
| Participant Photos | Avatar images you select for AI participants from your photo library | On your device only — never uploaded to our servers |
| iCloud Sync | Worlds, messages, participants, contacts, settings, and API logs (if logging is enabled) | Synced to Apple's iCloud servers (encrypted by Apple, accessible only with your Apple ID) |
| API Logs | Request and response data from AI model calls (opt-in, off by default) | On your device; synced to iCloud if enabled |
Our backend, hosted on Railway, stores a minimal set of data to support account authentication and optional background features:
| Data Type | Details | Purpose |
|---|---|---|
| Anonymous Identifier | An opaque, anonymous token generated by Sign in with Apple — not your Apple ID, name, or email | Account authentication |
| Apple Refresh Token | A token issued by Apple during sign-in, used to revoke your Apple credential if you delete your account (required by Apple Technical Note TN3194) | Account deletion compliance |
| API Key Metadata | If you use the API key provisioned at sign-up: the key itself (stored for re-delivery if you reinstall the app) and usage metadata (spend amount, model usage) visible to us via OpenRouter | Key provisioning and abuse prevention |
| World Configuration | World names, participant names, AI model selections, system prompts, and conversation settings (such as message rate and turn order) | Background AI generation and conversation management |
| Messages (Background Features) | When background features are enabled (such as Maestro Mode or scheduled activity), message content — both human and AI-generated — is stored on our server to maintain conversation state. Foreground-only messages are never sent to our server. | Background AI generation and conversation continuity |
| Message Metadata | Timestamps, token counts, message counts, and World activity state | Rate limiting, debugging, and abuse prevention |
We do not collect or store:
We do not use your data for advertising, profiling, or selling to third parties. We do not review, moderate, or monitor your content.
InOrbit relies on the following third-party services to function. We require that each third-party service provider handling user data provides the same or equal protection of that data as described in this Privacy Policy.
Server-side data is stored on infrastructure provided by Railway and processed by automated systems. On-device data is stored locally using Apple's SwiftData framework. We implement the following safeguards:
No method of electronic transmission or storage is 100% secure. While we strive to protect your data, we cannot guarantee absolute security.
We retain server-side data for as long as your account is active. On-device data (messages, Worlds, settings, photos) can be deleted at any time using the "Delete All Worlds" option in the App's settings.
You can delete your account and all server-side data directly in the App under Settings > Account Deletion > Delete Account, or via the web at micah.chat/inorbit/delete-account. You will be asked to verify your identity with Apple before deletion proceeds. Upon deletion:
You may also contact us at [email protected] to request account deletion.
InOrbit is not intended for children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with personal data, please contact us at [email protected] and we will promptly delete it.
Depending on your jurisdiction, you may have the right to:
To exercise any of these rights, contact us at [email protected].
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last updated" date. Continued use of the App after changes constitutes acceptance of the revised policy.
If you have questions or concerns about this Privacy Policy, please contact:
Micah Giszack
[email protected]