Before transit
With encryption enabled, AES-256-GCM protects chunk confidentiality and integrity. Password-based keys use a memory-hard derivation function and are not sent to the server. Unencrypted mode is an explicit customer choice.
Security model
AgooCloud recommends client-side encryption. The agent derives a key from the password, encrypts each changed chunk and sends only encrypted bytes through the managed API.
With encryption enabled, AES-256-GCM protects chunk confidentiality and integrity. Password-based keys use a memory-hard derivation function and are not sent to the server. Unencrypted mode is an explicit customer choice.
Production traffic is expected over TLS. Authenticated endpoints apply ownership checks to devices, backup sets, sessions, manifests and restore chunks.
Object-storage credentials remain server-side. Encrypted backups retain encrypted payloads under per-customer object keys. Operational metadata, including filenames and paths, is stored separately and is not hidden by payload encryption.
If you lose a client-side encryption password, AgooCloud cannot recover it. Keep a protected password record and regularly test restores. File backups do not guarantee NTFS permissions, ownership, alternate data streams or live-database consistency.
Please send a responsible disclosure to contact@rvlworks.com. Do not access or alter data that is not yours.