ProxyElite Privacy Policy
How we collect, use, and protect your personal data. Proxies operate at the Elite level — the HTTP_X_FORWARDED_FOR header is not forwarded, traffic content is not logged. Own data center since 2012, strict access control, TLS encryption.
Infrastructure in numbers
Data protection relies on our own infrastructure. All servers and channels have been owned by ProxyElite since 2012 — we control every node and do not rely on third parties.
Document contents
4 sections — pick the one you need for a quick jump
Definition of
personal information
What we consider personal data: direct and indirect identification
Data collection
and use
What data we collect, how we use it, and when we share it with third parties
Data protection
and retention
TLS encryption, Elite anonymity, retention periods, and deletion
Changes to
the policy
How and when we update the privacy policy
Definition of personal information
Direct identification
Name, email, phone — data that directly points to you
Indirect identification
IP address, account ID, cookies — data that can be linked to you
Anonymous data
Usage statistics, aggregated data — cannot identify you
Data collection and use
Data protection and retention
HTTP_X_FORWARDED_FOR header is not forwarded, and the client's real IP is completely hidden from the target website. We do not log traffic content — only connection metadata (time, IP, volume) for billing and abuse prevention.
TLS encryption
All transmitted data is protected by modern encryption algorithms
Access control
Strict access control to employee personal data. NDA for B2B
Retention periods
Metadata — 30 days. Account data — until deletion or 5 years by law
Changes to the policy
Who cares about the privacy policy
Different clients interact with our data in different ways. Below are typical scenarios and relevant policy sections.
Individual clients
Section 1: what data we consider personal. Section 2: how we use email and IP for the whitelist.
Parsing and data scraping
Section 3: we do not log traffic content. Metadata — 30 days, then deleted.
B2B clients
Section 3: NDA is available for signing. Contracts and closing documents for accounting.
Banking and fintech
Section 2: sharing data with third parties — only as required by law. Section 3: TLS encryption.
SMM and multi-accounting
Section 1: IP address — indirect identification. Section 3: Elite anonymity without X-Forwarded-For.
Legal matters
Section 2: disclosure by law. Section 3: 5-year retention for accounting. Section 4: changes.
Account security
Section 3: access control, encryption. Whitelist — 5 IPs free, two-factor authentication.
Data deletion
Create a ticket — we will delete your personal information, except for data required by law (5 years).
How ProxyElite protects your data
The technical mechanics without simplifications. Four layers of protection: from encryption to access control.
Elite anonymity
Proxies do not forward the HTTP_X_FORWARDED_FOR header. The target website cannot see your real IP and cannot detect that a proxy is being used.
The level is Elite, not Anonymous. This is a technical architecture, not a marketing promise.
No content logging
We do not store: HTTP request content, URLs, cookies, headers. Only metadata: time, client IP, traffic volume.
Metadata — 30 days for billing, then automatically deleted.
Encryption and access
All data in transit — via TLS. Server access — only for in-house engineers, no outsourcing. RBAC-based control.
For B2B — NDA signing. Own data center, not rented.
Deletion on request
Create a ticket — we will delete your personal information. Metadata is automatically deleted after 30 days.
Data required by law (accounting, 5 years) — we store the minimum necessary amount.
Privacy: ProxyElite vs free vs competitors
A quick comparison: how different types of proxy providers handle your data.
| Parameter | ProxyElite | Free proxies | Resellers |
|---|---|---|---|
| Content logging | No | Yes (owner can) | Depends |
| Anonymity level | Elite (100%) | Often Transparent | Depends |
| X-Forwarded-For header | Not forwarded | Often forwarded | Depends |
| Own infrastructure | Yes (since 2012) | No | Rented |
| NDA for B2B | Available | No | Rare |
| Deletion on request | Yes (ticket) | No | Depends |
Scheme: from purchase to data protection
Four steps. At every stage, your data is protected by the privacy policy.
Registration
Email for the account. Payment data — via the gateway, we do not store card numbers.
IP binding
Your IP is added to the whitelist. It is used only to authorize proxies — not logged.
Using proxies
Traffic through Elite proxies. Content is not logged. Metadata — 30 days, then deleted.
Data deletion
On request — we will delete your personal information. Metadata is deleted automatically.
Connect in 5 minutes
Ready-to-use code examples for the most common scenarios. Connection details (IP:port@login:password) are available in your personal account.
# Check IP via ProxyElite HTTP proxy
curl -x "http://USER:PASS@PROXY_IP:PORT" \
-L "https://api.ipify.org?format=json"
# Login/password can be passed as a separate flag
curl --proxy "http://PROXY_IP:PORT" \
--proxy-user "USER:PASS" \
"https://httpbin.org/ip"# SOCKS5 with DNS resolution on the proxy side (socks5h)
curl -x "socks5h://USER:PASS@PROXY_IP:PORT" \
-L "https://api.ipify.org?format=json"
# SOCKS5 without local resolution — socks5
curl --socks5 "PROXY_IP:PORT" \
--proxy-user "USER:PASS" \
"https://httpbin.org/ip"import requests
proxies = {
"http": "http://USER:PASS@PROXY_IP:PORT",
"https": "http://USER:PASS@PROXY_IP:PORT",
# for SOCKS5 you need pip install requests[socks]
"socks5": "socks5h://USER:PASS@PROXY_IP:PORT",
}
r = requests.get("https://api.ipify.org?format=json", proxies=proxies, timeout=10)
print(r.json()) # {'ip': 'PROXY_IP'}import { request, ProxyAgent } from 'undici';
const agent = new ProxyAgent('http://USER:PASS@PROXY_IP:PORT');
const { statusCode, body } = await request('https://api.ipify.org?format=json', {
dispatcher: agent,
headersTimeout: 10_000,
});
for await (const chunk of body) {
console.log(chunk.toString()); // {"ip":"PROXY_IP"}
}<?php
$ch = curl_init('https://api.ipify.org?format=json');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_PROXY, 'PROXY_IP:PORT');
curl_setopt($ch, CURLOPT_PROXYUSERPWD, 'USER:PASS');
curl_setopt($ch, CURLOPT_TIMEOUT, 10);
// For SOCKS5, uncomment:
// curl_setopt($ch, CURLOPT_PROXYTYPE, CURLPROXY_SOCKS5);
$response = curl_exec($ch);
echo $response; // {"ip":"PROXY_IP"}
curl_close($ch);IP:port@login:password or IP:port with whitelist authorization.
Works with your software
All IPv4 proxy plans are compatible with 500+ tools. Your data is protected regardless of the software.
IP:Port
192.0.2.1:8080
IP:Port:Login:Password
192.0.2.1:8080:user:pass
Format builder
any template
Privacy for business
For B2B clients — NDA, contracts, and a dedicated manager. Data is protected at the legal level.
Contract and NDA
We sign an official contract. NDA is available for signing. Invoices, acts, and closing documents.
Flexible payment terms
Deferred payment. Bank transfer, cryptocurrencies (BTC, ETH, USDT), and bank cards.
Dedicated manager
Personal account manager with direct contact via Telegram/Slack. Has signed an NDA.
Corporate orders from $1000
Custom pricing from 5000 IPs. Dedicated /24 subnets, 99.9% SLA with compensation.
It is forbidden to use proxies for
The privacy policy does not protect against blocking when the rules are violated.
The full list is in the terms of service.
Frequently asked questions about privacy
What data we collect, how we protect it, how to delete it.
ProxyElite collects: email upon registration, IP address for proxy binding (whitelist), payment data via payment gateways (we do not store card numbers), connection metadata (time, traffic volume) for billing. We do not log traffic content — only metadata. NDA signing is available for B2B clients.
No. We do not log traffic content — only connection metadata: connection time, client IP address, volume of data transferred. This is required for billing and abuse prevention. The content of HTTP requests, cookies, target website URLs — is not stored.
Only in two cases: when required by law (request from authorities or court case) and when necessary to prevent harm to you or others. We inform you about such requests unless prohibited by law. Payment data is processed through certified payment gateways.
Connection metadata — 30 days for abuse prevention, then deleted. Account data (email, payment history) — until account deletion or 5 years according to accounting requirements. After the retention period expires, data is destroyed.
We apply physical, administrative, and technical security measures: data encryption in transit (TLS), strict employee access control, own infrastructure in a Tier-III data center with N+1 redundancy. Proxies operate at the Elite level — the HTTP_X_FORWARDED_FOR header is not forwarded.
Yes. Create a support ticket requesting data deletion. We will delete your personal information, except for what the law requires us to keep (accounting documents — 5 years). Connection metadata is automatically deleted after 30 days.
Yes, for proper operation of the website and personal account. Cookies are used for authentication, saving language preferences, and theme settings. We do not share cookie data with third parties. You can disable cookies in your browser settings, but website functionality will be limited.
Still have questions about privacy?
Contact support — engineers will reply within 30 minutes. Or read the terms of service for a complete understanding of the conditions.
Contact supportElite anonymity · No content logging · NDA for B2B