
Your Cloud Provider Can Read Every File You Back Up — Encrypt Them with rclone in 10 Minutes
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
- Press n for a new remote
- Name it drive
- Pick your provider — Google Drive, OneDrive, Dropbox, Backblaze, S3 — the list is long
- 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
- Press n for a new remote
- Name it secret
- Choose the crypt type
- Remote to encrypt: drive:backups
- 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 XStep 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
| Task | Command |
|---|---|
| Configure remotes | rclone config |
| List what's really stored | rclone ls drive:backups |
| List through the crypt layer | rclone ls secret: |
| Test a sync without writing | rclone sync SRC secret:docs --dry-run |
| Read a file back | rclone 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.
Derrk Samuel
Web3, crypto, and Linux PC insights — practical guides, security tips, mining setups, blockchain tools, and decentralized tech strategies for techs.
Related Articles

TailsOS: How to Create a Bootable USB With Persistent Storage (Full Guide)

How to Flash Tails OS to a 512GB SSD — Wipe, Flash & Configure Persistent Storage

The Flash Worked — Now Make the Router Earn It: 30 Minutes From OpenWrt to a Network You Control
Discussion
Leave a comment
No comments yet. Be the first to start the discussion!