Proxeta · Legal

Privacy Policy

This Privacy Policy explains how the Proxeta website and Service process personal data. It is written from the actual behaviour of the product: every category below exists in the Service today, and nothing is listed that the product does not do.

Effective date:
26 September 2026
Last updated:
31 October 2026
Version:
1.0

This is the website and Service policy.

The Proxeta Proxy Manager Chrome extension has a separate policy because it works differently: it has no account, no balance and no integration with Proxeta servers. Proxeta Proxy Manager Privacy Policy.

1. Who is responsible

Proxeta is the product name under which the Service is operated. This policy applies to the Proxeta website and Service: it describes what is processed, for which purposes, for how long, and how you can exercise your rights.

Privacy questions and requests are handled through the support channels listed at the end of this policy.

2. What we process

Personal data categories

DataSourcePurpose
Email address, account identifier, account stateYou, when you register with a one-time email codeCreating and operating your account, sending the one-time code, support, security
One-time access code and its delivery stateGenerated by the Service, sent to your email addressAuthenticating a sign-in or registration request
Telegram identifier and public Telegram usernameTelegram, when you choose sign-in with TelegramCreating or matching your account, authentication, support
Session token, user identifier and email as browser cookiesCreated by the Service after successful authenticationKeeping you signed in on the website
Payment records: provider payment and order identifiers, amount, currency, product, status, timestampsYou and the payment providerProcessing your order, crediting your balance, accounting, dispute handling
Traffic usage records: gigabytes credited and consumed, product and timestampsGenerated by the Service as you use the proxiesProviding the paid traffic product, usage display, abuse prevention
ISP order records: country, connection format, quantity, duration, provider order and account identifiers, order status, expiryYou and the proxy providerProvisioning, renewing and supporting your static IP order
Proxy connection data for ISP orders: assigned IP address, port, login and passwordThe proxy providerDelivering the proxy product to you and showing your credentials
Referral link data and referral relationshipThe referral link you follow and the account that invited youCalculating referral rewards you have agreed to participate in
Support conversations and abuse reportsYou, through the website or the Telegram botAnswering your request, resolving disputes, preventing abuse
Technical logs: IP address, request path, timestamp, HTTP status, user agent stringGenerated by the web server and applicationOperating and protecting the Service, diagnosing faults, rate limiting
Website usage statistics, for each visit: page address (without query parameters other than campaign tags), page title, referring page (scheme, host and path only), browser, operating system, device type, screen size, language, approximate country, region and city, clicks on marked buttons, and a pseudonymous visitor identifier that Umami derives from your IP address, browser details and a value it changes every month. The IP address is used for this and for the approximate location and is not storedSent by our own script on proxeta.io to Umami Cloud, our website statistics provider; nothing is stored in your browser or read from its storageUnderstanding which pages and articles are useful and improving the website
Referral attribution code in browser storage (optional)You, only after you accept referral storageAttributing a new account to the account that referred it

3. What we do not do

  • We do not run advertising, tracking pixels or marketing cookies; there are none in the product.
  • Our only analytics is the website statistics described in section 9. They use no cookies or other browser storage, are not combined with data from other websites and are not used for advertising.
  • We do not use third-party error-tracking or product-analytics SDKs; the statistics script is our own.
  • We do not fingerprint devices or browsers to recognise or track you. The only exception is the visitor identifier the statistics provider derives to count visitors, which changes every month (section 9).
  • We do not build location profiles of visitors, and we do not perform geolocation lookups for access decisions. The website statistics record an approximate location (country, region and city) for each visit and use it only for statistics.
  • We do not collect the content of the websites you visit through a proxy.
  • We do not collect your payment card details or wallet private keys; crypto payments are handled by the payment provider.

4. Why we are allowed to process it

Where a legal basis is required, we rely on: performance of our contract with you (account operation, proxy delivery, payments, renewals, support); our legitimate interests in keeping the Service secure, preventing abuse and defending legal claims, and in understanding, through cookieless website statistics, how the website is used; your consent for optional referral attribution storage; and compliance with legal obligations that apply to us (for example accounting or lawful requests). Where consent is the basis, you can withdraw it at any time without affecting lawfulness of processing before withdrawal.

5. Account and authentication

Sign-in is passwordless. If you sign in with email, the Service generates a six-digit one-time code, stores it in an in-memory data store with a five-minute lifetime, sends it to your address using our email provider and deletes it after successful verification. If you sign in with Telegram, Telegram tells the Service your Telegram identifier and public username; the Service never receives your Telegram password.

After successful authentication the website stores a session token, a user identifier and the email address in first-party browser cookies. Those cookies are readable by the website JavaScript and are therefore not HttpOnly. See the Cookie Policy for names and durations.

6. Payments

Orders are paid through third-party cryptocurrency payment providers. Proxeta receives the payment result and the provider identifiers needed to reconcile an order; it does not receive your private keys and does not store wallet credentials. The provider processes your payment in accordance with its own terms and privacy notice.

7. ISP orders and proxy operation

When you order a static ISP proxy, the Service creates a technical provider identity derived from your Proxeta account identifier and asks the proxy provider to provision the address. Depending on the account type, the derived provider identity may be based on the account email or on the Telegram ID; the provider also receives the technical billing or account identifier required to provision the service. The derived identity is used for provisioning, renewal, replacement and reconciliation of your orders.

Proxy credentials returned by the provider are stored encrypted at rest in the Service database and are displayed to you in your account. Server-side logs record technical events of provisioning, renewal, swap and reconciliation so that a paid order cannot be duplicated, lost or double-charged.

8. Referral attribution

Referral attribution uses an optional browser-storage item. It is written only after you accept the referral category in the cookie settings, it lasts 30 days, and it is deleted immediately if you refuse or withdraw that consent. The referral relationship between two accounts is stored on our side because it determines rewards, and it is visible only internally and to the accounts concerned.

9. Service providers

We use a small number of service providers: a cryptocurrency payment provider, proxy network providers, an email delivery provider, Telegram for optional sign-in, our own hosting and database infrastructure, and the third-party IP-check endpoints used by the browser extension (which never receive data from your Proxeta account). Providers process data only for the purposes described here and subject to their own obligations. Where a transfer of personal data to another country occurs, it takes place under the terms offered by the relevant provider.

For website statistics we use Umami Cloud, whose servers are in the United States and the European Union. The statistics are sent by a short script of our own; no Umami code runs on the website. The script runs only on proxeta.io, sets no cookies, and neither stores anything in your browser nor reads anything stored there. When a page opens it sends the page address, page title, referring page, screen size and browser language, and when you click a marked button it sends the button's name. Before anything is sent, it removes every query parameter from the page address except the five campaign tags (utm_source, utm_medium, utm_campaign, utm_term, utm_content), removes the part after "#", keeps only the scheme, host and path of the referring page, and does not send the Telegram sign-in callback page at all. Umami uses your IP address and browser details to derive the approximate location and a pseudonymous visitor identifier that changes every month, and does not store the IP address. Umami keeps a record of each visit (approximate location down to the city, browser, device, and the pages and marked clicks of the visit) for up to six months. The statistics are not linked to your Proxeta account. If your browser sends a Do Not Track or Global Privacy Control signal, nothing is sent.

10. How long we keep data

Retention

DataRetention
One-time sign-in codeFive minutes, then deleted or expired automatically
Session cookies (user identifier, email, session token)Until you sign out or clear them; the session token itself is valid for seven days
Account record (email, Telegram identity, referral relationship, settings)While the account is active; deleted or anonymised after account deletion, except where retention is required by law
Payment, traffic and ISP order recordsWhile the account is active and afterwards for as long as needed for accounting, dispute handling, fraud prevention and legal obligations
ISP proxy credentialsWhile the order exists; removed or invalidated when the order is released
Support conversationsWhile needed to handle the request and for a reasonable period afterwards for dispute handling
Technical access logsA short period consistent with operating and securing the Service
Website usage statistics (Umami Cloud)Up to six months, then deleted by the statistics provider
Referral attribution in browser storage30 days, or immediately after you withdraw referral consent
Cookie consent decisionUntil you change it or clear browser storage

11. Security

Access to production systems is restricted, proxy credentials are encrypted at rest, payment provider callbacks are verified, and authentication endpoints are rate-limited. No service can promise absolute security. Session cookies for the website are readable by the website JavaScript because the current authentication architecture relies on them, so they are not HttpOnly cookies.

12. Your rights

Depending on the law that applies to you, you may have rights of access, correction, deletion, restriction, objection, portability, withdrawal of consent and complaint to a supervisory authority. The Data Rights page explains how to make a request and how we handle it.

13. Children

The Service is intended for persons who are at least 18 years old. It is not directed to children, we do not knowingly create accounts for children, and we do not market the Service to children.

14. Notice at collection

Where a jurisdiction requires a notice at or before collection, this section is that notice: we collect the email address and, optionally, the Telegram identity to create your account; payment and order records to deliver what you paid for; technical logs to operate and protect the Service; and cookieless website statistics to understand how the website is used. We do not sell personal data and we do not share it for cross-context behavioural advertising. Categories, purposes and retention periods are listed above.

15. Territorial availability

Proxeta does not intentionally market or offer its paid Service to persons located in the European Economic Area or the United Kingdom. Consistently with that position, the Service does not build visitor location profiles and does not perform GeoIP eligibility profiling: your IP address is not used to decide whether you may access the Service. The approximate location recorded by the website statistics (section 9) is used only for statistics.

This statement does not remove rights you may have under mandatory law.

16. Changes

This policy is versioned; the effective date, last-updated date and version are shown at the top of this page. Every revision is dated in "Last updated" and applies from the day it is published. A change that requires you to accept or acknowledge the legal documents again is published under a new version and legal bundle, and you will be asked to confirm it.

17. Contact

Privacy questions and requests: Proxeta support center or the Proxeta Telegram bot.

This document is part of the Proxeta legal bundle version 2026-09-26.1. The English text is the canonical version.

The Chrome extension Proxeta Proxy Manager has its own, separate policy: Proxeta Proxy Manager Privacy Policy.