Your disk is encrypted at rest, and when you leave, your data is destroyed by destroying the key. No marketing asterisks. Here is how it works.

Encrypted at rest:

• Your VM's storage is encrypted with ZFS native encryption using AES-256-GCM — the same cipher the US government uses for classified data.
• Encryption happens on our storage, below your operating system. There is nothing to configure and nothing to turn on.
• A drive pulled from a rack is unreadable. Keys are network-bound and never live on the drive itself.

What encryption at rest does and does not do:

• It protects data on disks that are powered off, decommissioned, or physically removed.
• It does not encrypt your data from us while your VM is running — a running VM's memory and live disk are necessarily accessible to the host. If you want a secret only you can ever read, encrypt it yourself inside your VM (LUKS, gocryptfs, age, GPG, your application's own encryption).
• You hold root. What you layer on top of our encryption is yours to control.
• Your backups can go further: register zero-knowledge recovery keys and each backup's encryption key is sealed to keys only you hold — not even we can recover that data. See Zero-knowledge backups: your recovery keys.

When your service ends:

• Your data is cryptographically erased — we destroy the encryption keys, which is designed to make the underlying ciphertext unrecoverable. The binding timeline is in our Terms: account data is erased within 30 days of termination, except for the billing and tax records US law requires us to keep.
• This applies whether you cancel, let a service lapse, or we terminate for an abuse violation.

Back up anything you cannot afford to lose before a service ends. Erasure is final and there is no undo. See our Terms of Service (sections 6.3 Retention and 8 Account Termination) for the binding language on retention windows and deletion.