HMDev Account
One place for your identity, developer access, saved channels, and encrypted backups.
Sign in to your HMDev account
One account for every HMDev app and game. It keeps your saved channels and becomes your developer identity when API access is approved. Developer keys remain protected by their own scoped session, but both experiences appear together in your profile. You never need an account to join a room — that stays one click.
Your account
Used across Rooms, saved channels, Drive backup, developer access, and administrator access.
Build with your HMDev account
Checking whether this verified identity has developer access…
How you sign in
Sign in with Google as well as your password. Your password keeps working.
This account signs in with Google and has no password. If it had one before, the password was removed when Google was linked to the same email, so that only the owner of that address can sign in. Set a new one to sign in where Google is not offered, such as a game’s sign-in screen. Google can be unlinked only once the account has a password, so that it always keeps a way in.
Saved channels
Kept on this device only. We never store your channels on our servers — including the name you use in each channel. If you lose them, ask someone in the room to share the link again.
Being straight about what that is worth: this is custody, not incapability. Your channels sit in this browser’s local storage, and every app on this site runs on the same origin, so any of them could read them. We ask them not to, and the platform API never hands an app a channel password. That is a rule we keep, not a wall that would stop us.
Nothing saved yet. Tick Save this channel when you join a room.
Backup
Your saved channels and their per-channel join names live in this browser. Export a copy to move them to another device. The file is encrypted with a key held by your account, so you must be signed in as yourself to open it — a copy that leaks is ciphertext to whoever finds it.
Destroy the backup key
If a backup file of yours has ended up somewhere it should not be, destroying the key is what makes it unreadable — it is the only remedy, and it cannot be undone.
Google Drive
Keep the same encrypted file in your own Google Drive, so a new device can pick it up after you sign in. Google stores it in a hidden folder for this app and only ever sees the encrypted bytes — the key that opens it stays with your account here.