Integration

You’ve spent 11 weeks building your privacy infrastructure. Now it’s time to put it all together into a sustainable daily practice.

This final week isn’t about learning new tools—it’s about making everything you’ve learned work together seamlessly. By the end, you’ll have a complete privacy workflow that protects you without getting in your way.

Your Complete Privacy Stack

Let’s recap what you’ve built:

Foundation Layer (Weeks 1-3)

• Threat model: You know what you’re protecting and from whom
• Linux Mint: Privacy-respecting operating system with full disk encryption
• Hardened Firefox: Browser configured to minimize tracking and fingerprinting

Communication Layer (Weeks 4-6)

• Password manager: Unique, strong passwords for every account
• Proton Mail + aliases: Private email that doesn’t track you
• Signal: End-to-end encrypted messaging

Network Layer (Weeks 7-8)

• Mullvad VPN: Hide your IP from websites and ISP
• Tor Browser: True anonymity when needed

Protection Layer (Weeks 9-11)

• VeraCrypt/LUKS: Encrypted storage for sensitive files
• 2FA everywhere: Accounts protected beyond passwords
• OpSec habits: The mindset and practices that make tools effective

Part 1: Your Daily Privacy Routine

Morning Checklist

When you start your computer:

1. System boots → Enter LUKS passphrase
2. VPN connects automatically → Verify with tray icon
3. Password manager unlocks → Ready for the day
4. Firefox opens → Containers active, extensions working

Verification (weekly):

• Check https://mullvad.net/check for VPN status
• Verify no DNS leaks at https://ipleak.net

During the Day

For general browsing:

• Use Firefox with VPN connected
• Appropriate container for each context (work, personal, banking)
• Password manager for all logins

For sensitive research:

• Switch to Tor Browser
• Security level: Safer or Safest
• Don’t log into personal accounts

For communication:

• Signal for sensitive conversations
• Proton Mail for private email
• Standard email with aliases for services

Evening/Weekly Maintenance

Daily:

• Lock screen when stepping away
• Close sensitive browser tabs when done

Weekly:

• Check for system updates: sudo apt update && sudo apt upgrade
• Review password manager for old/weak passwords
• Clear any accumulated browser data

Monthly:

• Check Have I Been Pwned for new breaches
• Review connected apps on accounts
• Verify 2FA still working on critical accounts
• Test backup restoration

Part 2: Context-Based Workflows

Workflow: Financial Activities

Setup:

1. Use dedicated “Banking” container in Firefox
2. VPN connected (or disable if bank blocks)
3. 2FA required for all financial accounts

Process:

1. Open Banking container
2. Navigate directly to bank (never click email links)
3. Use password manager to fill credentials
4. Complete 2FA
5. Finish and close container

Never:

• Click links in banking emails
• Use public WiFi for banking
• Save banking passwords in browser (use password manager)

Workflow: Sensitive Research

When to use: Researching topics you don’t want associated with your identity

Setup:

1. Disconnect from VPN (Tor handles anonymity)
2. Open Tor Browser
3. Set security level to Safer or Safest
4. Check https://check.torproject.org

Process:

1. Don’t log into any accounts
2. Keep browser window default size
3. Use New Identity between topics
4. Close when done

After:

• New Identity before closing (clear state)
• Close Tor Browser completely
• Reconnect VPN for regular browsing

Workflow: New Account Creation

For services you’ll use with real identity:

1. Use unique email alias (SimpleLogin/AnonAddy or Proton)
2. Generate strong password in password manager
3. Enable 2FA immediately
4. Save recovery codes in encrypted storage

For anonymous/throwaway accounts:

1. Use Tor Browser or VPN
2. Use throwaway email (not linked to identity)
3. Different username than your regular ones
4. Different password (still in password manager, marked as anonymous)

Workflow: Receiving Sensitive Files

1. Don’t open directly—download first
2. Disconnect from internet (optional for extreme caution)
3. Scan with ClamAV: clamscan filename
4. Check file metadata: exiftool filename
5. Open in sandboxed application if available

Workflow: Sharing Sensitive Files

1. Strip metadata: mat2 filename
2. Encrypt if sharing: age -r recipient-key -o file.age file
3. Share via encrypted channel (Signal, Proton)
4. Verify recipient received correctly

Part 3: Layered Security Decisions

The Decision Tree

When deciding what protection level to use:

Is this sensitive?
│
├── No → Regular Firefox + VPN
│
└── Yes → What kind of sensitive?
    │
    ├── Personal (banking, medical)
    │   → Dedicated container + VPN + 2FA
    │
    ├── Private research
    │   → Tor Browser (Safer level)
    │
    └── High-risk (activism, journalism)
        → Tor Browser (Safest) + consider Tails

Matching Tools to Threats

When NOT to Use Privacy Tools

Some situations where maximum privacy isn’t appropriate:

• Banking: May trigger fraud detection, use carefully
• Work accounts: May violate acceptable use policies
• Services requiring identity: Government, medical, etc.
• Emergency situations: Don’t let privacy prevent getting help

Privacy is a tool, not a religion. Use appropriate levels for each situation.

Part 4: Handling Edge Cases

When Your VPN Goes Down

Kill switch enabled (it should be):

• Internet stops working—this is intentional
• Reconnect VPN or disable kill switch temporarily
• Never disable kill switch for sensitive activities

If something leaked:

• Affected sites saw your real IP
• Change any sensitive sessions
• Consider if activity was sensitive enough to matter

When a Site Requires Disabling Protection

Site doesn’t work with VPN:

1. Try different VPN server
2. If critical, use split tunneling for just that app
3. Accept real IP exposure for that site

Site requires JavaScript (Tor):

1. Lower security level temporarily
2. Consider if site is worth the risk
3. Use New Identity after visiting

When You Suspect Compromise

Signs:

• Unexpected login notifications
• Password reset emails you didn’t request
• Strange activity in accounts
• Friends receiving messages “from you”

Response:

1. Don’t panic
2. Change passwords (start with email)
3. Check active sessions, revoke unknown ones
4. Enable 2FA if not already
5. Check for unauthorized recovery options
6. Monitor for continued suspicious activity

When Traveling

Before travel:

• Consider travel device with minimal data
• Enable hidden VeraCrypt volume for plausible deniability
• Know your rights at borders (varies by country)

During travel:

• Power off devices at borders (encryption protects when off)
• Use VPN on hotel/airport WiFi
• Be cautious of public computers

After travel:

• Check for tampering
• Change passwords used while traveling
• Review account activity

Part 5: Building Sustainable Habits

The 1% Rule

You don’t need to be 100% private to benefit. Each improvement matters:

• Using Signal for some conversations → better than none
• VPN most of the time → better than never
• Strong passwords on important accounts → better than weak everywhere

Progress over perfection. Don’t let perfect be the enemy of good.

Making It Automatic

The best security is security you don’t have to think about:

• VPN auto-connects at boot
• Password manager always running
• Firefox containers handle isolation
• 2FA becomes muscle memory

Reduce friction: If a security practice is annoying, you’ll stop doing it.

When You Slip Up

Everyone makes mistakes:

• Clicked a suspicious link? → Check for compromise, change passwords
• Forgot VPN was off? → Most sites aren’t logging your IP maliciously
• Used weak password once? → Change it now, move on
• Posted something revealing? → Delete if possible, learn for next time

Don’t catastrophize. Assess actual risk, take appropriate action, continue practicing.

Part 6: Going Further

Privacy 101 is Complete—What’s Next?

Immediate improvements:

• Gradually migrate remaining accounts to privacy-respecting services
• Practice until tools become automatic
• Share what you’ve learned with trusted others

Cypherpunk School 101 (our advanced course) covers:

• GnuPG for cryptographic signatures and encryption
• SSH for secure remote access
• Advanced anonymity with Tails and Whonix
• Self-sovereign identity
• Applied cryptographic protocols

Continuous learning:

• Follow privacy news (EFF, Privacy Guides, Krebs on Security)
• Stay updated on tool changes
• Adapt to new threats as they emerge

Contributing to the Movement

Privacy improves when more people practice it:

• Help friends and family with basic security
• Recommend privacy-respecting services
• Support organizations fighting for digital rights
• Use encrypted communication (normalizes it)
• Run Tor relay if you have bandwidth

Privacy 101 Graduation

You’ve completed the course. You now have:

✅ Knowledge: Understanding of threats, tools, and trade-offs

✅ Infrastructure: Complete privacy stack installed and configured

✅ Habits: Daily practices that maintain your privacy

✅ Mindset: OpSec thinking that makes tools effective

Completion Checklist

Here’s everything you’ve accomplished over 12 weeks:

Week 1: Foundations ✓

• Understand why privacy matters
• Create personal threat model
• Identify what you’re protecting

Week 2: Operating System ✓

• Running Linux Mint
• Full disk encryption enabled
• Updates configured

Week 3: Browser ✓

• Firefox hardened
• Essential extensions installed
• Containers configured

Week 4: Passwords ✓

• Password manager set up
• Unique passwords everywhere
• Master password secured

Week 5: Email ✓

• Private email provider (Proton/Tutanota)
• Email aliases configured
• Old accounts migrating

Week 6: Messaging ✓

• Signal installed and configured
• Disappearing messages enabled
• Safety numbers verified

Week 7: VPNs ✓

• VPN set up and running
• Kill switch enabled
• DNS leak protection verified

Week 8: Tor ✓

• Tor Browser installed
• Security levels understood
• Know when to use Tor vs VPN

Week 9: Storage ✓

• LUKS configured
• VeraCrypt for sensitive files
• Encrypted backups in place

Week 10: Authentication ✓

• 2FA on critical accounts
• TOTP app configured
• Backup codes secured

Week 11: OpSec ✓

• Identities compartmentalized
• Security maintenance scheduled
• Threat model documented
• Privacy mindset adopted

Week 12: Integration ✓

• Complete privacy workflow established
• Daily habits in place
• Ready for ongoing practice

Your Privacy Workflow Summary

Daily:
├── Boot → LUKS password → VPN auto-connects
├── Browse → Firefox + containers + extensions
├── Communicate → Signal + Proton Mail
├── Authenticate → Password manager + 2FA
└── Lock → Screen lock when stepping away

Weekly:
├── System updates
├── Password review
└── Browser cleanup

Monthly:
├── Breach check (HIBP)
├── Account review
├── 2FA verification
└── Backup test

As needed:
├── Sensitive research → Tor Browser
├── Sensitive files → VeraCrypt container
├── New accounts → Alias email + unique password
└── Threat model update → After life changes

Summary

This week you:

• Reviewed your complete privacy stack
• Established daily, weekly, and monthly routines
• Created context-based workflows for different activities
• Learned to match tools to threats appropriately
• Developed habits for sustainable privacy practice
• Prepared for continuous improvement

You’ve completed Privacy 101.

You’re no longer a passive participant in the surveillance economy. You have the tools, the knowledge, and the habits to take control of your digital life.

Privacy is a human right. Now you know how to exercise it.

Welcome to the cypherpunk community.

← Back to Week 11: Operational Security

Continue to Cypherpunk School 101 →