Account information
We store your name, email, password hash, email-verification state, account permissions and login/session metadata. Passwords are stored as salted hashes, not readable account passwords. Email codes are stored as keyed digests with expiry and attempt limits. API keys are displayed once and their digests, scopes and lifecycle metadata are retained.
Phones, connections and diagnostics
The service stores phone identifiers, names, relay assignments, pairing credentials, proxy connection credentials, VPN profiles, selected settings and sharing permissions. Operational information can include app/device version, online status, battery, network and SIM capabilities, exit IP, byte counters, connection events and diagnostic errors. Enabled phone-management features may process authorized telephony information. Diagnostic records can include network endpoint metadata. HTTPS destination content is carried by the tunnel without application TLS interception; this does not mean all proxy traffic or metadata is encrypted or unrecorded.
Billing and support
We store plans, subscription periods, payment orders, the network/asset and transaction identifiers you submit, approval history and support conversations. Public blockchain transactions are not private to Maskproxy. Support staff can access conversations and add staff-only notes that are not shown to customers. Do not send passwords, API secrets or private wallet keys in chat or email.
Purpose and access
We use this information to operate your workspace and phone connections, enforce permissions and plan limits, verify email ownership, reconcile payments, resolve support requests, protect against abuse and recover service data. Phone owners, explicitly authorized shared users and authorized administrators have access according to their role. Shared users receive only information permitted by their granted permissions. Staff access is separate from customer access.
Providers and cookies
Hosting and relay providers process network traffic and stored service data. Zoho Mail handles the official mailbox and application emails, including recipients and message contents. Their processing may occur in other countries and is subject to their own policies. The website uses an essential session cookie and a saved language preference. These pages do not add advertising or third-party analytics cookies.
Retention and your requests
Account, subscription, audit and support histories are retained for service operation and review; there is currently no single automatic deletion period covering all of these records. Expired challenges and short-term rate-limit records have separate cleanup rules. Encrypted backups can retain earlier records. You can update account information and revoke keys or sharing permissions in the dashboard. Contact support to request access, correction or deletion of other personal information, or to ask about retention. We review requests against account ownership, operational dependencies and applicable legal requirements; deletion is not represented as immediate removal from every backup.
Security and contact
We use access controls, HTTPS for the dashboard, authenticated phone transport and encrypted recovery archives. Protection also depends on your device and client configuration; no system can promise absolute security. Report suspected unauthorized access or privacy concerns to the official contact below. Updates to this policy are published here with their date.