Our rules

Rules

OpSec Disclaimer

We take your privacy seriously and employ robust measures to protect your data. However, no system can fully shield against legally mandated disclosure to government authorities or law enforcement. While we have no intention of sharing user information voluntarily, we may be compelled to comply with valid legal orders.

Ultimately, safeguarding your identity and online activity remains your responsibility. We strongly advise using tools like anonymization and secure browsing practices to enhance your personal security.

Check out our Logs section below to see what we might know about you.

Community Guidelines

We strive to foster a safe, respectful, and lawful environment for all users. Avoid engaging in fraudulent activities, disruptive attacks (such as DDoS), or using our services for harmful, unethical, or illegal purposes. Harassment, abuse, or actions that endanger our infrastructure, users, or the broader community are strictly prohibited.

Users who operate responsibly and align with ethical practices are welcome to utilize our services. We prioritize supporting those who respect our mission and contribute positively to the community.

Individuals who violate these guidelines—including deliberate harm, exploitation, or security breaches—will face immediate account termination. We actively monitor for threats and enforce these standards without exception. By adhering to these principles, you help safeguard our community and infrastructure.

Support

Our support squad is just a ping away on Telegram. Check the top of Support page the address of Support team. Before you reach out, make sure your security settings are locked down tight - we've got your back, but we need you to have ours too

Frequently Asked Questions

Connection limits?

We don't impose connection limits. You're billed for every single byte transmitted and received through our system.

Configuration advices?

Setting a timeout of 20s or slightly longer in your software can significantly improve success rates. We achieve a 99% success rate with this setting. We typically respond immediately, but in any case, you can expect a response within 20s - no need to worry about delays.

DNS leaks?

We have partially implemented DNS leak protection on our proxies (not on 100% of them). Additionally, we recommend using a trusted DNS server to resolve hostnames and maintain the privacy of your online activities.

Any restrictions?

We've got our own backs, and yours too. That's why we've blocked some ports to prevent potential security holes: 22, 23, 25, 135, 137, 139, 389, 445, 465, 587, 2525, and 8291. If new threats emerge, we'll add more to the list - no questions asked.

Local addresses are strictly verboten. And government websites or banks? Forget about it. We're not about to let you walk into a potential security nightmare. Our infrastructure, our rules. We're not apologizing for keeping our house clean and our users secure.

If our proxies applicable to task "ANY_TASK_NAME"?

No guarantees here. Our proxies might work for your specific task, but we can't promise anything. Make sure you've configured your software correctly, and if you're unsure, hit up our support crew for help. We'll do our best to assist you.

Logs?

We're not hiding anything - our visibility into your online activities is limited to IP addresses and hostnames of outgoing connections. We don't retain this data for any significant amount of time, so you can rest easy.

Your traffic passes through our infrastructure unmodified and unmonitored. We don't care about the contents of your packets, and we don't analyze them either. When you sign up on our site, we collect your public User-Agent and IP address, but we don't bother validating them.

To be clear: we do collect some technical data, but it's not about identifying individual users or compromising their privacy. Our focus is on providing a service, not building profiles on our users.

Refunds?

Please check our Refund and Cancellation Policy

IP-based Authentication

Our platform does not support IP-based authentication. We enforce username and password authentication as our standard security protocol, and whitelisting functionality is unavailable.

To ensure compatibility, we require all client software to adhere to current authentication standards. Systems relying on deprecated methods such as IP-based authentication will need to modernize their integration approach to align with our security framework.