Privacy and Data Handling at WeProx
Last updated: September 25, 2026. Engineers tend to want the schema, not the marketing, so this policy is organized as an inventory: each category of data WeProx processes, where it comes from, why it exists and how long it persists. If a field is not listed here, we do not collect it. Questions about any line item can be sent to support@weprox.net and will be answered by someone who can see how the system actually works.
Data inventory
The table summarizes each category. Detail on the less obvious rows follows below it.
| Category | Fields | Purpose |
|---|---|---|
| Account | email, optional name, hashed password, sign-in records | authentication, account security |
| Card and PayPal billing | payment outcome and amount; card data stays with Stripe or PayPal | billing, accounting |
| Crypto billing | public transaction hash and address | matching a top-up to your balance |
| Zelle and wire billing | sender name and payment reference | matching a transfer to your account |
| Proxy metadata | connection times, data volume, connecting addresses | operation, billing, security, abuse response |
| Telegram support | conversation with @weprox_bot, if used | support history |
Authentication
Passwords are stored only as hashes, so the plain-text value is never retained. Sign-in records let us detect unusual access to an account. A reCAPTCHA check runs at registration to filter automated sign-ups, and the dashboard maintains a sign-in session so you remain authenticated while working. The name field is optional and can be left empty.
Payment processing
Card payments are handled by Stripe checkout and PayPal payments by PayPal. The processor holds the card or account details; WeProx never receives or stores a full card number. Crypto payments in Bitcoin, USDT or Ethereum are reconciled using the public transaction hash and address, which are already visible on the respective chain. Zelle and bank wire payments are reconciled by sender name and reference. Standard billing records, such as amounts, timestamps and the plan purchased, are also kept.
Proxy traffic: content versus metadata
The distinction matters, so it is stated precisely. Content means the payloads you send and receive: URLs requested, pages returned, form data, API responses. WeProx does not inspect or record content.
Metadata means facts about connections rather than their payload, for example when a connection opened, how many bytes a line transferred and which client addresses connected to your line. Metadata may be processed to operate the network, calculate billing, protect the service against misuse and respond to abuse reports concerning an address on your line.
Website and tools
The public website sets no tracking cookies and loads no third-party analytics. The free IP checker and proxy checker resolve results by querying public IP-lookup services; the check is not stored.
Disclosure
WeProx does not sell personal data. Data is shared only where required to deliver the service, for example with the payment processors named above, or where the law obliges us to respond to a valid request.
Retention
Account data is retained while the account remains open. Billing records are retained for the period that tax and accounting law requires, which may extend beyond account closure.
Your rights and how to exercise them
You may request access to, correction of, deletion of, or an export of your personal data. Send the request to support@weprox.net from the email registered on the account so we can confirm ownership. Records that must be retained by law are excluded from deletion, and we will identify them in our reply.
The service is restricted to users aged 18 and over; users under 18 are not permitted and we do not knowingly process their data. Amendments to this policy are published on this page with a new date.