IO.NET
GDPR Compliance
Data Handling
IO.NET's privacy policy says data covered by the policy is stored in the United States, and its network/inference documentation describes a decentralized, geo-distributed/global GPU network with workers in multiple countries rather than an EU-only region option. No primary-source commitment to EU-only processing was found.
The privacy policy states that the service may retain information it collects about users for as long as they maintain an account, and that blockchain-stored data may not be deletable.
For Confidential Chat, IO.NET states messages are never saved, conversation content is never written to logs, and messages exist only in the browser and TEE during processing. This appears to be feature-specific and not a general API-wide statement about model training or all inference data.
Certifications & EU AI Act
Verification
- https://io.net/privacy ↗
- https://io.net/terms ↗
- https://io.net/docs/guides/intelligence/api-keys-and-secrets ↗
- https://io.net/docs/guides/payment/io-intelligence-payments ↗
- https://io.net/docs/guides/confidential-inference/confidential-chat ↗
- https://io.net/docs/guides/confidential-inference/overview ↗
- https://io.net/docs/guides/clouds/confidential-compute-overview ↗
- https://io.net/docs/guides/explorer/network-map-page ↗
- https://blog.io.net/article/io-net-achieves-soc-2-compliance-to-reinforce-its-enterprise-ready-infrastructure ↗
IO.NET publishes a privacy policy and terms, and it publicly states SOC 2 compliance, but no public DPA/AVV, SCC commitment, sub-processor list, or explicit API-data training statement was found in primary sources reviewed. Its own materials indicate data is stored in the US and that compute/inference can run on a decentralized global GPU network, so EU-only processing could not be confirmed.