Mobile Automation Data Security: Local Deploy & Account Isolation

Do not collect, do not store, do not upload

iEasyRun has three hard limits.

Device information, task content, and execution records stay inside the local environment. They are not sent to our servers. We do not run a backend that receives this data.

Screenshots are not written to disk or to a database anywhere in the chain. Device photos and screen images are not stored anywhere.

There is no ad profiling, no behaviour tracking, and no sale of data to any company or person. The free edition does not lower the privacy standard.

Two delivery forms. Installed in an office or at a customer site, both are local:

Form	Description	Fits
Windows portable	Double-click the exe, SQLite in a single file, no Docker	Individuals / small teams / a quick try
Compose standard	docker compose up -d starts app + mysql:5.7 + redis	Company intranet / several staff working together

The runtime stays in your hands, on a local computer or an internal server. Data does not leave your hardware. When a compliance review needs it, you can inspect the database contents and the log files directly. It also works with no network, as long as the devices connect straight over USB or Wi-Fi.

Tenants, login sessions, and the cloud comparison

Many studios start with 3 to 5 phones, then grow to dozens or even a hundred. Once more people are involved, someone has to decide who manages what and who can see what. Multi-tenant plus RBAC is for that.

The domain model:

Tenant
  └── Dept (tree)
        └── User ──< many-to-many >── Role
                                    └── Menu (tree, routes/buttons)
                                    └── Permission (API/button identifiers)

Role	Scope	Typical user
super_admin	All permissions (across tenants)	IT lead / super admin
admin	All business inside this tenant	Division admin
operator	Devices / tasks / AI	Operations staff
viewer	Read-only	Auditor / non-technical user

Business data always carries a tenant_id, and tenants are strictly separated. On the same server, tenant A’s devices and tasks are invisible to tenant B.

Login is tightened in a few places. Three fields are required together: tenant code, username, and password. The error is always “wrong account or password”. It does not say whether the tenant is missing or the password is wrong, so the two cannot be enumerated apart. Too many failed logins, past a threshold, locks the attempt for a while. Sessions use JWT. The standard edition can renew them with a Redis blacklist. The portable edition manages them in the database.

More teams are moving from cloud phone control to a local install. The difference is where the data stays:

Dimension	Cloud	Local install (iEasyRun)
Account information	Passes through the provider’s servers	Stays in your environment
Operation records	Sit in their database	Stay on your own computer
Compliance audit	You need them to produce the evidence	Inspect the local database directly
Adding capacity	Add a tenant when you need one	Add devices and reinstall

Accounts, records, and audits stay in your own environment because of how it is deployed. Install details are in installation.