Safety and local data

Understand Google sign-in, local profile data, proxy secrets, and agent access.

Before you start

Sign in only in Chrome
The app does not store your Google password or 2FA code. Enter these directly into Google’s page in the correct profile’s Chrome. Plain Chrome sign-in does not attach app control while you type your password.
Google may still require MFA, CAPTCHA, or another account check; complete it yourself.
Treat profile folders as sensitive
Each profile keeps cookies and history in its own local directory. Open Cài đặt → Chung → Dữ liệu và an toàn → Mở thư mục to locate app data. Do not post that folder or a backup publicly.
The app works locally, but creating and downloading through Google Flow still requires network communication with Google and media services.
Protect proxy and agent credentials
Proxy passwords are encrypted using Windows on this machine. If the vault is unavailable, password-protected proxies are blocked. A proxy failure does not trigger a silent switch to your real IP.
Local MCP/REST access uses separate API keys for applications. Give keys only to trusted clients and review agent limits.
Back up before changing program files
Follow updates and backup. Include both the app data directory and the actual results folder. Removing the program folder does not necessarily remove stored profiles or Library files.
Do not assume a backup of Windows-encrypted secrets will work on another machine.

You know which data is sensitive, where to find it, and what to protect before sharing or updating.

Does local-only mean no internet is used?

No. Settings and stored app data are local; Google sign-in, Flow generation, and media downloads require network access.

Can I continue if the proxy fails?

Repair or check the configured proxy first. The app does not silently switch a proxy profile to your real IP.