Privacy notice
Version: 2026-09-23
What is stored
WorldProxy stores a verified phone number for phone accounts or an email for earlier accounts, a one-way password hash, server-side session records, order parameters, balance ledger entries, and security audit events. Phone numbers are encrypted at rest; an irreversible keyed identifier is stored to prevent duplicate accounts and repeated trials.
Sign-in security
For account security and incident investigation, WorldProxy records registration, sign-in, sign-out and password recovery events: time, result, sign-in method, the connection IP address and the browser User-Agent when available. Failed attempts for known accounts are stored within rate limits. These records are available only to administrators, including in customer dossier exports. They do not contain passwords, session tokens or browsing history.
Registration protection
When enabled, Yandex SmartCaptcha processes technical browser and connection information to protect registration from automated requests. WorldProxy sends the verification token and connection IP address to Yandex for validation; email, phone, password, orders and balances are not included in this request. Local protection uses temporary keyed identifiers for ten minutes, hourly outcome totals for seven days, and daily verification counts for 33 days to control usage. Expired entries are removed when the protection is next used. This security check is separate from optional advertising analytics.
Phone verification
To create a phone account or recover a password, WorldProxy sends the entered number and the request's public IPv4 address to SMS.RU solely to place a verification call. WorldProxy stores the returned call identifier, a protected hash of the four-digit code, timestamps, and bounded attempt records. The code expires after 10 minutes and cannot be reused. A successful password reset signs out all previous sessions.
Payments and receipts
When a customer creates an SBP payment, the service sends the bank the amount and technical operation identifiers needed to create and verify the dynamic QR code. To issue a receipt, the seller sends the online cash register the amount, service description, tax parameters, payment identifiers, and the email address entered for the receipt. Bank passwords, one-time bank codes, and card details are not collected by the service. Payment and receipt records are retained for accounting, reconciliation, refunds, and dispute handling.
Free trial
For one-time trial enforcement and IP-bound access, the public IPv4 address used for the claim is stored with the trial record. WorldProxy also links the trial to the verified phone identifier and uses a signed, HttpOnly first-party device cookie with an irreversible HMAC device identifier. Browser contents and hardware fingerprints are not collected for this check.
Protection and disclosure
Sessions use protected cookies, and proxy credentials are encrypted at rest. Data is disclosed only when required to provide the selected service or by law.
Account control
The account owner can sign out from the current session and request account restriction through an administrator. Financial and security audit records may be retained where required for integrity and dispute handling.
Optional public-site analytics
With consent, WorldProxy records the first validated advertising visit on public pages and may link its source, numeric campaign and ad tags, and broad device type to a newly created account. A random browser identifier coordinates withdrawal across tabs. The attribution cookie lasts 30 days; visits and account campaign links are retained for up to 365 days and removed when consent is withdrawn through Analytics settings. Revoked browser identifiers are blocked for 30 days to reject delayed writes. Existing accounts are not backfilled. Confirmed top-ups, fulfilled purchases and returns are reported internally in aggregate; top-ups are not service revenue. Financial event markers without campaign or contact details may remain after withdrawal for up to 365 days from account creation. Raw query strings, click IDs, IP addresses and full user agents are not stored in these records. Yandex Metrica loads only after consent and receives sanitized public page addresses and a registration event without account details. Other query parameters are removed. Session replay, click maps, form capture, private-page analytics and offline click-ID uploads are disabled. Proxy credentials, checker input, account email, phone, password, provider identifiers and support messages are not sent by WorldProxy analytics code. The browser choice is stored locally; use Analytics settings to withdraw it and request server-side deletion.
The current advertising choice also covers an explicit Buy click on a public proxy page and linking its source to a new email or phone account. A previous browser choice for public Yandex Metrica alone does not authorize this new attribution; the site asks again before recording it. The internal funnel counts an accepted cart checkout from existing order and payment records, without tracking private page views or sending those records to Metrica.