Conditions of use

Terms of service

Before using MaskPilot, review the boundaries for accounts, the desktop client, plans, data, and team collaboration. Registering, downloading, or continuing to use the service means you agree to follow these conditions.

Updated · 2026-09-06
01

Service scope

MaskPilot provides browser account environments, fingerprint configuration, proxy and extension management, team permissions, sync and recovery, desktop updates, and local AI connections. Available features depend on the current client version, plan, and operating configuration.

  • The current public desktop release targets Windows x64.
  • The website provides product information, account sign-in, plan display, documentation, and downloads. It does not create plan orders in the browser.
  • Features still in testing, staged rollout, or incomplete release are not public commitments.
02

Accounts and credentials

Provide valid registration information and protect passwords, verification codes, device confirmation codes, and local AI Tokens. Approve only a client sign-in you started when both codes match.

  • Do not share passwords, verification codes, or complete Tokens.
  • Remove unfamiliar devices and contact support after a suspected account compromise.
  • Teammate accounts must stay within the work scope assigned by the owner.
03

Authorized and compliant use

Use MaskPilot only with accounts, proxies, extensions, data, and business environments you own or are clearly authorized to operate. You must follow applicable law, platform rules, and third-party service terms.

  • Do not use the service for unauthorized access, fraud, malicious automation, permission bypass, or disruption of another system.
  • Do not use team, sharing, or AI features to expand access beyond the current user’s authority.
  • You are responsible for the source and authorization of imported proxy configurations, local extensions, and tasks sent to AI.
04

Plans, orders, and payment

The website displays the current plan catalog. Purchases, renewals, and upgrades start in the signed-in desktop client. Amount, term, payment channel, and order state follow the client display and backend record created for that order.

  • Available payment methods can change with operating configuration.
  • Do not pay the same order twice; wait for the client to refresh an order that is still processing.
  • Refunds, expiry, and manual review follow the order channel, state, and actual processing result.
05

Data, sync, and recovery responsibility

Sync and recovery reduce the risk of device changes and accidental deletion, but they do not replace independent backup and verification for important business data. Each device controls whether it can upload account data.

  • Close accounts normally and allow the sync flow to finish.
  • Coordinate a normal close and confirm sync results before switching devices. Preserve local data after a version conflict and do not remove local process lock files.
  • After recovery, recheck proxies, extensions, plan capacity, and teammate assignments.
  • Local changes that were never synced are not guaranteed to recover on another device.
06

Updates, availability, and changes

MaskPilot may update the client, browser runtime, extension policy, and service interfaces for security, compatibility, fixes, or product changes. A forced update is reserved for cases where an older version can no longer run safely or compatibly.

Maintenance, networks, third-party services, or events outside reasonable control can cause temporary unavailability. We aim to keep failure states and recovery paths clear but do not promise uninterrupted availability at all times. Material term changes update the date on this page.