Account
Google sign-in provides subject, email, and email_verified; we do not receive or store your Google password. OAuth tokens are not stored in raw form; only a digest and authorization metadata are retained.
PRIVACY
Privacy Notice
Operator: the Remote Device Hub individual developer. Effective/updated: 2026-10-03. Contact: /contact. We aim to retain only what is needed to provide the service and describe device operations accurately.
Devices
We retain device ID, name, account ownership, and a token digest for binding and authentication.
Operations
File contents and command stdout/stderr travel between the customer's MCP client and device Agent and are handled briefly in Agent memory; the Hub does not retain them as operation audit records.
Audit
Audit data contains metadata such as time, device, account, client, request ID, errors, and duration. It is retained for 30 days, with a 100,000-record cap cleaned during writes.
Support requests
The form stores your reply email, category, subject, message, submission time, and random ticket number only to handle support, privacy, security, and billing requests. Data is kept in private server-side SQLite, accessible only to authorized operators, retained by default for 90 days, and cleaned at startup and hourly. There is no public read access or third-party forwarding. Raw IP/UA are not stored in tickets, although security access logs may process IP, path, time, and status.
Deletion
There is currently no self-service export or deletion. Request it through the contact form and complete necessary identity verification for manual handling; security or payment records may be retained when legally required. Account authorization, device, OAuth, and client data do not share one uniform 30-day period; backups may not be purged immediately.
Third parties and payments
We currently use no external tracking, font CDN, or advertising service. Payments are not enabled; future payments will be hosted by a processor and the Hub will not store card numbers or CVC. ChatGPT and other third parties process data under the policy you select.
Security logs at the entry point may process IP, path, time, and status; support records do not intentionally store IP/UA. Do not submit passwords, tokens, card data, or complete sensitive logs.