Your data stays on your device
MokoHub is local-first. Your list of services, your workspaces, your settings, and your profile are all saved right on your own computer. There is no MokoHub account to sign up for and no central MokoHub server storing your information.
This means the everyday things you do in the app do not get sent off to a company server somewhere. The app simply remembers your setup locally and shows you your dock the next time you open it.
What actually leaves your device
Very little traffic leaves MokoHub itself. The connections that do happen are the ones you would expect from any app that loads websites:
- The services you open. When you use Gmail, Slack, your intranet, and so on, those pages talk directly to their own websites, exactly as they would in a normal browser tab.
- Update checks. The app periodically checks a trusted location to see whether a newer version of MokoHub is available.
- Service icons and templates. Small, non-personal files used to display your service tiles correctly.
Your account passwords for those services are never stored by MokoHub. You sign in to each service through its own web page, and MokoHub keeps that logged-in session on your device so you do not have to sign in every time.
Each service is kept separate
Every service you add runs in its own isolated space. This is called partition isolation. In practical terms:
- One service cannot read another service's cookies, logins, or saved data.
- A problem on one site cannot leak into another.
- You can even keep two accounts of the same type separated.
The one intentional exception is Google. So that a single sign-in covers your whole Google Workspace, all of your Google tiles (Gmail, Calendar, Drive, and so on) are grouped to share one login session. Signing into any one of them signs you into the rest. This is by design and only applies to the Google group.
Domain lock keeps pages where they belong
MokoHub includes a safety feature called domain lock. It makes sure a service tile can only navigate to trusted web addresses. If a page ever tried to redirect you somewhere unexpected, for example a fake login page, domain lock can stop it.
Domain lock runs in one of three ways, depending on how your organization set it up:
- Off - no restriction.
- Warn - unexpected page changes are recorded but still allowed. This is often used at first, to confirm the trusted list is complete.
- Enforce - page changes to untrusted addresses are blocked outright. Managed and kiosk setups usually run in this mode.
Your normal sign-in steps, including the Google sign-in and consent screens, are covered by the trusted list, so signing in works smoothly while unexpected redirects are still caught.
Sign-in and identity
The Get started button on the welcome screen simply opens your dock. It is not a real account login and it does not send any credentials anywhere.
Your real identity comes from signing in to each service, most importantly your Google Workspace account, directly inside that service's page. MokoHub does not see or keep your Google password; Google handles that within its own secure sign-in. Where your organization uses Google as a single sign-on provider, signing into Google once can carry through to your other internal tools automatically.
Updates you can trust
MokoHub updates itself from a trusted, verified source, and the installer it downloads is digitally signed. That signature is checked before anything is installed, so you can be confident an update genuinely came from Moko and was not tampered with along the way.
Note that the older in-app "What is new?" release-notes panel has been removed. Updates still arrive and install the same way; there is simply no separate changelog popup inside the app.
Staying signed in
By default, your service logins are saved on your device so you are not asked to sign in every time you open MokoHub. A managed setup will not silently clear your logins on launch. If you ever find yourself signed out unexpectedly, it usually means your session expired or local storage was cleared, and signing back in resolves it.
Quick summary
- Local-first: your setup and data live on your device, not on a MokoHub server.
- Isolated: services are walled off from each other, with Google grouped on purpose for single sign-on.
- Protected navigation: domain lock keeps tiles on trusted addresses.
- No stored passwords: you sign in to each service directly; MokoHub just remembers the session locally.
- Verified updates: updates are signed and checked before installing.