Security & privacy

#🔒 Security and privacy, in plain words

mobyx runs on your computer. Your workflows, your data files, your screenshots and your passwords are stored here, not on our servers. What mobyx does use online is an account service, so it can know who you are and what your plan includes. This page says exactly what that is and how it is protected.

#Why mobyx has an account service

It is a hosted, widely used database and sign-in service. Running our own would mean building account security, password storage and a database from scratch -- which is how products end up with weak ones. Using a specialist service means those parts are done properly and kept up to date. It holds:

• your account (email, name, phone you entered)
• your plan and its expiry
• your sign-in history and the computers signed in
• your payment records (the invoice, amount, status)
• the Community and marketplace content we publish
• the relay that carries a Remote phone's commands

It does not hold your workflows, your data files, your screenshots, your credentials or your API keys.

#How it is protected

Your password. It is handled by the sign-in service and stored only as a salted hash. mobyx never keeps it on this computer, and we cannot read it.

Staying signed in. The app keeps a renewable sign-in token, encrypted with Windows DPAPI so it only opens for your Windows account, and written so a crash cannot corrupt it. Signing out deletes it.

Who can see what. Every table has row-level security enforced by the database itself: you can read your own rows and nobody else's, whatever any app or website asks. Administrator actions run on the server, check that you are an administrator there, and are written to an audit log.

Your plan. Checked against the server's clock, not this computer's, so changing the date does not extend it.

Payments. Crypto only, straight to our wallet: no card details exist to be stolen. The address you pay is printed on your invoice and stays the same for that invoice.

What you install. Updates and marketplace plugins are checked against a SHA-256 checksum before they are used. A file that does not match is refused.

This computer. Credentials, Secrets and API keys are encrypted with Windows DPAPI. Free-plan limits and plan checks are enforced inside the app's own code, not only on its buttons.

#What is sent, and to whom

Your account -- email and password when you sign in or sign up, the name and phone you enter, and an id for this computer so the device limit on your plan can be enforced. Sign-in times are kept so you can see them in Settings → Security.

Usage statistics (optional) -- asked once, with the full list in front of you; "no" is a complete answer and everything keeps working. If you agree: when mobyx opened and closed, its version and Windows, the country and city of its connection, how many devices of which kind were used, and that a workflow ran. Never what it does or sees.

Update checks (GitHub) -- the app asks GitHub for the latest published version number. Nothing about you or your workflows is included.

Your AI provider -- only when you have saved an API key AND a node or the assistant actually asks for help. What goes: the text list of what is on the phone screen (labels, ids, positions), your description of the target, and for the assistant your question plus the names of the nodes on your canvas and the devices connected. A screenshot is sent only if your provider supports images and the screen has no readable elements at all.

#What never leaves

Your workflows. Saved as files on this computer.
Your data. Excel/CSV/JSON sources are read locally; rows are never uploaded.
Credentials and Secrets. Encrypted on disk with Windows DPAPI, tied to your Windows account.
Your API keys. Encrypted the same way, and sent only to the provider they belong to.
Screenshots, recordings and templates. Written to your own folders (Settings → Application).
What the AI learned. Element ids and labels, in a plain JSON file you can read or delete.

#Staying in control

AI is off until you switch it on, and switching it off stops anything being sent immediately -- the Smart nodes simply work as they did before.

Settings → AI shows what has been learned and lets you forget it, and lets you remove a saved key.
Settings → Application shows exactly which folders the app writes to.
Settings → Security shows this computer's device id and your recent sign-ins.

Everything the app stores lives in one folder, so you can inspect or delete it yourself.

#Your phones

mobyx talks to phones over ADB from this computer. For a Remote device, the Mobyx Relay app relays that ADB traffic through the mobyx account service so the phone can be reached over the internet -- the relay carries device commands, and the pairing is yours to remove at any time from Device Manager.

#Plugins are kept apart from mobyx

Plugins are code written by other people, so they live in a fenced area, away from mobyx itself.

What a plugin can use. A small public surface: the node and executor base classes, the phone (ADB) actions and the mobyx SDK, plus the usual libraries for text, files and the web.

What it cannot reach. Your account, your plan, payments, saved secrets and API keys, the AI settings, usage reporting, the Mobyx Device and browser engines. A plugin that tries to import any of them, or to go around the rule, is refused and does not load.

Private plugins. A Marketplace plugin can be published with private code: it installs and works, but its code is locked, it is not offered in the editor, and it will not run if the file is changed.

Marketplace plugins are published only by the mobyx team and checked against a SHA-256 checksum before they are saved. A plugin you write or install from elsewhere is your own choice, so treat it like any program from someone you do not know.