Dev.to Security 🔐 Cybersecurity 👁 0 📖 3 min read

I Switched to Encrypted Everything After Chat Control Passed

so chat control passed and i had what i can only describe as a "privacy reckoning." i looked at my digital life and realized how much of it was running through services that would soon be legally required to scan everyth

so chat control passed and i had what i can only describe as a "privacy reckoning." i looked at my digital life and realized how much of it was running through services that would soon be legally required to scan everything.

here's what i switched, why, and what the experience has been like after 3 weeks.

email: protonmail → tuta

i'd been on protonmail for years, but i switched to tuta (formerly tutanota) for two reasons:

  1. tuta has been more vocal about resisting chat control implementation
  2. tuta uses their own encryption protocol rather than PGP, which is more resistant to certain metadata analysis techniques

the experience: honestly, the transition was rough for the first few days. tuta's interface is clunkier than protonmail's. but after a week, i barely noticed. the encryption is automatic for tuta-to-tuta emails, and the calendar integration works well enough.

downside: tuta's search is terrible compared to protonmail. you can only search unencrypted metadata, not email content. this is a direct trade-off of their encryption model.

cloud storage: google drive → proton drive → self-hosted

i initially moved to proton drive, but the storage limits were too small for my needs (i have about 800GB of files). so i set up a nextcloud instance on a VPS in switzerland.

the experience: nextcloud is incredible once it's running. file sync, calendar, contacts, notes, kanban boards — all encrypted, all under my control. the setup took an entire weekend, but now it just works.

the catch: i'm responsible for my own backups. i have a cron job that creates encrypted daily backups to a separate storage provider. if my server dies, i lose nothing. but this took time to set up properly.

messaging: signal (already) + matrix

i was already on signal for personal messages. i added matrix (specifically element) for group chats and communities.

why matrix: matrix is federated, meaning no single company controls it. even if the main matrix.org server gets hit with a detection order, self-hosted servers can continue operating without scanning.

the experience: matrix/element is significantly less polished than signal or whatsapp. the UI is confusing for non-technical people. i've managed to get about 15 of my contacts to use it, but most of my social circle still uses whatsapp for group chats.

browser: firefox + hardened config

i was already on firefox, but i hardened it significantly:

  • strict tracking protection
  • container tabs for isolating different identities
  • ublock origin with custom filter lists
  • disabled telemetry
  • resist fingerprinting enabled

the experience: some websites break. maybe 5-10% of sites have issues with the hardened config. i keep a separate firefox profile for sites that need to work (banking, government services).

DNS: adguard DNS

switched all my devices and my router to adguard DNS. blocks trackers and surveillance domains at the DNS level.

the experience: faster page loading (because trackers aren't loading), zero configuration needed after setup, and i occasionally get a satisfying "blocked" notification when an app tries to phone home.

password manager: bitwarden → self-hosted vaultwarden

already used bitwarden, but switched to self-hosted vaultwarden on the same VPS as nextcloud.

the experience: identical to bitwarden, but under my control.

the honest assessment

3 weeks in, here's what's true:

the good: i feel significantly more in control of my digital life. knowing that my data isn't being scanned by automated systems is a weight off my mind.

the bad: it takes time. everything i switched to requires more maintenance than the "just use google" approach. some things are less polished. my non-technical friends think i'm paranoid.

the reality: this isn't for everyone. but if you're a developer, if you're technical, if you understand the risks — there's no excuse not to at least start migrating. it doesn't have to be all at once.

i put together a practical guide based on my experience: How to Protect Yourself After Chat Control

start with one thing. just one. then do another next week. that's how you build a private digital life.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.