The Story

On March 16, 2026, my Google Ads account ran 334 changes in 61 minutes. None were mine. The next morning Google suspended my locksmith business for "malware" on a website Google itself rates clean. Eight weeks, two lawsuits, and one FedEx signature later, Google still hasn't picked up the phone. This is what actually happened.

1. The business that depends on the platform

I run Public Locksmith out of Charlotte, North Carolina. I'm the licensed locksmith on the truck (NC #2721) and the person answering the phone at 2 a.m. Like most service businesses in 2026, the way customers find me is Google. Specifically, two Google products: paid Google Ads at the top of search results, and Google Local Services / Google Guaranteed in the local pack with the green checkmark. About 70% of my new customers come from one of those two channels. The rest come from word of mouth, repeat customers, and the occasional Yelp click.

I mention this not as a complaint about platform dependence — that's a separate conversation — but to set the stakes. When Google cuts off both channels in the same night, the phone literally stops ringing. Not slows down. Stops.

2. What the records show

Sometime around midday on March 16, 2026, an unauthorized third party gained access to my Google Ads account. Google's own change log — the same audit log Google provides every advertiser as evidence of who did what — records 334 individual changes inside a 61-minute window. New campaigns created. Bid caps raised. Geographic targeting changed. Keywords added that have nothing to do with locksmiths.

By the time I noticed and locked the account back down, the unauthorized activity had generated $3,973.75 in charges to my linked payment method. The fraudulent campaign was running ads that had nothing to do with my business or my service area. I don't have those keywords in my account today; I never had them; my dispatch records show no leads from those terms.

At the same time, Google's own Safe Browsing tool — the public service Google runs to identify malware sites — rated publiclocks.com as clean, with no security issues found. Anyone reading this can verify that themselves at transparencyreport.google.com/safe-browsing/search. The site has been rated clean before, during, and after the suspension.

3. The appeal that wasn't

On March 17, the morning after the unauthorized activity, Google suspended my account and labeled the violation "Malware Software." My website hadn't changed. There was no malware. I submitted an appeal the next day, March 18, with the audit log attached and a screenshot of the Safe Browsing report showing the site was clean.

The denial came back in under two hours. Google's own published policy says appeals typically take around five business days for human review. The denial arrived in less time than it would take to read the full audit log I attached. The reason given was a copy-paste of the original suspension reason, with no engagement with the evidence I'd submitted.

4. What that did to the business

Before the suspension, my Google Local Services account had generated 220 leads. After the suspension: zero. Not a slow trickle. Not a few. Zero. The Local Services account stops appearing in the local pack when the underlying Google Ads account is suspended, even though Local Services is technically a separate product. My phone, which had been averaging 0.86 calls per day from those channels, dropped to 0.20 per day — a 77.3% drop.

Translated to revenue, the documented gap is approximately $198 per day, accruing every day the account remains suspended. As of today, that's eight weeks and counting. That's not an estimate I made up; it's based on the average ticket size from those channels in the 90 days before the suspension and the volume of leads I'm not getting now.

5. The trap: I can't fix what they're asking me to fix

Here's the part of this story that, if you've never been on the receiving end of platform support, will sound made up. To get the account un-suspended, Google's automated reply says I need to remove the policy-violating campaign — that is, the fraudulent campaign that an unauthorized stranger created in my account in the 61-minute attack. To remove the campaign, I would need to log into the account and delete it. But I can't log into the account, because the account is suspended. The thing they're requiring me to do is the thing the suspension prevents me from doing.

Within roughly 24 hours of the unauthorized activity, Google attempted to collect approximately $4,000 in additional charges for the fraudulent campaign — billing for ads I never approved, on a campaign I didn't create, while my account was already suspended for the activity that generated those charges. The collection attempt failed because I had moved my payment method by then. If I hadn't moved fast enough, the actual loss would have doubled, on top of the $3,973.75 already taken.

And there is no human at Google a paying advertiser can reach to point out the contradiction. There's no phone number that connects to a person with authority to lift a suspension. The chat support is a triage script that loops back to the same suspension page. The appeal form has no place to attach a 30-second video showing me trying to log in and being blocked. The ToS arbitration clause has no documented small-claimant track record. The user-facing system, by structural design, has no way to handle the case where Google itself is wrong. That's not a bug. That's the shape of the system.

6. What happens when you actually sue

After the appeal denial, after weeks of trying to get through Google's regular support channels, after watching my dispatch board go quiet day after day, I filed a small-claims action in Mecklenburg County, North Carolina, against Google LLC. Small claims is the system designed exactly for this — a clear contract, a clear violation, a documented dollar amount. The filing fee is roughly the cost of dinner. The case asked for the $3,973.75 in fraudulent charges Google had retained.

Service of process is the next step. North Carolina law lets you serve a corporation through its registered agent. Google's NC registered agent is Corporation Service Company at 2626 Glenwood Ave, Suite 550, Raleigh, NC 27608. On March 26, 2026, FedEx delivered the summons and complaint to that exact address. The package was signed for by H. Bughs. I have the FedEx delivery confirmation. The signature is on file.

From the moment of service, the clock starts. The defendant has a defined window to respond, appear, or settle. None of that happened. 36 days went by. No phone call from Google's legal department. No email asking to discuss. No filing in the court file. No restoration of my account. No refund of the fraudulent charges. Silence.

7. Today: a second lawsuit

The small-claims case alone wasn't going to fix this. The damages had grown past the small-claims jurisdictional limit. The harm wasn't just the $3,973.75 anymore — it was every day of suspended advertising access stacking on top. So today, May 1, 2026, I filed a second action, this one in the Mecklenburg County General Court of Justice, District Court Division. Three counts:

Count I — Breach of Contract. The Google Ads Terms of Service is a contract. Charging me for unauthorized activity, then suspending the account on grounds inconsistent with Google's own data, breaches that contract. Count II — Negligence. Account-security practices that allow 334 changes in 61 minutes from an unauthorized source, with no real-time anomaly detection that pauses spending until the account holder confirms, fall below the standard of care a reasonable platform owes its paying advertisers. Count III — Unfair and Deceptive Trade Practices under N.C.G.S. § 75-1.1. North Carolina's UDTP statute attaches treble damages to unfair or deceptive acts in commerce. The complaint alleges the suspension reason and the appeal handling fit that statute. UDTP also creates a fee-shifting pathway.

Alongside the complaint, I filed a Rule 65 motion for a Temporary Restraining Order and preliminary injunction asking the court to order Google to restore advertising access pending the merits hearing. Documented continuing damages: ≥$8,712 and accruing approximately $198/day.

8. Why this matters beyond one locksmith

If you've never run a small business that depends on Google Ads or Local Services, the structure of the problem may not be obvious. So here it is in plain terms. The advertiser pays Google. Google holds the funds. Google retains them when the activity that generated the charges turns out to be unauthorized. The advertiser appeals. Google denies the appeal — sometimes within hours, before any human can credibly have reviewed the evidence. The advertiser has no functional escalation path. Email support is automated. There's no phone number that reaches a human with authority. There's no arbitration clause that's actually been used by a small claimant in the public record.

When formal legal process is finally served, the documented response — based on this case — is silence. That silence is a posture. It's a calculation that the cost of ignoring small claimants individually is lower than the cost of building a real review system. That calculation only changes when the costs change. The costs change when the documented record is public, when other small businesses with similar receipts come forward, and when the regulatory and judicial conversation moves beyond the assumption that platforms self-police adequately.

If you're a business owner who's been through some version of this — a Google account suspended after unauthorized activity, fraudulent charges Google retained, an appeal denied without substantive review, a sharp drop in lead flow you can document, harm that hasn't been resolved despite formal written notice — please share your story below. Confidentially. Without obligation. The intake form is at the bottom of this page. Documented receipts move the conversation. One locksmith on his own moves nothing.