proxysale
Sign in Get proxies

Language

Privacy policy: what data we collect, share and keep

This policy lists the data ProxySale receives, the purposes of processing, the recipients and the retention periods, and explains how you can manage your details.

Last updated: October 31, 2026

In brief

  • Traffic content stays unloggedWhich sites you open through the proxies and what you send there never reaches the Service’s records.
  • We collect littleEmail, payments, access settings and technical accounting: what accounts and billing cannot run without.
  • Shared only as neededPayment systems, suppliers, Cloudflare, Metrica and Telegram receive only what their part of the job requires.
  • You decideSupport will show what is stored about your account, fix mistakes or delete what is not needed.

1Who is responsible for the data

  1. 1.1

    The data controller is the administration of ProxySale (“we”). The policy applies to proxysale.biz, the cp.proxysale.biz panel, the @proxysalebizbot Telegram bot and the support chat on the site.

  2. 1.2

    The policy is part of the terms of service and shares their definitions. By starting to use the Service you confirm you have read it. Processing the Service cannot work without is mandatory: if it does not suit you, decline the Service.

2Data we hold

  1. 2.1

    Account record: email, sign-in details, panel language, account creation date.

  2. 2.2

    Verification before the free test: whatever you filled in on its form.

  3. 2.3

    Proxy access: whitelisted server IPs, issued lists and connection lines, the plans, countries and cities you chose, sticky session settings.

  4. 2.4

    Technical accounting: how much traffic went through, when access was created and used, how many connections there were and which errors occurred. These details serve billing, authorization and protection against abuse.

  5. 2.5

    Payments: amount, currency, payment method, date, transaction ID and, for crypto, the sender wallet and the transaction hash. Card details stay with the payment service.

  6. 2.6

    Affiliate activity: whom you brought, what was credited, which wallet receives payouts.

  7. 2.7

    Requests: messages in tickets, the chat, the bot and emails, along with attachments.

  8. 2.8

    Site visits: hosting and Yandex Metrica register the IP, browser type, pages viewed and time.

  9. 2.9

    Referral mark: for 90 days a cookie stores the partner code and the origin of the visit (UTM tags, ad click ID, referring page, landing page) so that the partner and the channel are credited at sign-up. The site language is kept in browser memory.

  10. 2.10

    Free proxy downloads: before handing over the file, Cloudflare Turnstile makes sure a human asked for it.

3What happens to your traffic

  1. 3.1

    The Service keeps no record of the pages you open through the proxies or the content you send.

  2. 3.2

    For billing, authorization and anti-abuse, service details about connections are stored: volume, time, addresses. Their scope is limited to these tasks.

  3. 3.3

    Suppliers, carriers and data centers that connections pass through may keep their own logs under their own policies. ProxySale has no say over them and bears no responsibility for them.

  4. 3.4

    Proxies do not give absolute anonymity: the destination site and the nodes in between see whatever reaches them over the connection at the technical level.

4Purposes of processing

  1. 4.1

    Issuing proxy access, keeping the balance and counting traffic.

  2. 4.2

    Accepting payments and crediting affiliate earnings.

  3. 4.3

    Support replies and notices about orders, your balance and changes to the terms.

  4. 4.4

    Spotting abuse, fraud, multi-accounts and attempts to get around a block.

  5. 4.5

    Reviewing complaints from sites, suppliers and third parties.

  6. 4.6

    Complying with the law and protecting the Service’s interests.

  7. 4.7

    Statistics and developing the Service.

5Recipients of data

  1. 5.1

    Payment systems and crypto gateways receive what a payment cannot go through without.

  2. 5.2

    Infrastructure suppliers receive technical data on access and load to issue access, count traffic and look into complaints. Account contacts reach them only when a complaint cannot be resolved otherwise or the law says so.

  3. 5.3

    Cloudflare hosts the site, repels attacks and runs the Turnstile check.

  4. 5.4

    Yandex Metrica measures site traffic.

  5. 5.5

    Telegram runs the support bot.

  6. 5.6

    Lawyers and consultants are brought in when the Service has to defend its rights.

  7. 5.7

    Competent authorities receive data on a lawful request.

  8. 5.8

    A successor receives the data if the Service changes hands.

  9. 5.9

    Each recipient applies its own rules to the data. We may skip notifying you of a transfer if the law forbids notice or it could derail an investigation or weaken the Service’s protection.

  10. 5.10

    The servers of the Service and its suppliers stand in several countries, so data is processed in more than one jurisdiction.

6Retention

  1. 6.1

    Retention depends on the task: data lives as long as the Service needs it to operate, to account for payments, to settle disputes and complaints, to fight fraud and to obey the law.

  2. 6.2

    A deleted account leaves behind its payment history, records of violations and bans and complaint correspondence, kept for the same purposes.

  3. 6.3

    Backups and service logs are overwritten in cycles, and older data disappears with them.

7Security

  1. 7.1

    Reasonable technical and organizational measures protect the data.

  2. 7.2

    The internet, messengers and other people’s networks offer no complete protection in transit, and nobody can honestly promise it.

  3. 7.3

    The safety of your password, devices, wallets, list links and connection lines is in your hands.

8Your rights

  1. 8.1

    Through support you can request a list of the data held about you and ask to correct or delete it.

  2. 8.2

    We will refuse deletion when the data is required by law, for payment records, to settle a dispute or complaint, to counter fraud or to protect the Service’s rights.

  3. 8.3

    Before answering, we may check that the request came from the account owner.

9Cookies

  1. 9.1

    ProxySale sets the referral cookies from section 2, the support chat keeps the conversation ID in a cookie, and Yandex Metrica adds its own analytics cookies.

  2. 9.2

    You can block or clear cookies in your browser. The site keeps working, but the partner and the visit source will not be credited at sign-up, and the chat conversation will start over.

10Changes and contact

  1. 10.1

    The policy may be updated. A new version takes effect once posted on this page, and by continuing with the Service you agree to it.

  2. 10.2

    Send questions about your data to a ticket in the panel, the chat on the site, the @proxysalebizbot bot or support@proxysale.biz.