Privacy
Updated 17 October 2026
0110 Hub registers your account and helps you install a fleet panel on your own server. This notice describes the registration Hub at hub.0110.digital.
Sign-in data
Google sign-in requests only openid, email and profile. We use your stable Google account identifier, verified email and display name to prove your identity and label your account. GitHub sign-in uses your stable GitHub identifier, display name and available verified email. The Hub GitHub App has no repository access.
An unfamiliar identity does not create or merge an account automatically. You choose to create an account or prove an existing sign-in method before linking. Matching email addresses never merge accounts.
How data is used and shared
Identity data is used for authentication, account linking and account display. Provider access tokens are used to verify identity and then discarded. They are not stored as fleet credentials. The Hub does not send your Google or GitHub profile to AI models, use it for advertising, or sell it.
Signing in exchanges the necessary authorization request with Google or GitHub. The Hub stores account identifiers, linked methods, session and passkey records, security audit events and your fleet setup information on the operator's server. The interface stores your language and theme preference in your browser. Authentication cookies maintain your session; the Hub does not add advertising trackers or third-party font requests.
Fleet setup and retention
Server names, IP addresses and purposes are held while you prepare an installation. The Hub transfers this draft inventory to your chosen main server. After the installer acknowledges import, the draft server rows are removed; the encrypted installation replay is removed from active Hub records within 24 hours while the service runs; overdue records are cleared on restart or a subsequent request. Operator recovery backups may retain earlier records until the operator removes or rotates those backups. Short-lived identity and installation proofs expire independently. Account, fleet identity and security records remain until removed by the operator.
Your installed fleet panel owns its own database, vault key, agents and passkeys. A Hub account cannot read that vault or enqueue operations on the installed panel. The Hub makes a limited HTTPS identity check of the controller you register.
Your controls and contact
In Sign-in methods, you can remove a linked provider after verifying your passkey; removal also revokes its Hub sessions. You can revoke provider authorization in your Google or GitHub account. Removing a linked method does not delete the Hub account or an installed fleet. Contact the operator to request access, correction or deletion of Hub account data.
Contact the operator at alexdavidov127@gmail.com.
Google sign-in data is handled in accordance with the Google API Services User Data Policy, including its Limited Use requirements. This Hub does not request access to Gmail, Drive or other Google account content.