Account sign-in
Email/password and Google sign-in are handled through Firebase Authentication. The website receives a Firebase sign-in token to verify your account before issuing a short-lived website session.
Privacy overview
Your account and device data.
This page describes the data flows in the current app and host implementation. It is a product summary, not a substitute for a complete legal privacy policy.
Pairing information
The pairing QR contains a secret that should be treated like a password. After you scan it, the browser keeps only non-exportable cryptographic keys derived from it (not the secret itself), tied to your signed-in account, for up to 30 days. Disconnect or sign out removes them. Do not share the QR or paste it into public messages.
Relay traffic
The relay forwards encrypted messages between connected devices and does not intentionally save command contents. Hosting providers may retain their own operational logs; review their policies for details.
PC information
When you request a dashboard view, the PC returns app, collection, process, and recent agent status information needed to display that view. The dashboard does not store those results as a hosted profile.
- Firebase Authentication stores and verifies account credentials; the website does not receive your password.
- The website session is held in a Secure, HttpOnly, SameSite cookie and expires with the Firebase sign-in token or when you sign out.
- Commands require a signed-in account and the paired PC secret. The PC validates commands against its supported actions.
For questions about data retention or account deletion, contact the site operator. A public rollout should provide a complete privacy policy and contact details.
Want the technical side?
See the checks applied before any command reaches your PC.