English
Privacy Policy
Last updated: 2026-07-19
Moshline uses an on-device-first privacy model. If you enable remote notifications, we handle limited routing data as described below.
Limited notification-routing data: When remote notifications are enabled, Moshline sends its notification service your APNs device token, a random webhook token generated by the app, and the APNs environment. The service stores the mapping only to route notifications you request to this device.
Notification content and other data: Webhook notification payloads are processed only to construct and deliver the requested push and are not persisted by our notification service. We do not require an account or store your server host list, terminal input or output, passwords, or SSH private keys on our servers.
No analytics or telemetry: We do not run user analytics, behavior tracking, ad tracking, or background telemetry in Moshline.
On-device operation: Connection settings, authentication materials, and runtime interaction data stay on your device. Secure Enclave keys are generated and stored locally.
Retention and deletion: The notification-token mapping may remain in service storage while the notification route is active. Uninstalling Moshline removes local app data but does not automatically delete that server-side mapping. Contact us at the address below to request its deletion.
No selling or tracking: We do not sell notification-routing data or use or share it for advertising or behavior tracking. Notification content and the APNs device token are sent to Apple Push Notification service only as needed to deliver requested notifications.
Contact: If you have questions about this policy, email tardislabs@gmail.com.