De-Googling your Life: The full 30-Day Teardown

Nobody wakes up one morning having decided to give a single American company their email, their photos, their calendar, their contacts, their documents, their location history, their search queries, their browser, their phone's operating system, and their video habits. You just say yes to convenient things for fifteen years and then one day you look up.

The good news: it comes apart. The bad news: it does not come apart in a weekend, and anyone who tells you otherwise has never tried to move 60GB of photos while also needing their calendar to work on Tuesday.

So here's a 30-day teardown. The order matters far more than the tools.

Before you start: 2 rules!

Rule 1: Nothing goes dark. Every switch happens in parallel first. New thing runs alongside old thing until you trust it, then you cut. People who rip out their email on day one end up crawling back by day three and concluding de-Googling doesn't work. It works. Big-bang migrations don't.

Rule 2: Know why you're doing it. There are three different motives here and they lead to different endpoints:

• Reduce data exhaust: You want less of your life feeding one profile.
• Reduce dependency: You don't want one company's policy change to break your life.
• Increase control: You want the data on hardware you can touch.

Beginners usually want the first. Advanced folks usually end up chasing the third. Both are legitimate, but the third costs real time, and it's worth being honest with yourself on day zero.

Days 1–3: Reconnaissance

Don't change anything yet. Go and look. Download your data export. Not to read it but to feel the weight of it. Most people are quietly rattled by the location history and the search archive, and that's a useful fuel source for the next four weeks.

Then audit third-party access: every site where you clicked "Sign in with Google." This is the part people forget, and it's the reason month-two de-Googling attempts collapse. If forty services authenticate through your Google account, that account is load-bearing. You can't remove a load-bearing wall until you've put a post under it.

Days 4–7: The easy wins

Start where the switching cost is near zero and the payoff is immediate.

Search. Change your default. That's it. That's the whole task. You'll have a mild adjustment period, you'll hit a few queries where you go back, and within a fortnight you'll stop noticing. This is the single highest ratio of privacy-gained to effort-spent in the entire project.

Browser. Move to something not built by an advertising company, import your bookmarks, and turn on tracker blocking. Do this before email, because your browser is where every other migration happens.

Maps. Install an alternative and use it for a week of trips you already know. Don't test a new navigation app on the way to the airport. Test it on the way to the supermarket.

You are now roughly 40% less legible to Google, and you haven't done anything hard yet. Sit with that for a second because it's the most important lesson of the whole month. Most of the exposure comes from a handful of defaults, not from heroic infrastructure work.

Days 8–14: Email, the hard one

Email is difficult for exactly one reason: it's your identity. Every password reset in your life points at it.

The move that works is the forward-and-drain method.

1. Get a new address at a provider you've chosen deliberately. Use your own domain if you can. This is the advanced play, because it means your next migration is a DNS change instead of another month of this.
2. Set the old account to forward everything to the new one. Send from the new one immediately.
3. Now drain the list from Days 1–3. Every time a genuine email arrives at the old address, go update that account's login. Banks and government first, shopping last.
4. Expect the tail to last months. That's fine. The old account becomes a spam sink, not an active mailbox.

Meanwhile, replace "Sign in with Google" on anything that matters. Where possible, switch to email-and-password with a proper password manager, or passkeys. Every one of those you remove is a dependency retired.

Days 15–21: Photos, files, and the storage question

Here's where the fork appears. The pragmatic path: move to an encrypted cloud provider. You export, you upload, you get sync and phone backup and sharing, and you're done in a weekend. You've solved data exhaust and mostly solved dependency. You have not solved control, because it's still someone's server.

The sovereignty path: self-host. A small always-on machine at home, photo sync, file sync, calendar and contacts served over standard protocols. Now you genuinely own it.

And now you own the hard part too: you are the backup plan. Self-hosting without offsite, tested, encrypted backups isn't independence, it's a single point of failure with extra confidence. The rule is three copies, two media, one offsite, and (the bit everyone skips) one restore actually performed. A backup you've never restored is a rumour.

Calendar and contacts are the sleeper win in this week. They ride on open standards, which means they're the least painful thing to move and the easiest to keep portable forever.

Days 22–27: The phone

This is the boss level, and it's optional.

God mode: a de-Googled Android build. Genuinely transformative, genuinely fiddly, and a real compatibility bet (banking apps in particular can be a real pain in the ass sometimes).

Sane mode: keep the phone, strip the layer. Replace the default keyboard, browser, maps, and mail apps. Turn off ad personalisation and location history. Use an app store that lets you install open-source software. You'll capture most of the benefit for about 5% of the pain.

Either way, the keyboard matters more than people expect. It sees literally everything you type.

Days 28–30: Lock the door and look back

Delete what you've finished with such as services, then data, then eventually the account itself if you've truly drained it. Screenshot your third-party list so future-you knows what was cut.

Then do the honest accounting. Write down what broke, what you missed, and what you quietly reverted. Maybe you kept YouTube. Maybe collaborative documents pulled you back for work. That's not failure but rather your actual threat model revealing itself, which is worth more than a clean scoreboard.

What you're really buying

Thirty days doesn't get you purity. It gets you optionality: the ability to leave any one provider without your life seizing up. Own domain, open standards, local copies, no single sign-on chokepoint.

Purity is a destination. Optionality is a property. Only one of them survives the next terms-of-service update.