PRIVACY

Your data,
explained plainly.

Updated 18 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 first check the queried IP against network datasets stored on our server. If the local data does not identify a VPN, hosting, Tor or public-proxy network, or the local data is unavailable, we send the queried IP to our existing isproxyip detection integration through its configured gateway. This request does not include your account email, ProxyRadar API key or billing data. Public source lists are downloaded separately during scheduled updates.

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.

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.