Mobile Proxies US Privacy Policy

Revision 2026-11-08. This policy is organised like a data map: for each system we run, what is stored, why, for how long, and who can see it. Three facts first. We keep only what running accounts and lines requires. Traffic content crossing a line is neither inspected nor retained. Personal data is never sold or handed over for marketing. The controller is Mobile Proxies US, operator of mobileproxiesus.com and cp.mobileproxiesus.com; requests go to [email protected].

Account records

Stored: email address, password hash, registration time, the IP address and user agent of the registration request, two-factor secret if enabled, your API key, language preference, and the support conversations you have with us including a Telegram username if you use the bot. Not requested: name, postal address, phone number. Purpose: operating and securing the account. Retention: for the life of the account and 30 days after deletion, except as noted under payments.

Payment records

Stored: amount, currency, method, time and provider reference for each payment; balance history; for card and PayPal payments the provider's result plus only the final digits of the card, never the complete number; for crypto the receiving address, transaction hash and amount; for Zelle and wire the reference you supplied and the sender name as shown on the transfer. Purpose: billing, refunds, dispute handling, tax and accounting obligations. Retention: the period required by accounting and tax law, which outlasts account deletion.

Line and API records

Stored per line: plan, metro, carrier, device type, issued credentials and their issue times, every exit IP change with its time, the time and source IP of each connection to the proxy endpoints, byte counters per UTC day (used for the fair-use rule), and API calls with their time, source IP, path and result code. Purpose: billing, fault diagnosis, answering abuse complaints quoting an address plus a timestamp, and showing a carrier that particular traffic came from our device.

Not stored: which hosts you reach, request or response content, DNS lookups, nothing from which your activity could be rebuilt. The proxy forwards packets; it writes no payload logs. Retention: connection metadata 90 days, then deleted, unless a specific record is required for an open complaint or a legal process; byte counters for the plan period plus 90 days.

Website and dashboard records

Stored: ordinary web server logs (page, time, IP address, user agent) for 30 days, for security and capacity. The public site loads no analytics, advertising or social media scripts. The dashboard sets a login session cookie and a language cookie; neither follows you across sites. If you use a referral link, we record which account referred which, in order to credit the referrer, and nothing further about the referred person.

Recipients

Payment providers process payments under their own policies. Hosting and email providers store data for us under contract and on our instructions. Carriers see a line's traffic as they see any subscriber's; when answering a network abuse report we may identify the line and account to the carrier. Law enforcement or courts receive data when a valid demand under law applicable to us requires it; we tell the account holder when permitted. Nobody else. Personal data is never sold, rented or passed on for marketing.

Your rights and how to use them

You can view and change your email, password, two-factor and API keys in the dashboard. You can ask for a copy of all personal data we hold, for corrections, or for deletion of your account. Deletion removes account and line records within 30 days, keeping only payment records required by law and records needed for an unresolved complaint. We honour the rights granted by data protection laws (including those of the EEA, the UK and California) for every customer regardless of location, and we answer within 30 days. Write to [email protected] from the account's email address.

Security measures

Passwords hashed; dashboard and API served over TLS; proxy and VLESS connections encrypted wherever the protocol supports it; production access restricted to the people who need it, and logged; devices housed in locked facilities. Should a breach touch your data, we notify you without undue delay, with what we know and what we recommend.

Changes to this policy

The revision date at the top moves when the policy changes. Significant changes are posted in the dashboard before they apply. Earlier revisions are available from support on request.

Questions