SecureMint

Encrypt Files Before Uploading to Google Drive

Worried about Google scanning your cloud files? r/privacy threads with 60+ upvotes keep asking the same question: 'How do I encrypt files before uploading to cloud?' The usual answers — VeraCrypt, Cryptomator, 7-Zip — all require installs or cross-platform pain. SecureMint solves this entirely in the browser: AES-256-GCM encryption with PBKDF2-SHA256 key derivation, no account, no upload to our servers. You encrypt locally, then upload the resulting .enc file (or self-decrypt HTML) to Google Drive yourself.

SecureMint uses zero-knowledge design. The server cannot read your data.

Steps

1

Open SecureMint /encrypt

Go to securemint.app/encrypt. This page runs entirely in your browser — open DevTools Network tab if you want to verify no file is uploaded.

2

Pick the file you're about to upload to Google Drive

Drag and drop any file, or pick a folder's worth of files. There is no size limit for local encryption — only your device's memory.

3

Set a strong password you'll remember

Use a passphrase of 4+ random words or a 16+ character random password. PBKDF2-SHA256 with 600,000 iterations makes brute-force impractical. Store it in a password manager.

4

Download the .enc file and upload THAT to Google Drive

You'll get a .enc (or self-decrypting .html) file. Upload this ciphertext to Google Drive, Dropbox, OneDrive, or any cloud. Even if the provider is breached, your file is unreadable.

Why It's Secure

  • AES-256-GCM authenticated encryption — tampering is detected automatically.
  • Nothing is uploaded to SecureMint. Verify in DevTools → Network tab (you should see no POST requests).
  • Works on any OS with a browser: the encrypted file is cross-platform. No VeraCrypt container format lock-in.
  • Self-decrypt HTML option means the recipient (or future-you) doesn't need SecureMint to decrypt.

FAQ

Why not just use Google Drive's built-in encryption?
Google Drive encrypts at rest, but Google holds the keys. They scan contents for malware, CSAM, and TOS compliance. Zero-knowledge means only you hold the key — Google cannot decrypt even if legally compelled.
Is this different from just 7-zipping with a password?
Yes. ZIP AES-256 encryption leaks filenames by default, uses older key derivation, and isn't authenticated — tampered ciphertext silently corrupts the output. SecureMint uses GCM authentication and modern PBKDF2-SHA256 (600k iterations).
Can I open the .enc file on a different computer?
Yes. Go to securemint.app/receive on any device with a browser, drop the .enc file, enter the password. Or use self-decrypt HTML mode for a fully standalone file.