A Bot Deleted My Account. Google's Fix: Delete My Family.
Published on • 11 min read
Quick recap for anyone joining late: in June, a bot deleted my 16-year-old YouTube account for “spam,” named no offending content, and rejected my one allotted appeal faster than a human could have read it. That post was about the deletion. This one is about the cleanup, because it turns out getting unpersoned is just the opening act. The encore is discovering what your account was load-bearing for.
A few weeks after the notice and the insta-denied appeal, I did the thing everyone tells you is impossible: I got a human at Google. Or at least I’m 85% confident I did — the typing rhythm was irregular, the sympathy felt hand-crafted, and no language model would voluntarily admit this little could be done. They were genuinely kind. I want to be clear about that, because nothing that follows is their fault. I asked for a fix, and they gave me the fix, and the fix is the problem.
The Knot
Here’s the situation the bot left behind. For years I’ve been the manager of my family’s Google family group. We set it up so family and friends could share one YouTube Premium subscription: my wife, family members, everyone’s music and ad-free viewing hanging off my account. The one the bot deleted.
So today, right now, my family and I are paying for a subscription that I — the person whose card is on file — cannot use. I get the ads. I get the “you should try Premium!” upsells. I am, as far as YouTube’s billing system is concerned, a paying customer; as far as YouTube’s trust-and-safety system is concerned, I don’t exist. These two departments do not appear to be on speaking terms.
But the family group doesn’t just share Premium. Google family groups also share storage. Which means my Google Drive — the one I’ve been filling since 2010, back when it was still Google Docs and the cloud was a novelty — is tangled into the same knot.
The Official Fix
Here is the solution, straight from my sympathetic human, lightly paraphrased:
- Delete my family group. As manager, only I can do this. The bot couldn’t be bothered, so the honor falls to me.
- Have my wife create a new family group and re-invite every existing member.
- Rejoin my own family — but under a brand-new email address, because my old identity is radioactive and can never hold a YouTube subscription again.
- Export my entire Google Drive via Google Takeout — terabytes of it — and re-upload everything to the new account, because the storage my files live in is welded to the family group I just deleted.
Read step one again. Google’s official remediation for a bot deleting my account is that I should delete my family. I’ve written some dark comedy on this blog, but I’ve never written a line that twisted!
Takeout Is Aptly Named
Now, step four. On paper, “export and re-upload” sounds like a weekend of sad progress bars. Annoying, survivable. But I’m a data scientist, and I’ve spent enough of my career on data provenance to know what Takeout actually hands you.
Takeout gives you the files. It does not give you the history of the files. When you re-upload sixteen years of Drive to a new account, you lose:
- Version history. Every document becomes brand new, born today, with no record of how it evolved.
- Sharing permissions and sharing history. Every collaborator link dies. Every “shared with X on date Y” record evaporates.
- The audit trail. Ownership, activity, comments-in-context — the entire chain of custody, gone.
For a folder of vacation photos, who cares. But I’ve spent my career collaborating with scientists. Most of my real data lives in public repositories where it belongs, but scattered through that Drive are one-off slide decks, back-of-the-envelope calculations, review notes — the connective tissue of sixteen years of collaboration, with friends and family and half the co-authors I’ve ever had. After the migration, every record of who I shared what with, and when, is a blank page. If you’re a person with actual compliance obligations — clinical data, grant deliverables, anything a lawyer might someday subpoena — this isn’t an inconvenience. It’s a chain-of-custody bonfire, and Google offers no tooling whatsoever to carry any of it across.
So that’s my choice. Door number one: keep paying for music I can’t play. Door number two: torch the provenance of my entire digital life so I can hear an album without ads. The support agent and I sat with that for a moment. I believe we were both sad.
The Early-Adopter Tax
Here’s the part that stings in a different register. I have always been a Google early adopter, and an enthusiastic one. I was in Google Wave trying to convince people it was the future of email. I posted earnestly into the void of Google+. And when Google Photos launched in 2015, I went all in — every photo, every event, every kid’s birthday, uploaded and organized and shared. That was the deal as I understood it: I give you my time and a frankly intimate amount of my data, and you give me quality products. For sixteen years, Google held up its end.
Now the Photos tentacle of this knot. The pixels themselves are safe — I’m a data scientist, I have the originals redundantly backed up on my NAS and in Amazon Photos, because paranoia is a professional skill. But the shared albums are not pixels. Hundreds of them, spanning years of birthday parties, small gatherings, trips — each one a little collaborative artifact with contributions from other people, comments, the record of who shared what with whom. All of it hangs off the same radioactive email address as everything else. There’s no Takeout for the shared-ness. Rebuilding it means hundreds of hours of manually re-exporting, re-uploading, and re-inviting, and some of it — other people’s contributions to albums I no longer control — may simply be gone.
And I notice the wound is deeper here. Files can be replaced. Research connections can be re-established with an apologetic email. But when it’s the album of your kid’s fourth birthday, assembled by six phones over one afternoon, the loss stops being an IT problem. That’s the salt in the wound: you trust these companies with the irreplaceable stuff because they spent two decades earning it, and then you discover the trust only ever ran in one direction. There is no accountability to the small person. There is a support chat, and the support chat is sorry.
Antitrust, Suddenly Non-Abstract
Which brings me to the thought I can’t shake: every hour of this cleanup is a monopoly tax.
Walk the counterfactual with me. If YouTube were a standalone company and its bot deleted my account, I would lose… my YouTube account. Annoying! But my email wouldn’t care. My files wouldn’t care. My family’s photo albums wouldn’t notice. The blast radius of one company’s broken moderation system would be one company’s product. Instead, because Google spent twenty years fusing video, email, storage, photos, and family billing into a single load-bearing identity, one spam classifier’s false positive is now reaching into my kid’s birthday albums. The blast radius is the bundle. And this isn’t a Google-specific sin — Apple welds your purchases, photos, and devices to one Apple ID with the same single point of failure; every mega-platform does it, because lock-in is the business model.
We mostly experience antitrust as an abstraction — economists arguing about consumer prices, a DOJ filing you skim past. It’s hard to feel a basis point. But this is what market concentration actually looks like when it lands on one person: not a price on a chart, but a father doing hundreds of hours of unpaid data migration because the company that owns his music also owns his memories, and its robot made a mistake it won’t let a human review.
The Part That Actually Makes Me Angry
Here’s what I keep coming back to. YouTube has a three-strike policy. It’s a good policy! A warning, then escalating strikes, then termination. It exists precisely so that a person like me — sixteen years, zero strikes — gets a chance to say “oh no, sorry, which video? I’ll take it down right now.”
And I would have. In a heartbeat. I made seven podcast episodes with NotebookLM; if a single email had said “these trip our AI-content rules, remove them,” they’d have been gone before lunch and I’d have grumbled about it over exactly one beer. Instead the system skipped every rung of its own ladder, went straight to the guillotine, and left me negotiating a hostage exchange where the hostage is my own file history.
The Unofficial Appeals Court
So the official channels are exhausted: one appeal, one bot, one denial. But it turns out there’s an unofficial appeals process, and it’s depressingly well documented: go viral.
In late 2025, Search Engine Journal cataloged a string of channels that were terminated by the same automated system, denied on appeal, and then restored — not because anyone re-reviewed the case, but because the case got loud. The film-analysis channel Final Verdict was terminated for “spam” (hello, old friend), posted the receipts on X, watched the thread take off, and was quietly reinstated. The true-crime channel The Dark Archive got its account back after publicly tagging @TeamYouTube. A streamer named Proko got TeamYouTube to admit the error in public — an admission the private appeal process had already declined to make. A tech YouTuber with 350,000 subscribers was terminated for being “linked” to an unrelated banned account, and the decision held right up until the story spread on X. YouTube’s official comment on all this: the “vast majority” of terminations are upheld, and only “a handful” get reversed. A handful, that is, of the ones that trend.
Notice what the pattern actually says. The appeal that matters isn’t the button in the UI — it’s the quote-tweet. Due process at YouTube is adjudicated by ratio. Your case gets a human exactly when it threatens to become a PR problem, and not one second before.
And I’ll be honest: I hate everything about this as a strategy. Airing grievances on the internet until a corporation flinches is slimy in both directions — slimy that I’d have to do it, slimier that it works. Google is a multi-trillion-dollar company. The fix for “our classifier sometimes deletes sixteen-year accounts by mistake” is not “hope the victim has reach.” It’s hiring enough humans to handle the edge cases and making the model better — two things that are, famously, what Google does for a living.
But transparency compels me to admit what you’re reading. This post is the flare. I’m not going to run a pressure campaign or rally a mob — that’s not me — but I am writing this in the open, honestly, in the hope that some human at Google stumbles across it and does the thing the bot wouldn’t: look at the actual account, for one actual minute. Because here’s my entire list of demands, and it’s embarrassingly small: put a human in the loop. Tell me which videos were the problem. I will delete every one of them, today, cheerfully, and we can all go back to pretending the three-strike policy exists.
The Lesson: Your Google Account Is a Load-Bearing Wall
If you take one thing from this saga, take this: never link YouTube to a personal account you care about. Make a satellite account. Let the satellite watch the videos, hold the subscription, absorb the bot strike. Keep your email, your documents, your family plan — your identity — somewhere the moderation classifier can’t reach it.
I didn’t do that, and I want to be honest about why: because in 2009 nobody did. There was no “data hygiene mindset” to have. You signed up for one Google account and it grew around your life organically, like ivy, and you didn’t notice it had grown into the walls until someone yanked it out. Sixteen-years-ago me wasn’t careless. He just couldn’t imagine that the same login would one day hold his music, his family’s storage, two decades of collaboration records, and a single point of failure with a bot’s finger on it.
Now we all know better. The cloud gives you exactly one identity per ecosystem, welds your life to it, and reserves the right to delete it by algorithm, without warning, with no human on the other end of the appeal.
Plan accordingly. Ivy is lovely until it’s structural.
Related Posts
I Spent 16 Years on YouTube. A Bot Deleted Me in a Day.
One June morning, Google erased my 16-year-old account without warning and rejected my appeal in minutes. Here is the timeline, and why I think an algorithm decided I was a problem.
When Email Becomes Your API: Archiving Claude Code to Evernote
Evernote suspended their developer-token API in January 2026. I needed to back up every Claude Code conversation anyway. So I turned email-to-note into a sync engine.
The New King George: 250 Grievances for the Semiquincentennial
Two hundred fifty years ago we fired a king for putting himself above the law and the treasury above the people. Here is a ranked, fully-cited catalog of 250 ways the new one brought the monarchy back.