Acceptable use policy

What is allowed

Lawful B2B workloads: e-commerce price monitoring, SEO research, advertising verification, AI training data collection from the public web, threat intelligence research, brand-protection scanning, travel-fare aggregation, and similar use cases. iOS / macOS build CI on customer-owned source code. Docker workloads, GPU inference, and fine-tuning on customer-owned data and models.

What is forbidden

• Anything involving CSAM, in any form. Hashes are filtered at the gateway and on the provider daemon.
• Phishing, credential-harvesting, or social-engineering payloads.
• Fraud, including account takeover, payment fraud, or coupon abuse.
• Targeted attacks against individuals (doxxing, stalkerware).
• DDoS or other availability attacks.
• Bypassing CAPTCHA or similar challenges in ways that violate the target site’s ToS for malicious purposes.
• Traffic to or from sanctioned countries or entities.
• Cryptocurrency mining via Docker or GPU workloads — economically unsound at our price points and disruptive to the provider experience.
• Anything inconsistent with the categories a provider has opted into.

How we enforce it

Pre-flight filtering at the gateway and on the provider daemon blocks the most common abuse vectors before bytes are relayed. Behavioral anomaly detection flags accounts whose pattern (request rate, destination diversity, error ratios) drifts from their declared category. Confirmed abuse triggers account suspension, refund forfeiture, and where appropriate cooperation with law enforcement.

Provider protections

If a customer’s use case causes legal exposure to a provider whose IP routed the traffic, iogrid’s legal defense fund covers reasonable provider costs. Providers can revoke consent for any category at any time without notice; we route subsequent requests elsewhere.