# What is encrypted cloud storage, and who holds the key?

> Encrypted cloud storage where you hold the key: restic, rclone crypt, Kopia or Cryptomator on an S3-compatible bucket, $2.23/TB-month on 12 months.

- URL: https://privates3.com/encrypted-cloud-storage/
- Last updated: 2026-11-17
- Publisher: PrivateS3 (https://privates3.com)

**Quick answer — What is encrypted cloud storage, and who holds the key?**

Encrypted cloud storage keeps files unreadable to anyone without the key. What matters is who holds it: the seller, or only you. **PrivateS3** encrypts disks at rest, but its real answer is client-side: restic, rclone crypt, Kopia or Cryptomator encrypt on your machine, and the bucket costs $2.23/TB-month on 12 months.

**In brief**

- **At rest on the server**: Disks encrypted at rest with AES-256 on the server; for privacy from the operator, files are meant to be encrypted on the customer's side (restic, rclone crypt, Kopia, Cryptomator) before upload.
- **What PrivateS3 can see**: Without client-side encryption, the operator can technically read stored files, file names and sizes; with it, the operator sees only encrypted blobs, their sizes and upload times.
- **Your key, your risk**: every tool here warns that a lost password means lost data.
- **Metadata**: most tools leave file sizes visible; rclone crypt also leaves modification times.

## Which tool encrypts files before they reach the bucket?

*Client-side encryption tools that work with an S3-compatible bucket: cipher, what they hide and what stays visible, per their documentation read on 17 November 2026*

| Tool | Cipher (per its docs) | Hides names | Still visible to the operator | Best for |
| --- | --- | --- | --- | --- |
| restic | AES-256 in counter mode, Poly1305-AES | Yes | Pack file sizes, upload times | Server and laptop backups |
| rclone crypt | NaCl SecretBox (XSalsa20, Poly1305), key from scrypt | Yes, by default | File length, modification time | Syncing folders |
| Kopia | Data encrypted with the repository password | Not stated on the page read | Blob sizes, upload times | Backups with a GUI |
| Cryptomator | Vault keys wrapped with a scrypt-derived key | Not stated on the page read | Encrypted file sizes | Desktop vaults for Cyberduck or a sync folder |
| Nextcloud encryption module | Server-side module of Nextcloud | No | File names in the bucket | A Nextcloud mount |

## What is the difference between server-side and client-side encryption?

**Who holds the key.** With server-side encryption, the seller encrypts disks and keeps the key, so a thief who takes a disk learns nothing, but the seller can still read files. With client-side encryption, files are scrambled before they leave your machine and the seller never gets the key.

PrivateS3 does both and says which protects what. Disks encrypted at rest with AES-256 on the server; for privacy from the operator, files are meant to be encrypted on the customer's side (restic, rclone crypt, Kopia, Cryptomator) before upload. For privacy from PrivateS3 itself, only the second kind counts. The [no-KYC page](https://privates3.com/no-kyc-cloud-storage/ "Can I buy cloud storage without KYC?") covers the account side of the same question.

## Which tool should you pick?

**Pick by the job, not by the cipher: all four use well-studied, documented designs.**

- **Backups of a server or laptop**: restic or Kopia. Both encrypt always, deduplicate and keep snapshots. Restic's design document says everything in a repository is encrypted and authenticated. See [restic on PrivateS3](https://privates3.com/restic-backup-storage/ "Where should I store restic backups?").
- **A folder kept in sync**: rclone with a `crypt` remote. The rclone docs say names are encrypted by default and contents use NaCl SecretBox.
- **Clicking, not typing**: Cryptomator creates a vault you drag files into, then sync or upload the vault folder.

The [encryption how-to](https://privates3.com/guides/how-to-encrypt-files-before-cloud-upload/ "How do I encrypt files before uploading them to the cloud?") walks through rclone crypt and Cryptomator side by side.

## What does client-side encryption still leave visible?

**Sizes, times and the account's activity.** Rclone's crypt documentation says file length can be calculated to within 16 bytes and modification time stays readable, since sync needs it. Restic and Kopia hide file names inside packs, but pack sizes and upload times remain.

On top of that, PrivateS3 keeps request records: Request logs (source IP, time, bucket, operation, bytes) are kept 14 days for abuse handling and quota accounting, then deleted. PrivateS3 read the documentation of each tool on 17 November 2026; the table above quotes their own descriptions. Encryption hides what you store, not when or how much. That is the honest boundary, and it is the same at every S3 seller.

## What happens if you lose the key?

**The data is gone, and no one can bring it back.** Restic's manual says a lost password means the data is irrecoverably lost. Rclone's crypt docs warn that a changed or lost password leaves earlier content undecryptable. PrivateS3 never holds these keys, so support cannot help.

Store the password in a password manager and on paper in a second place. For a team, two people should hold it. No storage seller can recover a client-side key: it is the price of a key only you hold.

## Encrypted storage: common questions

### Does client-side encryption slow uploads?

Slightly, on the CPU of the machine that encrypts. On a modern computer the network is usually the limit, not the cipher.

### Can I search encrypted files in the bucket?

Not from the bucket side, since names and contents are scrambled. Search works through the tool, which decrypts the index locally.

### Is PrivateS3's AES-256 at rest enough?

Against stolen disks, yes. Against the operator, no: the operator holds that key. Encrypt on your side for that.

### Can I mix tools in one bucket?

Yes, in separate folders: for example a restic repository in one prefix and an rclone crypt folder in another.

### Does encryption change the price?

No. Encrypted data counts toward the quota like any other: $5.40/TB-month, or $2.23 on 12 months.

**Verdict**

- **Encrypt on your side, then store on PrivateS3**: the bucket sees only ciphertext, sizes and times, from $2.23/TB-month on 12 months.
- **Treat the key as the data**: lose it and the files are lost, at PrivateS3 or anywhere else.

## Sources

1. [References: design and cryptography](https://restic.readthedocs.io/en/stable/100_references.html) — restic documentation (read 17 November 2026)
2. [Crypt](https://rclone.org/crypt/) — rclone (read 17 November 2026)
3. [Repositories](https://kopia.io/docs/repositories/) — Kopia (read 17 November 2026)
4. [Security architecture](https://docs.cryptomator.org/security/architecture/) — Cryptomator (read 17 November 2026)
5. [External Storage configuration](https://docs.nextcloud.com/server/stable/admin_manual/configuration_files/external_storage_configuration_gui.html) — Nextcloud Administration Manual (read 17 November 2026)

**Storage for your encrypted files: 5 TB for 12 months, $133.87** Any client-side tool, no API fees, paid in crypto. [Get storage](https://privates3.com/app/checkout/?plan=s3-5t-12m&product=storage&from=encrypted-cloud-storage&lang=en)

---

PrivateS3: PrivateS3 sells S3-compatible object storage billed per terabyte for backups and files (restic, rclone, Veeam, Cyberduck, Nextcloud), meant to be encrypted on the customer's side before upload. A terabyte costs $5.40 a month or $26.77 for 12 months, 10% under the lowest comparable offer read on 17 November 2026, with no API or egress fees up to 3 times the stored size, paid in crypto with no ID document.
