Acceptable use
You can use EclipseProxy for a wide range of legitimate use cases. Some things we don’t allow.Allowed
- Web scraping of public data
- Account management at scale (within target platform terms)
- Ad verification and brand monitoring
- SEO research and rank tracking
- Price monitoring and competitive intelligence
- Multi-account workflows on platforms that permit them
- App testing from different geographies
- Privacy / anonymization of your own browsing
- Research and journalism
Restricted
- Banking / financial services targets: many blocked at our gateway
- Government / official services: blocked
- Anything illegal in your jurisdiction or the destination’s
Not allowed
- Spam / bulk unsolicited email from our network
- DDoS or any traffic-based attack
- Malware distribution, phishing, fraud
- CSAM or any content involving minors
- Direct attacks on infrastructure (port scanning, vulnerability exploitation against third parties)
Grey areas, case-by-case
- Ticket scalping: depends on jurisdiction and platform terms
- Sneaker reselling: depends on retailer terms
- Gift card workflows: depends on platform (some are abuse, some are legitimate gifting at scale)
- Account creation at scale on platforms that don’t allow it: generally not, exceptions for specific researcher / security use cases
Specific examples
- “Can I use this for ticket scalping?”: depends on jurisdiction. Most platforms (Ticketmaster, etc.) forbid it. We don’t proactively block ticketing sites but if a target requests blocks at scale, we may comply.
- “Apple / Xbox gift card code generation?”: no, that’s fraud against the platform.
- “Web scraping, SEO, ad verification?”: yes, core use cases.
What happens if you violate
- Warning for borderline cases
- Account suspension for clear violations
- Termination + refund denied for malicious behavior
- Law enforcement cooperation for illegal activity
Restricted destinations
We block traffic to specific destinations at our gateway for legal, abuse-prevention, and reputational reasons.Categories typically restricted
- Banking and financial institutions
- Government / official services
- Known phishing / malware infrastructure
- Specific endpoints on third-party sites that are abuse-prone (e.g., authentication endpoints commonly used for credential stuffing)
- Sites that have asked us to block their traffic at scale