Your Cloud Provider Can Read Every File You Back Up — Encrypt Them with rclone in 10 Minutes

Your Cloud Provider Can Read Every File You Back Up — Encrypt Them with rclone in 10 Minutes

Derrk SamuelSeptember 22, 20266 min read
The terms of service you scrolled past say your provider scans what you store. rclone's crypt layer encrypts every file — names included — before it leaves your machine: three config screens, one command, and backups nobody but you can read.

The Fine Print You Scrolled Past

Every mainstream cloud provider reserves the right to scan your files — the terms of service call it "malware and abuse prevention," and it means their systems read what you store. Meanwhile the breach headlines never stop: credentials leak, accounts get taken over, and whatever sat in that account — tax documents, wallet exports, the folder literally named "backup" — goes with it.

You can't stop using cloud storage. You can stop it being readable.

The Payoff: Unreadable by Design

rclone has a crypt layer that encrypts everything before it leaves your machine — filenames included. What lands in your cloud is indistinguishable from noise: to the provider, to a hacker holding your password, to anyone else. Ten minutes and one extra config screen, and your backups are files like a91f...3c.bin — every one of them, forever, automatically.

Step 1 — Install rclone

curl https://rclone.org/install.sh | sudo bash
rclone version

Step 2 — Connect Your Storage

rclone config
  1. Press n for a new remote
  2. Name it drive
  3. Pick your provider — Google Drive, OneDrive, Dropbox, Backblaze, S3 — the list is long
  4. Follow the OAuth prompts (on a headless server, run rclone authorize "drive" on your desktop machine and paste the token back)

Step 3 — Add the Crypt Layer

Back into the same menu:

rclone config
  1. Press n for a new remote
  2. Name it secret
  3. Choose the crypt type
  4. Remote to encrypt: drive:backups
  5. Set a password and a salt — rclone obscures them in the config, but obscuring is not encryption: those two values ARE the key

Treat the crypt password like a seed phrase. If it's lost, the backups are gone forever — no provider support ticket can recover them. Store it in a password manager and on paper somewhere safe.

“Treat the crypt password like a seed phrase. If it's lost, the backups are gone forever — no provider support ticket can recover them. Store it in a password manager and on paper somewhere safe.”

Share on X

Step 4 — Prove the Roundtrip

echo "if you can read this, encryption failed" > test.txt
rclone copy test.txt secret:
rclone ls drive:backups

That last command shows a file with a machine-garbled name and a .bin suffix — open the same folder in your provider's web UI and you'll see the same gibberish. Now read it back through the crypt layer:

rclone cat secret:test.txt

Plain text out, noise at rest. That's the whole trick.

Step 5 — Automate It

One cron entry, 3 AM nightly, mirroring your documents into the encrypted remote:

0 3 * * * rclone sync ~/Documents secret:documents

Test the command by hand first: rclone sync ~/Documents secret:documents --dry-run shows what would transfer without touching anything.

Quick Reference

TaskCommand
Configure remotesrclone config
List what's really storedrclone ls drive:backups
List through the crypt layerrclone ls secret:
Test a sync without writingrclone sync SRC secret:docs --dry-run
Read a file backrclone cat secret:test.txt

The Wrap-Up

Encrypted backups turn cloud storage into what it should have been all along: dumb, blind, cheap space that you alone can read. Set the cron entry, forget it, and the day a provider gets breached, your name won't be in the interesting part of the dump.

Hit a snag — the OAuth loop on a headless box, a crypt password lost (I'm sorry), or cron refusing to fire? Drop a comment below and I'll help you untangle it.

D

Derrk Samuel

Web3, crypto, and Linux PC insights — practical guides, security tips, mining setups, blockchain tools, and decentralized tech strategies for techs.

Discussion

Leave a comment

No comments yet. Be the first to start the discussion!