💡 왼쪽 원문을 읽으면서 오른쪽에 따라 써보세요. Tab 키로 힌트를 받을 수 있습니다.

원문 렌더가 준비되기 전까지 텍스트 가이드로 표시합니다.

Introduction — "Gmail thinks I am stupid, so I left"

In June 2026, two posts landed side by side on the Hacker News front page. One was a personal blog post titled "Gmail thinks I'm stupid, so I left." After nearly twenty years on Gmail, the author wrote, the product had started treating its user as someone incapable of making decisions: unwanted AI summaries forced on top of messages, important mail hidden by opaque criteria, settings that quietly resurrect themselves after the next update. The other was a TechCrunch article reporting that DuckDuckGo had made its no-AI search mode easier to access — and that traffic to it was booming. Both posts drew long comment threads on GeekNews as well.

It is no coincidence that these two stories trended together. They signal that fatigue with big tech's strategy of wedging AI features into every product is crossing a threshold. What is interesting is that this wave of departures is motivated differently from the privacy movements of the past. It is not ideology; it is usability. My tool started getting in my way, the feature I turned off turned itself back on, and my data has slipped out of my control — these concrete annoyances are what is moving people.

This post is not a sermon about why you must leave Google. It is a practical guide that calculates, as of 2026, how mature the alternatives are in each domain, what switching actually costs, and how far it is rational to switch.

Why People Leave — Three Accumulated Grievances

The motivations boil down to three strands.

1. AI shoehorning: AI summaries forced above search results, AI reply suggestions in the inbox, AI buttons in document tools. There is no off switch, or it is buried deep, or it resets with every update. DuckDuckGo pulling in traffic with a no-AI mode is the direct result of targeting exactly this pain.

2. Dark patterns: the cancel button buried deep, the consent button rendered huge. Refusing ad personalization routes you through a longer flow, and defaults are always set in favor of data collection. Regulatory fines keep coming, but the pattern itself has not gone away.

3. Data collection: profiling built on search history, location history, and mail contents. Even if you consented to each item individually, the combined profile when one company holds search plus mail plus maps plus browser plus OS is a problem of a different order.

A fourth motivation became visible in 2026: single-account dependency risk. If one Google account gets suspended, mail, photos, drive, YouTube, and OAuth sign-ins all lock at once. This is why every account-suspension appeal posted to HN draws hundreds of comments.

Alternatives by Domain

Search

| --- | --- | --- | --- | --- |

Based on real-world use, DuckDuckGo is a sufficient replacement for general web search. Korean-language search quality remains a weakness versus Google, which the partial-exit strategy below accounts for. Kagi has the entry barrier of being paid, but many say the single feature of permanently blocking content-farm domains from results is worth the price alone.

Mail — The Most Important Domain

Mail is the heart of degoogling and the domain that demands the most care, because password resets for every other service arrive by mail.

| --- | --- | --- | --- | --- |

One principle matters more than which service you pick: use a custom domain. If your address is myname at gmail.com you are locked to Gmail; if it is myname at proton.me you are locked to Proton. But with me at mydomain.com, you can swap the service behind it any time. Owning the domain is owning your mail sovereignty. Ten to fifteen dollars a year for a domain is the price of that freedom.

Browsers

| --- | --- | --- | --- |

If you also care about checking the Chromium monoculture, Firefox deserves the vote; if you depend heavily on Chrome extensions, Brave is the realistic compromise.

Maps, Photos, Drive

| --- | --- | --- | --- |

Self-hosting Options — With Difficulty Ratings

If you can run your own server, the menu widens. Difficulty is shown in stars (1 star easy, 5 stars hard).

| --- | --- | --- | --- |

Getting Immich running is about this simple.

mkdir immich && cd immich

wget https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml

wget -O .env https://github.com/immich-app/immich/releases/latest/download/example.env

edit the upload path and DB password in .env, then

docker compose up -d

open http://your-server:2283 in a browser, register the server URL in the mobile app

That said, self-hosting carries invisible costs. Backups are your responsibility (the 3-2-1 rule: three copies, two media types, one offsite), and so are security patches. For data you cannot afford to lose, like photos, think of self-hosting plus encrypted offsite backup as a package deal. Self-hosting mail deserves its own warning: due to IP reputation and spam deliverability, even veterans advise against it. Letting a paid service run your mail while you own the domain is close to the correct answer.

Hands-on — The Mail Migration Procedure

Here is the hardest and most important migration, step by step. The core principle: no big-bang cutover; migrate gradually.

[Step 0] [Step 1] [Step 2] [Step 3] [Step 4]

Buy domain ──> Open new ──> Set Gmail ──> Change address ──> Demote Gmail to

+ prep DNS mailbox forwarding per service a receive-only

+ import old + start sending (over months) archive

mail from new address

Step 0 — prepare the domain. Buy a domain and add the DNS records your mail service specifies. Example for Fastmail.

MX @ in1-smtp.messagingengine.com (priority 10)

MX @ in2-smtp.messagingengine.com (priority 20)

TXT @ "v=spf1 include:spf.messagingengine.com ?all"

CNAME fm1._domainkey fm1.mydomain.com.dkim.fmhosted.com

CNAME fm2._domainkey fm2.mydomain.com.dkim.fmhosted.com

CNAME fm3._domainkey fm3.mydomain.com.dkim.fmhosted.com

TXT _dmarc "v=DMARC1; p=quarantine; rua=mailto:dmarc-report@mydomain.com"

All three of SPF, DKIM, and DMARC must be configured or your outgoing mail will land in spam folders. Verify with a checker (mxtoolbox and the like) after setup.

Step 1 — import old mail. Most paid mail services offer Gmail IMAP import. Alternatively, download an mbox file via Google Takeout for archival. Twenty years of mail is a personal record in its own right — always keep a copy.

Step 2 — set up forwarding. Turn on full forwarding to the new address in Gmail settings. From this point, watching only the new mailbox shows you everything. Start sending from the new address too.

Step 3 — change the address on each service. This is the main game. Export your account list from your password manager and work through it by importance.

- Top priority: finance (banks, cards, brokerage), government, telecom

- Next: work tools, cloud accounts, developer accounts (GitHub, cloud consoles)

- Last: shopping sites, newsletters, communities

One extra trick: use a distinct alias per service. Register as shop-amazon at mydomain.com and you can instantly identify the source of a leak and disable just that alias.

Step 4 — demote Gmail. After months of monitoring forwarded mail and catching stragglers, keep Gmail as a receive-only archive. No need to delete it — it retains value for recovering ancient accounts.

Cost Math — The Price of Free vs Paid Subscriptions

To the retort "Google is free, why pay?" there are two answers. First, the price of free is your data, ad exposure, and the usability erosion described above. Second, the actual cost of a paid stack is smaller than you think.

| Item | Example service | Yearly cost (in dollars) |

| --- | --- | --- |

| Domain | One dot-com | about 12 |

| Mail | Fastmail Standard | about 60 |

| Search | Kagi Starter | about 60 |

| Photos | Self-hosted Immich (share of home server power) | about 20 |

| Cloud backup | Encrypted offsite 100GB | about 24 |

| Total | | about 176 |

That is 176 dollars a year — roughly 15 a month. Go with free DuckDuckGo for search and it drops to 116 a year. For the price of a few coffees you get services where you are the customer. The old adage that in ad-funded services the user is the product, not the customer, converts into roughly this much money.

The Partial-Exit Strategy — You Do Not Have to Leave Everything

The number one cause of failed degoogling is perfectionism. People try to change everything, burn out, and revert everything. Approach it with a priority matrix instead.

High impact (sensitive data)

[Priority 2] | [Priority 1]

Photos (Immich) | Mail (custom domain)

Drive | Search (default engine)

| Browser

High ------------------+-------------------> Low

cost | cost

[Defer] | [Priority 3]

YouTube | Calendar, contacts

Leaving Android | Maps (for travel)

Low impact

Priority 1 (high impact, low cost): change the default search engine (5 minutes), switch browsers (half a day), secure a mail domain (one weekend). Priority 2 is photos and drive — high impact but lots of data to move. Fully leaving YouTube and Android is low return on cost; deferring them is nothing to be ashamed of. The key is breaking the combined profile. With search here, mail there, and maps elsewhere, no single company can draw your whole picture.

Notes for Korean Users

The Korean environment adds extra variables.

- Public-sector and banking compatibility: government sites and banks are often tested against Chromium-family browsers. Even with Firefox as your daily driver, keeping Brave or another Chromium browser solely for government/banking — a dual-browser strategy — is the realistic move.

- Domestic maps: Google Maps was always weak in Korea; the real alternatives are Naver Map and KakaoMap. In Korea the maps domain is already a local-service dependency rather than a Google one, and the privacy-pure alternatives (OSM family) are weak at domestic business search. Using Organic Maps only for overseas travel is a sensible compromise.

- Identity verification: phone-based identity verification and PASS function as stronger identifiers than mail, so changing your email mostly preserves account continuity on Korean services. Conversely, that means changing the registered email on domestic services is relatively easy.

- Kakao/Naver dependency: the Korean version of degoogling effectively bundles in de-Kakao and de-Naver problems. Messengers are the hardest domain due to network effects — putting them in the defer quadrant of the matrix is good for your sanity.

Recommendations by Threat Model

Privacy is not one-size-fits-all. Calibrate intensity to your own threat model.

| --- | --- | --- | --- |

For developers in particular, 2026 events — the npm supply chain attack reaching Red Hat Cloud Services, the 1-click GitHub token theft via a VSCode extension flaw — show that accounts and tokens themselves are targets. Mail sovereignty and hardware-key two-factor authentication are matters of security practice, not just privacy.

Liberating Your Data — Making the Most of Google Takeout

Migration starts with extracting your data wholesale. Requesting a full archive from Google Takeout yields tens of gigabytes of zips. Practical tips:

1. Format choices matter. Mail comes as mbox, calendars as iCal (.ics), contacts as vCard (.vcf), photos as originals plus JSON metadata.

2. 10GB split parts beat 50GB parts when a download fails and needs retrying.

3. The archive is not single-use. Even after migrating, keep it on an external disk as a point-in-time backup.

For moving the archive offsite, the canonical method is rclone with an encrypted remote.

configure an rclone encrypted remote (interactive)

rclone config

n) new remote -> name: backup-crypt -> type: crypt

target: any cloud remote path; choose to encrypt filenames and contents

upload the Takeout archive

rclone copy ./takeout-2026 backup-crypt:takeout-2026 --progress

verify (checksum comparison)

rclone check ./takeout-2026 backup-crypt:takeout-2026

This produces a backup that even the cloud provider cannot read.

Photo Migration — From Takeout to Immich

Google Photos Takeout archives separate the image originals from their metadata JSON, so a naive copy breaks capture dates. The community tool immich-go solves this.

point it at the Takeout zips without extracting them;

it reads the JSON metadata and restores capture dates/albums while uploading

immich-go upload from-google-photos \

--server http://my-server:2283 \

--api-key MY_IMMICH_API_KEY \

./takeout-*.zip

Verify three things after upload: photo counts match, capture-date ordering is correct, album structure is restored. Once confirmed, enable auto-backup in the mobile app so new photos go straight to Immich. Clean up Google Photos after a few months of observation.

Calendar and Contacts — Surprisingly Easy

Thanks to standard formats, calendar and contacts are a thirty-minute job.

Calendar: Google Calendar -> settings -> export -> download .ics

Upload the .ics in the import menu of the new service (Proton/Fastmail)

Contacts: Google Contacts -> export -> vCard (.vcf)

Import the .vcf in the new service

Ongoing sync then runs over the standard protocols CalDAV (calendar) and CardDAV (contacts). Both iOS and Android support CalDAV/CardDAV under account settings, so the OS-native calendar and contacts sync without any special app. Pick services that speak standard protocols and your next move gets easier still.

Alias Mail — The Key Tool for Leak Tracing and Spam Control

Paired with a custom domain, alias services are powerful.

| Service | Cost | Notes |

| --- | --- | --- |

| SimpleLogin | Free to 36 dollars/year | Acquired by Proton; replies can be sent from the alias |

| Fastmail masked addresses | Included in plan | Generation integrated with password managers (1Password) |

| addy.io | Free to 12 dollars/year | Open source, self-hostable |

The operating rule is simple: real address for people, aliases for services. When spam starts arriving at some alias, that service is the leak source, and disabling just that alias ends it. A side benefit: you stop agonizing over which email to use at sign-up.

Browser Hardening — What to Do After Switching

Switching browsers is only half the job. The following settings complete the set.

1. Install uBlock Origin. The point is blocking tracking scripts, beyond just ads. It runs at full strength on Firefox, which continues to support Manifest V2.

2. Change the default search engine to DuckDuckGo or Kagi, and disable address-bar suggestion features that send keystrokes externally.

3. Block third-party cookies and set a cookie-clearing schedule. Firefox Total Cookie Protection is on by default.

4. Use Firefox container tabs. Isolate work that needs a Google account (YouTube and so on) in a dedicated container — you stay logged in there while separating it from activity in other tabs.

5. Enable DNS over HTTPS to reduce ISP-level DNS query logging.

If you care about fingerprinting, remember that piling on extensions backfires — your extension combination itself becomes a fingerprint. A few vetted extensions plus built-in browser protections is the orthodox setup.

DNS-level Blocking — The Whole Device at Once

To reduce tracking by apps outside the browser, DNS-level blocking is efficient.

| Method | Difficulty | Notes |

| --- | --- | --- |

| NextDNS | 1 star | Cloud service, per-device profiles, 300k free queries |

| Pi-hole | 2 stars | Home server / Raspberry Pi; covers the whole home network |

| AdGuard Home | 2 stars | Pi-hole alternative; encrypted DNS out of the box |

Install Pi-hole (Docker)

docker run -d --name pihole \

-p 53:53/tcp -p 53:53/udp -p 8080:80 \

-e TZ=Asia/Seoul \

-e FTLCONF_webserver_api_password=changeme \

-v ./etc-pihole:/etc/pihole \

--restart unless-stopped \

pihole/pihole:latest

point your router DHCP DNS at the Pi-hole IP to cover the whole house

A common combination: NextDNS-style cloud filtering when away from home, Pi-hole at home, splitting the roles.

Mobile — How Far to Go on Android and iOS

Mobile is the final boss of degoogling and the most expensive domain.

- Pragmatic route (1 star): keep your current phone, audit Google app permissions, reset/delete the advertising ID, apply the DNS blocking above. Limited effect, near-zero cost.

- Middle route (3 stars): swap default apps for alternatives — keyboard (an open source keyboard instead of GBoard), photos (the Immich app), maps (Organic Maps), browser (Firefox). Leave the OS alone.

- Hard route (5 stars): switch to a degoogled OS like GrapheneOS (Pixel only). Sandboxed Google Play services preserve compatibility, but Korean banking and identity apps sometimes fail device-integrity checks, so for Korean users a secondary-device approach is advisable.

iOS has low Google dependency but swaps it for Apple dependency — recognize the structure and judge by your threat model.

The 30-day Plan — Done in Four Weekends

Week 1: Foundations

[ ] Buy domain, sign up for mail service, configure DNS (SPF/DKIM/DMARC)

[ ] Adopt a password manager (or audit the one you have)

[ ] Switch browser + uBlock Origin + change default search

Week 2: Begin the mail cutover

[ ] Enable full Gmail forwarding, start sending from the new address

[ ] Change mail on finance/government/telecom accounts (top 10 first)

[ ] Request a full Google Takeout archive and back it up offsite

Week 3: Move the data

[ ] Migrate calendar/contacts via .ics/.vcf, set up CalDAV/CardDAV sync

[ ] (Optional) Stand up Immich, migrate photos with immich-go

[ ] Change mail on dev/work accounts, register hardware-key 2FA

Week 4: Wrap-up and steady state

[ ] Move shopping/community accounts to alias mail

[ ] Apply DNS blocking (NextDNS or Pi-hole)

[ ] Demote Gmail to receive-only archive, schedule a monthly review

Frequently Asked Questions

Question: should I delete my Google account entirely?

Answer: not recommended. It retains residual uses — recovering ancient accounts, managing Android devices. Emptying the core data and keeping it dormant is the practical move.

Question: my company runs Google Workspace — is any of this meaningful?

Answer: treat the work account separately; that is your employer's choice. The goal is your personal data under your personal control, not changing your workplace tooling.

Question: what if the paid service goes under?

Answer: this is exactly why custom domains and standard formats (mbox, ics, vcf) are the core. Services can die, but the address and the data remain yours, and moving to the next provider costs about as much as editing DNS records.

Question: how much is enough?

Answer: revisit the threat model table. A general user who stops at priorities 1-2 (mail sovereignty plus search/browser) has already achieved the core goal of dismantling the combined profile.

Question: what do I do when search quality falls short?

Answer: use a fallback strategy. In DuckDuckGo, prefixing a query with the g-bang syntax sends just that one search to Google. A structure of privacy search by default with Google as the exception lasts far longer than all-or-nothing.

Realistic Limits and Balance — A Critical View

For balance, the counterarguments.

- Asymmetric security capability: Google's account security infrastructure (phishing detection, anomalous-login blocking) is world-class. Sloppy self-hosting can end up less secure than Google. Privacy and security are different axes, and that must be acknowledged.

- The convenience cost is real: integrated search across the ecosystem, photo search quality, and the spam filter remain best in class. An alternative stack means giving up some of this.

- Alternative services are companies too: Proton and Kagi can change policies. Which is why the essential investment is in mobility — custom domains, standard protocols, export features — rather than in any one service.

- Perfect anonymity is not the goal: blocking fingerprinting and payment trails escalates costs exponentially. For a general user, the rational goal is not "untraceable" but "dismantle the combined profile and remove the single point of failure."

Final Checklist

When you think the migration is done, audit it with the list below.

- [ ] You own a custom domain, with auto-renewal and expiry alerts configured

- [ ] SPF/DKIM/DMARC all pass in a verification tool

- [ ] Finance/government/telecom/developer accounts all use the new address

- [ ] Every account is in your password manager, with hardware keys on the critical ones

- [ ] The Google Takeout archive is encrypted and stored offsite

- [ ] Photo data exists in at least two places (the 3-2-1 rule)

- [ ] Backups and updates for self-hosted services are automated or scheduled

- [ ] Gmail forwarding is active, with a monthly straggler-account review on the calendar

- [ ] The browser default search is changed and uBlock Origin is active

- [ ] A migration plan for family-shared data (shared albums and such) has been agreed

That last item matters more than it looks. A solo migration breaks down at shared albums and shared documents. Data shared with family or a team requires agreement before it moves.

Closing

The author of "Gmail thinks I'm stupid" did not leave over grand ideology, but over the accumulated sense that the tool no longer respected its user. The good news in 2026 is that the alternatives have matured. DuckDuckGo proved the demand with a traffic surge for its no-AI mode, self-hosted tools like Immich have become weekend-project easy, and paid mail services paired with custom domains deliver genuine freedom of movement.

You do not need to change everything. This weekend, buy one domain and change your default search engine. Those two small steps are the most cost-effective actions for breaking the combined profile.

References

- Gmail thinks I'm stupid, so I left (original): https://moddedbear.com/gmail-thinks-im-stupid-so-i-left

- TechCrunch — DuckDuckGo no-AI search traffic boom: https://techcrunch.com/2026/06/01/duckduckgo-makes-its-no-ai-search-engine-easier-to-access-as-its-traffic-booms/

- Privacy Guides (the standard reference for alternatives): https://www.privacyguides.org/

- DuckDuckGo: https://duckduckgo.com/

- Kagi: https://kagi.com/

- Proton Mail: https://proton.me/mail

- Fastmail: https://www.fastmail.com/

- mailbox.org: https://mailbox.org/

- Immich (self-hosted photos): https://immich.app/

- Nextcloud: https://nextcloud.com/

- Firefox: https://www.mozilla.org/firefox/

- Hacker News: https://news.ycombinator.com/

- GeekNews: https://news.hada.io/