Account and environment
Each store preserves its own sign-in, browser settings, and extensions without repeated browser cleanup.
E-commerce workflow
Keep store accounts, regional exits, and owners aligned.
Give every store its own account environment, then manage proxies, extensions, notes, and teammate access in one workflow. Verify the setup before expanding it.
MaskPilot 
Keep three relationships clear
More stores make account, exit, and owner mapping more important.
This workflow does not promise platform outcomes. It explains how to reduce mixed environments, mismatched proxies, and missing handoff context.
Region and exit
Organize proxies by region and purpose, then confirm the current exit and timezone through the actual route before launch.
Store and owner
Assign account visibility first, then allow account, proxy, or AI actions by responsibility. Use a separate one-time flow to hand off a copy.
Store workflow
Start with a test store and build a workflow that can be handed off.
Verify the environment, network, sign-in, and exit path with a lower-risk test account before applying the management pattern to more stores.
Create a separate environment for each store.
Record the store purpose, region, and owner before creating the account. Language, timezone, WebRTC, the stable seed, and common settings stay with it.
- Cookies and site data stay with the account
- Core fingerprint settings remain stable across launches
- A copied or received account gets a new identity
- Validate sign-in and exit with a test account
Keep the proxy region aligned with store purpose.
Proxy health is tested on the current computer. Before launch, MaskPilot uses the actual route to read the exit timezone and stops if it cannot confirm one.
- Organize proxies by region, purpose, and notes
- Do not assign one entry proxy to several accounts
- Test multi-hop prefixes to locate failures
- Do not substitute stale cache for the current exit
Enable only the extensions and access each store needs.
Extensions are selected per account and teammates receive access by responsibility. Before an upgrade or role change, review the stores that will be affected.
- Extensions do not load into every account automatically
- Compatibility is checked again before launch
- Account visibility and feature permissions stay separate
- Team features depend on the current plan
Preserve boundaries during handoff and recheck after recovery.
One-time sharing creates an independent copy rather than transferring ownership. A recovery path is created after account close only when the current device allows upload.
- A sharing Token can be used once
- The receive result retains necessary audit fields
- Encryption happens on the current device before upload
- Recheck proxy, extensions, and teammate access after recovery
Usage boundaries
Clear state does not replace authorization or platform rules.
Use stores, proxies, extensions, and data that you own or are authorized to operate, and follow applicable law and third-party terms.
No platform outcome promise
Separate environments do not guarantee approval, traffic, or avoidance of platform controls.
Verify before expanding
Test a new region, proxy, extension, or browser change before applying it broadly.
Plans control team features
Member access and capacity follow the active plan shown in the client.
Keep independent backups
Sync and recovery reduce device-change risk but do not replace backup of important business data.
FAQ
Questions before you start
Does every store need a separate account environment?
Create a separate environment for each real sign-in so cookies, site data, extensions, and browser settings do not mix.
Can one proxy be assigned to several store accounts?
One entry proxy is not assigned to several accounts. Design the proxy library around the actual business boundary when network resources must be reused.
Does handoff transfer the original account?
No. One-time sharing creates an independent copy for the recipient while the original stays with its owner.
Can work continue immediately on another computer?
The original device must allow upload and finish sync after a normal close. Recheck proxies, extensions, capacity, and assignments after recovery.
Start with one test store
Verify one complete store workflow first.
Download MaskPilot and use an authorized test account to check the environment, proxy, and extensions before expanding the workflow.