Last updated: July 28, 2026
1. Information we process
CosmoRemote processes account details (email when you sign in), device identifiers, app diagnostics, purchase status, paired-device metadata, project names, prompts, outputs, and session history when those features are enabled.
The exact data depends on how you use the product. Local Wi-Fi sessions can stay between your devices, while account sync, remote relay, purchase restoration, and cloud history require backend processing.
2. Code, prompts, and session content
CosmoRemote is designed to connect your phone or tablet to the computer running Claude Code, Codex, Cursor, or a terminal shell. Your code, prompts, and command output may pass through the local bridge or remote relay so the app can display and control the session.
If cloud history or account sync is enabled, session content and related metadata may be stored so you can review previous work across devices. You can delete local history from the app, and backend deletion controls are provided through the app or support flow.
3. Analytics and diagnostics
CosmoRemote uses PostHog for product analytics. We capture product usage events (pairing, session starts, test runs, feature discovery, and subscription flows) to understand how the app is used and improve it. No code, prompts, or session content is sent to analytics.
PostHog does not track users across unrelated apps or serve advertisements. We do not use advertising identifiers or build ad profiles. You can opt out of analytics by disabling optional telemetry in the app settings.
Crash reporting and diagnostics help us identify bugs and stability issues. Diagnostic data is limited to technical context (device model, OS version, app version, stack traces) and does not include personal content.
4. Purchases and subscriptions
Purchases and subscriptions are processed through the Apple App Store or Google Play Store, with subscription state managed by RevenueCat. RevenueCat receives an anonymous app user ID and purchase verification tokens to confirm entitlement status.
We do not receive or store your payment card details. The app stores handle billing, renewals, cancellations, and refunds under their own terms and privacy policies.
5. Push notifications
CosmoRemote can send push notifications to your device when a session finishes, needs attention, or when other account-relevant events occur. Notifications are delivered through Apple Push Notification service (APNs) or Google Firebase Cloud Messaging (FCM) and are managed by our backend relay.
You can disable push notifications at any time through your device's system settings. Notification preferences are also available inside the app.
6. What stays on your devices
Your prompts run on your own Mac, with your own API keys and accounts. The CosmoRemote relay only bridges traffic between your phone and your Mac when you are not on the same local network. Every connection uses TLS encryption.
Your code, projects, and working directories stay on your machine. The relay does not inspect, store, or log your session content. If you use the optional cloud history feature, session metadata and output snapshots are stored so you can review them later.
7. How we use information
We use information to provide pairing, live streaming, remote relay, session history, account access, subscription entitlement checks, push notifications, fraud prevention, diagnostics, security, support, and product improvement.
We do not sell your personal information. We do not use your private code or session content for advertising.
8. Third-party providers
CosmoRemote works with third-party tools and services, including Claude Code, Codex, Cursor, app store payment systems, RevenueCat, PostHog, crash reporting, authentication, push notification services, and infrastructure providers.
Those providers process data under their own terms and privacy policies. Review the policies for any AI CLI, API account, app store, or connected provider you use with CosmoRemote.
9. Security and retention
We use reasonable technical and organizational safeguards for transport security, authentication, and entitlement checks. All relay connections use TLS. No internet-connected system can be guaranteed to be perfectly secure.
We keep information only as long as needed for the product, legal obligations, security, backups, and support. Some deleted data may remain in backups for a limited period before being purged.
10. Your choices and account deletion
You can limit data processing by using local-only workflows where available, disabling optional telemetry or push notifications, deleting local session history, signing out, or removing paired devices.
To delete your account and associated data, use the account deletion option in the app Settings screen. You can also request deletion by contacting us at contato@cosmohq.org. We will process deletion requests within a reasonable timeframe, subject to legal retention obligations and backup cycles.
For other privacy requests or questions, contact CosmoRemote at contato@cosmoremote.com.