Security, privacy, and acceptable use

The intended design does not inspect workload content by default; actual isolation and operator access still need production verification. Limited host, network, account, billing, and security information may be processed when needed to operate the service, investigate authorized support, respond to an active threat, or meet a valid legal obligation.
Link to this answer ↗

The intended records include account and session data, public SSH keys, API-key hashes, ledger and transaction records, instance configuration, support messages, and limited security telemetry. Exact retention periods and subprocessors must be stated in the production Privacy Policy.
Link to this answer ↗

Customers are responsible for protecting passwords, recovery codes, SSH private keys and API secrets; applying software updates; limiting exposed services; and securing their own data and backups. Dedicated hardware does not make an unsafe workload secure.
Link to this answer ↗

The service must not be used for malware, phishing, credential theft, botnets, unsolicited messaging, denial-of-service attacks, unauthorized access, exploitation of minors, interference with other tenants, or unlawful conduct. Security testing requires authorization from the target.
Link to this answer ↗

No. It means identity documents are not requested at signup. AnchorGPU may still enforce its Acceptable Use Policy, protect customers and infrastructure, investigate credible reports, and respond to valid legal process.
Link to this answer ↗