PRIVACY
Your data,
explained plainly.
Updated 19 October 2026
ProxyRadar is operated by Neo Software Services LTD, 71–75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom.
Account and service data
We store account information such as your email address, password hash, API key and plan. Service records include queried IP addresses, classification results, usage counts and request information needed to operate the API. Support messages are stored with your account email.
IP detection and external checks
We process the IP address you submit to provide a network classification. When needed, the queried IP is shared with an external IP intelligence provider for an additional check. That request does not include your account email, ProxyRadar API key or billing data. We also use network datasets to provide category information.
Payments and optional Google sign-in
Stripe processes payments and subscription management. We store subscription references and status; payment card entry takes place on Stripe’s pages. If you choose Google sign-in, Google supplies identity information needed to link or create your account.
Account emails
Resend delivers transactional account emails, including password reset messages. We share the recipient email address and message content with Resend for delivery. IP lookup requests are not included in these emails. We do not enable email open or click tracking for account messages.
Public checker
The public browser checker does not require an account. We use a keyed hashes of the requesting IP, network prefix and session, attempt counts and timestamps to enforce daily fair-use limits; the demo allowance file is reset on the next day’s use. The checker does not add its results to a customer’s account history. Normal server access records and short-lived session data may still be processed for service operation and request security.
Website traffic measurement
We measure visits to our public pages using first-party server-side statistics. A daily keyed hash of the requesting IP and browser type estimates daily visitors; analytics records do not store the raw IP, full browser identifier or full referring URL. We record the referring host, supported campaign labels, page paths and approximate device type. Analytics does not set a tracking cookie. Known bots, prefetch requests and requests carrying Do Not Track or Global Privacy Control are excluded. Daily visitor hashes are removed after 35 days; page totals can be retained longer. When an account is created, we may associate the first source observed that day with that account to measure registrations and sales. We do not send these statistics to an external analytics service. Avoid putting personal data in campaign labels.
Optional advertising measurement
If you allow measurement through Cookie preferences, Google Ads uses measurement cookies and receives the page visited, ad-click identifiers, basic browser/network information, and confirmed registration or first paid subscription events. Payment events include amount, currency and a random-looking transaction reference for deduplication. We do not send account email, name, password, API key, card details, support messages or queried IP addresses in these events. We do not enable enhanced conversions or personalized-ad signals. Without permission, Google measurement tags are not loaded. Do Not Track and Global Privacy Control override permission. You can withdraw consent using Cookie preferences; your selection is remembered on this browser for up to six months. Account features work without optional measurement. Google explains its processing in its partner-sites privacy notice.
Cookies
We use session and request-security cookies for sign-in, forms and account features. These cookies are necessary for the account interface to work.
Retention and access
Account, usage and support records are retained for service operation, security and account administration. Backups may retain historical copies. Contact support to request account access, correction or deletion and to discuss any records that must be retained.
Keep your credentials private
Do not place API keys in public code or share them in support messages. Prefer the Authorization header for API calls. You can replace your key from the dashboard; doing so invalidates the old key immediately.