Bonus material
- Part
- 10 of 10
- Course
- A six-week GDPR curriculum for small companies
Bonus
This is how I continuously improved a part of my business until I've gotten to the point where even if I were stripped of all my possessions and thrown into a different country, I could still get my whole business back in just a few hours. As long as I get my hands on a laptop, that is.
At the Beginning
Before I started to get into GDPR, I had a standard setup: A computer with no backups for most things. At least my code was backed up on Github. But beyond that, I relied on the service providers I used. If I lost the emails I already had downloaded to my machine, I had to hope that my email provider still had their copies.
And then I got into GDPR, and I started coming up with disaster scenarios. What if my machine breaks? Well, I better have a backup in that case. And so I got an external drive and started to regularly copy things over.
But That's Not Enough
But what if someone breaks in and steals my machine? Okay, I encrypt my system. But what about the backups? Alright, let's encrypt those too. But what if I lose my USB stick with my password manager on it? Then the backups are useless, because I can't decrypt them... Fair enough, let's memorize the password.
So I've setup a password that's both easy to remember and hard to guess: Seven random words are easy to remember and provide over 90 bits of entropy. Ask your favorite AI how hard that would be to guess, even if you were to use all computers on the planet for it.
But what in the case of fire? Okay, none of my solutions cover the case where everything I have is lost. Which means.. I had to go online.
And I looked around for good, GDPR compliant solutions, and AWS was one of them. But one important aspect of backups is that you can actually access them. And if I lose everything, including any papers or USB sticks, how would I manage to get into my AWS account? I needed a solution that would be easily accessible, but still safe. And AWS S3 buckets weren't it.
Proton is a swiss company focused on privacy-first online services, and that includes encrypted cloud storage. And in there you can make shareable links to folders inside your cloud storage. That means that anyone who has the link can access it. But you can also password protect them. You might have guessed it - I generated another set of seven random words, and used that as the password.
But the URL to that backup folder itself is hard to remember - it's random letters and numbers. So I needed a place to store the link and the specific commands I'd need to decrypt my backups. Did I mention that the files I upload to Proton are encrypted, even though they encrypt everything as well? Well, there's no reason not to encrypt the files before uploading them to Proton.
Back on track. To get easy access to the Proton link and the decryption commands (just the commands, without the passwords of course), I've setup a TXT record on the subdomain of one of my domains. You know how you can enter a link like "https://antidefault.com" in your browser, and it finds out the IP address and connects to that server? That's done via A and AAAA records. A TXT record is a piece of text that's attached to a link the same way an A or AAAA record is. There's only so much text you can store in them, but it's enough for the link and the command. And "TXT record on random-word.domain.com", that's something I can easily remember.
To Summarize
There's a bit more to it - I've written more on my blog: Proper Paranoia: Basic Resilience Against Catastrophes (2025) [1] - but I think you can see how this developed. I didn't implement a solution for every single scenario right out of the box. I started with simple backups, and then step by step I improved the whole thing until I had something that allowed me to sleep really well at night. It feels good to know that I'm covered even in the worst cases.