1. Acceptance of Terms
By using Good Proxies you agree to these Terms of Service. If you do not agree with any provisions — please do not use the service.
Last updated: October 25, 2025.
This document defines access rules for Good Proxies, key restrictions, refund conditions, allowed usage scenarios and administration rights.
By using Good Proxies you agree to these Terms of Service. If you do not agree with any provisions — please do not use the service.
Good Proxies provides access to public proxy servers via website and API. We do not guarantee uninterrupted proxy operation or availability.
To use the service you must purchase an access key. You are responsible for the confidentiality of your key. Sharing keys is prohibited.
You may NOT use the service for:
All prices are in USD. Payment is made in advance. We accept bank cards, USDT, BTC and other cryptocurrencies.
Refunds are issued only if service downtime exceeds half of the key validity period, but not less than 24 hours. Refunds are calculated minus used days. After refund the key is blocked.
Each plan has daily request and IP-subnet limits. When exceeded, API access is restricted until the next day.
A key must be activated within 10 months after purchase. The validity period starts immediately on activation and cannot be paused. Expired keys are non-refundable.
Strictly prohibited:
We may suspend or terminate access for violations of these Terms without refund. If a key is suspected of being used by multiple users, it is blocked pending investigation.
The service is provided "as is". We do not guarantee proxy functionality, speed, anonymity or availability and are not responsible for blocks on third-party sites.
Good Proxies is not liable for any direct or indirect damages arising from use or inability to use the service.
We may change these Terms at any time. Continued use after changes means acceptance of the new terms.
For all enquiries email [email protected].
The administration may:
A browser with JavaScript and Cookies enabled is required. Extensions limiting site behaviour must be disabled.
If a single IP sends too many requests, it may be blocked to protect the infrastructure.
We use GeoLite2 (MaxMind) and IP2Location LITE databases. Some IPs may have outdated geolocation; the administration is not responsible for this.