Privacy Policy

1. Who is responsible

This notice covers data processed in operating ProxyHub at proxyhub.team. Contact the support address below about this processing or your rights.

Privacy requests can be sent to support@proxyhub.team.

2. Information we process

Account and sign-in information

When you choose Google or Telegram sign-in, we receive the profile fields that provider makes available: a provider-specific identifier, name, and, where supplied, email, username, picture URL and related profile attributes. We assign an internal account identifier and retain session and sign-in security records. We do not receive your Google or Telegram password.

Payments and purchases

We store order and invoice references, product, quantity, price, payment method and status, account-credit movements, reservations, timestamps and information needed to reconcile payment and fulfilment. A cryptocurrency payment is not necessarily anonymous: transaction information may be public on its blockchain and may be linked to your invoice.

Referrals

Referral records connect a new account to an inviter and record eligible completed purchases, reward amounts and timestamps. Inviting users see their own link, referral balance and aggregate counters, not a list of invited users, their contact details or their individual purchases. Support staff can review attribution and reward records to resolve discrepancies.

Purchase terms and withdrawal notices

For new orders we record the presented policy version, your confirmation and its time, and any express request for immediate service. If you submit a withdrawal notice in your account, we keep its statement, order and account references, receipt time and acknowledgement for handling the request. No additional IP address or browser fingerprint is collected specifically as evidence of these checkboxes.

Proxy provisioning and usage

We store provider subaccount details and proxy access credentials needed to deliver your service, purchased allowances, rental identifiers and expiry, selected service settings, and provider-reported balance and usage history. Access or rotation links can authorise actions; treat them as credentials.

Support and action history

We record important account and service events, including sign-ins and session endings, order transitions, credit reservations and adjustments, activation and renewal, generation outcomes and mobile rotation actions. Records can include internal account and order references, timestamps, result codes and relevant amounts. We also receive information you choose to send to support.

Technical and security information

The website, its hosting and security systems may process IP addresses, request times, browser or device information and error records to serve requests, prevent abuse and investigate failures. Browser storage used by the site is described in Cookies and browser storage.

The website's support audit history is an account-action history, not a record of the contents of every proxied page. This is not a claim that our proxy servers, carriers or upstream providers keep no operational connection records. Their actual processing must be assessed separately.

Do not send support private keys, seed phrases, sign-in tokens, unnecessary identity documents or unredacted proxy credentials.

3. Purposes and legal grounds

Where data-protection law requires a legal basis, the intended bases are:

• Providing the requested service: creating an account, authenticating you, provisioning proxies, accounting for usage, processing an order and resolving a service request.
• Legitimate operational and security interests, where permitted: protecting accounts, detecting abuse and duplicate transactions, diagnosing failures, maintaining a reliable transaction history and establishing or defending claims. These interests must be balanced against your rights.
• Legal obligations: records or disclosures required by applicable accounting, tax, payment or other law, once the relevant obligations are identified.
• Consent where required: optional tracking or other genuinely optional processing. We do not treat accepting general terms as consent to every use of personal information.

Some account and transaction information is needed to provide the service. Without it we may be unable to authenticate you, reconcile a payment or supply a proxy. We do not currently load optional analytics or advertising trackers in the reviewed website code.

Automated checks help authenticate users, prevent duplicate transactions and restrict suspicious requests. You can contact support about a blocked or disputed action. This does not replace any right to human review available under applicable law.

4. Recipients and service providers

• Google or Telegram: the provider you choose handles its sign-in flow and returns account information. Its own privacy terms also apply to its services.
• Heleket: receives invoice amount, currency, order reference and an internal account reference to create and reconcile a payment. Information entered on its payment page is also subject to its privacy notice.
• Proxy suppliers: Third-party providers of residential and mobile proxy infrastructure and the mobile service servers involved in your order receive the subaccount, credentials, allocation and configuration data needed to provide it. Networks carrying proxy connections necessarily handle connection information.
• Infrastructure and support: hosting, backup and communication services process information needed for their functions. Authorised support personnel may consult account and transaction history to resolve issues.
• Legal recipients: information may be disclosed in response to a valid legal requirement or as lawfully necessary to investigate abuse and establish or defend claims.

We do not sell customer account information. We do not describe all recipients as mere processors: some providers determine their own purposes under their own policies.

5. Retention and deletion

Account, purchase, usage and support information is retained while needed to provide services, reconcile transactions, deal with disputes and satisfy applicable recordkeeping requirements. The relevant criteria are whether the account or service remains active, whether a payment or claim is unresolved, and whether a specific legal retention period applies.

Session expiry ends access but does not automatically delete the account or historical actions. The current support-action archive has no automatic age-based purge. Account closure is not an assurance of immediate deletion from every database or backup; deletion requests require review of the information and any continuing lawful need.

6. Your choices and rights

Depending on applicable law, you may request access, correction, erasure, restriction, portability or objection to processing, and withdraw consent for processing based on consent. You may also complain to a competent data-protection authority. Not every right applies in every situation.

Contact support with enough information to locate your account. We may ask for proportionate verification to protect it, but not unnecessary sensitive information. We will explain any lawful reason we cannot fulfil all of a request and follow applicable response deadlines. Withdrawing optional consent does not affect the legality of earlier processing or prevent essential processing supported by another valid basis.

For information controlled by Google, Telegram or a payment provider independently, you may also need to exercise rights directly with that provider.

7. Security and changes

We use authenticated access, session controls and restricted support access to protect account information. No system can guarantee absolute security. Keep private access links confidential and report suspected compromise promptly.

Services are not intended for children under 18. Contact us if you believe a child has supplied personal information so we can review it and take appropriate action.

Changes to this notice will be dated. Material new processing will be explained, and fresh consent will be obtained where required. Continued use is not treated as blanket consent to a new optional purpose.