Leaving Google in 2026, after the reCAPTCHA wall
The old fear was Google deleting your account. The new one is duller: every site that uses reCAPTCHA quietly deciding a de-Googled phone isn't human. What the wall reaches, what it doesn't, and where your files can live on the other side of it.
A user on GrapheneOS tries to sign up for an ordinary website. They get a checkbox that says “I'm not a robot.” They tick it. The checkbox loops back to itself, refuses to complete, and a message eventually appears that says, in effect, you are not human. Their phone is fine. Their connection is fine. What is missing is Google Play Services, which the newer reCAPTCHA quietly uses to decide whether a device is real. This is the reCAPTCHA wall, and the conversation about leaving Google in 2026 has just changed shape because of it.
What changed, mechanically
reCAPTCHA is Google's anti-bot service. Most of the web uses it. The traditional version watched mouse movements and page behavior. The newer version, the one rolling out aggressively this year, makes a different kind of check on Android: it asks the device to produce a Play Integrity attestation, a signed claim from Google Play Services that the operating system is “approved” by Google. On a de-Googled Android phone, that signature is not available. The result is not a soft “please retry”; it is a hard wall. The site does not see a human. It sees nothing it recognizes.
This is not happening on every site. It is happening on enough sites, with enough momentum, that the de-Googled-Android community spent the past week trading screenshots and asking what they should do.
The fear has changed shape
For a long time the fear of using Google was sized like this: one day they delete your account, and you lose everything. That fear is real, and the threads about Google blow my life up randomly are still there. It turns out the more imminent version is duller and harder to reason about. Not that Google deletes your account, but that the rest of the web, by leaning on Google's anti-bot service, quietly starts declining to talk to you when you stop being deeply enrolled in Google's ecosystem.
This is friction-against-the-exit. It is what a vendor does when leaving is technically still possible but the cost of leaving keeps going up.
What the wall reaches, and what it doesn't
It helps to look at the actual surfaces.
The wall reaches every site that uses reCAPTCHA with the newer attestation modes. That includes a lot of sign-up forms, government portals, banks, airline booking pages, forum registrations. It also touches Gmail's own sign-up flow now, which is a separate but related story: registering a new Gmail account requires a QR scan and a phone number on certain device profiles. None of this is fixed by switching browsers.
The wall does not reach files. The way a phone or laptop talks to a file server over a private network does not pass through reCAPTCHA. Your photos and documents do not need to prove they are human. Sending a file from your phone to a small device sitting on a shelf in your apartment, over a WireGuard tunnel, has no occasion to ask Google whether the phone is real.
This is the part of leaving Google that has nothing to do with Google. The photos, the family videos, the receipts, the scanned documents, the music collection, the backups of the cloud accounts you have not closed yet. They live somewhere physical. The question is whether that somewhere is a vendor's bucket, where the next policy change might fence you out, or a drive in a box you control, which does not need Google's permission to exist.
This is the lane Harbor Dock occupies. A small ARM board, a USB drive, a Tailscale network, and your files are reachable from your phone without going through any third party's reCAPTCHA, sign-in flow, or device-attestation check. It does not, and cannot, solve reCAPTCHA on the rest of the web. The web problem is a browser problem, not a storage problem. It can take a meaningful chunk of personal data out of the same blast radius.
The honest tradeoffs
A few things should be said clearly.
De-Googling an Android phone is a separate decision, and a harder one. Moving to GrapheneOS, /e/OS, or LineageOS commits to dealing with the reCAPTCHA wall every time it shows up on a site you needed. Some people will conclude that the cost is too high right now, especially for shared devices and family members who did not sign up for the project. That is a defensible call. The files-and-photos decision is a smaller commitment and lands earlier in most people's leaving-Google timeline.
Harbor's pitch is not “leave Google today.” It is more modest: you do not have to de-Google your phone this year, but you do need somewhere to put the photos and documents that aren't going to ask you to prove you're human in five years. Whatever you decide about reCAPTCHA, the storage question is solvable now, with hardware you can hold, on a network only your devices can see.
The reCAPTCHA wall has made the cost of leaving Google's services visible in a way the abstract “vendor lock-in” discussion never quite did. The wall is a real thing that returns a real “no” on a real site. The right response is not to panic about the phone. It is to make sure the rest of the surface, the parts where there is no wall, is already on your side of it.