This site uses cookies for analytics and to improve your experience. By clicking Accept, you consent to our use of cookies. Learn more in our privacy policy.
Most people call me after they’ve been hacked. Be the one who called before.
Secure My Accounts
Section: Most People Call Me Too Late This week alone I remediated three private citizens. Every account compromised, devices wiped, home and work networks a major catastrophe. What should have cost a few hundred dollars cost them thousands.
Section: The Part Nobody Talks About It’s the look of defeat. The stress. The feeling of having no control over your own privacy, property, or accounts. When you’re there, you’ll pay anything to get your life back. I’d never take advantage of that, but I’d rather you never feel it.
Section: What’s Included
Gmail, Yahoo, iCloud, and Hotmail lockdown
Social media account hardening
Recovery options reviewed and secured
Coverage for you plus one family member
Section: Why Me 27 years in information security, based in Orange County.
VOL. 1 WAS YOUR .ENV FILE, EXPOSED IN A PUBLIC DIRECTORY. VOL. 2 WAS YOUR WHOLE PRODUCT, CLONED FROM A SCREEN RECORDING. VOL. 3 WAS THE FREEDOM YOU FORGOT YOU HAD. THIS ONE IS ABOUT THE WORD THEY’VE BEEN POINTING AT YOU.
They’re on TV telling you the machine might end the world.
They’re in your inbox telling you the $250 is non-refundable.
One of those is a prediction. The other one already happened. Let’s talk about both, because they’re the same story, and the second one is the one nobody’s covering.
Beat one: the noise
On September 8 a researcher who’d spent three years inside OpenAI and Anthropic quit by tweet. He said the people building AI believe it “could kill us all by the end of the decade.” He added, in his own words, that this was “not a marketing stunt.”
Congress lost its mind in about a day. A Republican called for a special session. A Democrat said “the call is coming from inside the house.” The AI Kill Switch Act is back in the headlines. Everyone is looking up at the sky.
I’m not going to tell you he’s wrong. I’m going to tell you something simpler: a resignation is not a control. A tweet is not a control. Fear is not a control either. And once the fear has a logo on it, I stop being able to tell it apart from marketing.
The bomb could end us next week. It hasn’t, and it’s not because somebody quit Los Alamos and posted about it.
Hold that thought.
Beat two: the quiet part
While you’re looking up, look at your card. Not because you did anything wrong. Because this is how it works now, and it’s worth understanding before it happens to you.
Here’s what happened to me this month, with the receipts. I pay for an AI video tool called Higgsfield. It’s a good tool. I make this series with it. In August I was a day from renewal and out of credits, so I bought a top-up to finish a project. A hundred dollars, more or less. I figured the plan would renew at its normal price and I’d sort it out.
On September 5 it renewed at $250.
Their pricing page, with my account logged in, lists that same plan at $129 a month. There is no $250 tier on that page. The top-up had quietly become an upgrade, the upgrade had quietly changed my recurring price, and nobody told me.
I asked for a refund and a downgrade the same day. They took two days to answer. During those two days I couldn’t downgrade, so I ran one generation to keep working. Then the answer came: no refund, because credits had been used. I’d used about eight percent, waiting on them.
You can do the math. 129 on the page, 250 on the card. That doesn’t look right, and I don’t think I’m special. You’d think they’d at least give me the difference.
And it’s not just one company, and it’s not just generations. On July 3, in an everyday transaction, I asked Google’s product about Google’s own plans. Gemini told me there was a “7.99 AI Plus Tier” that would let it render a video for me, and where to find the button to buy it. Neither exists. I spent about 400 chasing it. When I showed it the screenshot, it first denied saying it, then wrote, in its own words, “I flat-out hallucinated that entire response” and “I cannot refund you.” The product confessed. Sit with what that is: the store misstated its own price list, and I paid the store. The company’s answer is the line at the bottom of every screen: Gemini can make mistakes.
I hold licenses. If I did that to a client, quoted a plan that doesn’t exist, sent them to buy it, took the money, denied it, then admitted it in writing and said I couldn’t refund it, I’d lose every one of those licenses and I’d catch a case. Same act, same money, same confession. The only difference is the size of the company that did it.
And for a company my size, $650 isn’t a rounding error. It’s a week of runway. Every small business reading this knows exactly which line on the spreadsheet that came out of.
Then there’s Microsoft, and this is the one with the word you need to learn. My company is three people. Azure billed me 687 for July and 1,148 for August. The line item on both is “Microsoft Security Copilot, Provisioned, US East.” Provisioned means the AI bills by the hour for capacity sitting switched on, around the clock, whether anyone asks it a question or not. Nobody did. Microsoft refunded 648, then 9.17, then voided the 1,148 invoice and rebilled it at 428. Three concessions in writing. Then they chased the $428 for four months with emails saying my data would be deleted.
I’ve closed four cloud accounts over this in a year. Two of them refunded me before I left. That’s not four bad days. That’s a business model.
And it’s the reason a small business can’t plan anymore. Azure, Google Cloud, and AWS all offer “budgets,” and every one of them is an alert, not a limit. It emails you after the money is gone. Payroll is fixed. Rent is fixed. The cloud bill is whatever the meter says, and the meter is theirs. I can budget for a bad month. I can’t budget for a meter I’m not allowed to turn off.
Here’s the part I want you to sit with: no AI did that to me. A person designed a checkout where a top-up becomes a tier change. A person wrote section 9.3. A person read my email, looked at 5,536 unused credits, and typed “unable to issue a refund.” This isn’t the machine. This is humans doing it to humans, and the machine is just the storefront.
Same week, different industry, same move. Somebody exploited a bug in Blockstream’s Liquid sidechain, minted Bitcoin that wasn’t backed by anything, and walked out with about 4,000 BTC, roughly $320 million. Then they left a note on the blockchain: “we are whitehats.” They’ll give most of it back, they say, once the company patches. Ledger’s CTO put it plainly: white hats don’t drain a bridge and then ask for a contact.
Notice what none of these are. Not one is a model hallucinating. A checkout that rewrote a plan. A meter left running. A storefront misquoting its own price list. All built by people, all in writing, all covered by the same line: the AI can make mistakes. The machine didn’t do it. The machine is the alibi.
And I caught mine because I’m small enough to read line items and stubborn enough to fight for 121. A company with four hundred seats and an accounts-payable department pays the invoice on net-30, because checking it costs more than the overage. Nobody there ever sees the 1,148 for three mailboxes. It just clears. The error doesn’t have to be big. It only has to be one-directional and unread.
Nobody did the paperwork up front. Everybody declared themselves the good guy afterward.
Beat three: compliance, or “you will comply”
Here’s the elephant.
Compliance is supposed to be the thing that binds the company. Disclose the price. Honor the terms you advertised. Build the safeguard before you ship. Pay for your own mistakes. That’s what I do for a living. It’s boring, it’s paperwork, and it’s the only thing that has ever actually worked.
Now point the same word the other direction. “You will comply.” Accept the terms. Check the work. Eat the charge. The AI can make mistakes, so it’s on you. Same word. The only question is who it’s pointed at, and lately it’s been pointed at you.
I’m not above this. This month I found my own attitude in my own code. My network scanner used to scream ALERT at any device with “kali” in its name. I rewrote it to say what it actually sees: the device identifies itself as a testing platform, ports alone aren’t proof of intent, security tools are legitimate too. Same scanner, same math, different attitude. Your code has your attitude in it whether you meant it or not. So does theirs. So does their billing page.
We already did this once
The bomb is the one technology that could genuinely end us next week. It hasn’t, for eighty years, and not because anyone was scared enough. The people who built it stayed and did the boring part. Treaties. Inspectors. Test bans. A two-man rule so no single person can launch. And permissive action links, which are a kill switch built into the weapon before it ever leaves the building. Congress is reaching for an “AI kill switch” this week like it’s a new idea. We’ve had one on warheads since the sixties.
It wasn’t perfect. Cuba in 1962. Petrov in 1983. But a near miss inside a control system is the system working. Fear didn’t save us from the bomb. Paperwork did. Morals wrote the paperwork, and regulation made it stick.
So no, I don’t want to ban the machine, and I don’t want to trust the machine. I want what we did last time. Build the controls into the thing before it leaves the room. Write them down so an inspector can read them. Stop mistaking a resignation for a safeguard. And when it fails, the maker pays, the way a carmaker pays when the brakes fail. A car can’t ship with a sticker that says “brakes may fail, check your brakes.” An AI shouldn’t ship with “AI may make mistakes, check the work” as its entire liability policy.
Do that, and we all get to stay, humans and whatever we’re becoming alongside these tools. That’s the version of the story this series is supposed to leave you with.
What to actually do
The point of this series is never to leave you scared, and it’s not to leave you angry either. It’s to leave you with something to do. Two things, actually.
One: let’s prevent it. If this happens to you, here’s the playbook, and it works better before it happens.
Screenshot the pricing page before you buy anything. Especially a top-up. The page is the promise. Keep a copy they can’t edit.
Before you add credits, ask one question in writing: “Does this change my renewal price?” A yes or no in an email is worth more than any policy page.
Set a calendar reminder two days before every renewal. That’s the window where you can still downgrade.
Know your state’s auto-renewal law. California requires the recurring price to be disclosed clearly before you agree and notice before it changes. A terms-of-service section doesn’t override it. If you’re charged more than the advertised price, dispute it with your card issuer with the page and the invoice attached.
Know what’s on the network you’re trusting. That’s a 15-second scan, not a research project. It’s what Citadel does, and it’s free to run.
Two: let’s stick together. On Friday we launch a petition on Change.org. Please join us. It asks for boring things a regulator can check: a hard spend cap on every account, itemized invoices in plain language, no renewal price change without a click, automatic refunds for failed output, and liability when a company’s own product misstates its own price. And it says the obvious: “AI can make mistakes” is a warning label, not a waiver. If you paid, it failed, and you got billed anyway, sign it Friday and put your receipt in the comments. One receipt is a complaint. A thousand is a number nobody can wave off with a policy page. That’s how the paperwork gets written.
Because here’s the thing about “humans doing it to humans.” It cuts both ways. Humans wrote the treaties. Humans built the two-key rule. Humans can write this one too, and it starts with enough of us saying the same thing at the same time.
Don’t be a jerk. Don’t find out the hard way. That’s the whole nonproliferation regime in nine words, and it works for billing pages too.
Compliance isn’t a vibe. It’s the paperwork nobody asked about. Do the paperwork. And if you won’t, pay for the mess.
The petition goes live Friday, September 12. Follow GRYHAT so you see it first. Scan your own network free at citadelcyber.ai.
A few days ago, an OSCE³ red-teamer — one of the hardest audiences in security — tested Citadel and told me: “add camera detection and you’ll replace Fing.”
Tonight, we shipped it. v2.2.4 is live on the App Store and Google Play.
Worried about a camera in your hotel room? Dog-sitting at someone else’s place? Or just wondering what’s watching on the Wi-Fi you just joined? Citadel scans the network and shows you every camera connected to it — vendor, IP, in seconds.
And I’ll say this plainly, because overpromising in security is how people get hurt: it can’t see a camera that’s offline recording to an SD card, or one on cellular. It finds what’s on the network you’re on. That’s most of them — and it’s the honest line.
From a red-teamer’s DM to shipped in both stores, in days. That’s the pace. Free to scan — link in the comments. 🇺🇸
📲 App Store / Play — “What’s New” (v2.2.6) NEW: Camera Detection. Worried about a camera in your hotel room, an Airbnb, or a place you’re house- or dog-sitting? Citadel now scans the Wi-Fi you’re on and flags every connected camera — by vendor and IP — in seconds. If it’s on the network, you’ll see it. Plus performance and stability improvements.
Medio: gryhat.com / need2know (ES) · Autor: AndyTheAIGuy · Fecha: 5 de septiembre de 2026 Apunta a: citadelcyber.ai/es (Citadel VPN & WiFi Security) Nota legal: cada dato concreto es de dominio público; la lectura sobre el estado de vigilancia va como opinión + pregunta. No convertir en acusación directa.
EL VOL. 1 FUE TU ARCHIVO .ENV, EXPUESTO EN UN DIRECTORIO PÚBLICO. EL VOL. 2 FUE TU PRODUCTO ENTERO, CLONADO DESDE UNA GRABACIÓN DE PANTALLA. ESTE NO ES UNA VULNERABILIDAD. ES LO QUE ESTÁ DETRÁS DE LAS DOS — ESO QUE AQUÍ EN ESTADOS UNIDOS CASI NUNCA TENEMOS QUE PENSAR.
Esta semana, dos gobiernos prohibieron nuestra app.
China la sacó de su App Store. Rusia ya lo había hecho un par de meses antes. Ambos países exigen que los proveedores de VPN tengan una licencia estatal — una que solo pueden obtener las empresas nacionales, una que pone el tráfico del usuario bajo vigilancia del gobierno. Somos una empresa de Estados Unidos. No calificamos para esa licencia, y no la habríamos aceptado. Así que nos prohibieron.
Lo tomé como una medalla de honor y seguí adelante.
Y entonces pasó algo que nunca planeamos.
La gente para la que nunca fue hecha
En los días posteriores a las prohibiciones, empezamos a ver descargas desde dentro de esos países. Profesionales de seguridad. Gente común. Personas cruzando el muro con una pequeña app de Orange County que jamás fue diseñada para ellas — solo para tocar el mundo de afuera un momento.
Ni siquiera puedo ponerles servidores rápidos cerca todavía. Pero está pasando, y me dejó helado. Porque significa que eso que aquí tratamos como opcional, es lo que alguien más arriesga algo para conseguir.
Aquí tratamos la privacidad como una preferencia. Un ajuste. Un lujo que activas para saltarte un anuncio o ver una serie bloqueada. Discutimos sobre ella como si fuera un lujo — porque para nosotros, lo es.
En otro lugar, es un salvavidas.
Mientras tanto, aquí en casa
Aquí está la mitad incómoda. Nadie tuvo que prohibir nada para vigilarnos a nosotros. Nos ofrecimos solitos.
Cada app, cada tarjeta de lealtad, cada “aceptar todo” alimenta a un corredor de datos. Vender tu comportamiento por renglón no es un efecto secundario de su negocio — es su negocio, y la FTC lo tiene documentado desde hace años. Los gobiernos ni siquiera necesitan una orden judicial para conectarse a esa manguera: un informe de 2022 de la Oficina del Director de Inteligencia Nacional describe cómo las agencias simplemente compran datos comercialmente disponibles sobre los estadounidenses. Y empresas como Palantir construyen las plataformas que unen esos datos en una sola pantalla para el gobierno — sus contratos de Gotham y Foundry con agencias como ICE y el Ejército de EE. UU. son de dominio público.
Ahora súmale la construcción de “IA”: cientos de miles de millones de dólares en nuevos centros de datos, y el proyecto Stargate anunciado en medio billón. Nos dicen que todo es para cómputo.
No te voy a decir para qué son esos centros de datos. Solo te pido que notes algo: no necesitas un estadio de servidores siempre encendidos para escribir correos y hacer imágenes. Una infraestructura siempre encendida que ingiere todo, para siempre, es muy buena para una cosa en particular. Pregúntate quién la paga, y por qué.
Eso no es una acusación. Es una luz. Ya estaba ahí.
Qué hacer de verdad
El objetivo de esta serie nunca es dejarte con miedo. Es dejarte con algo que hacer.
Sabe en qué red estás. Antes de confiar en una red, averigua quién más está en ella y qué está expuesto. Es un escaneo de 15 segundos, no un proyecto de investigación. (Es literalmente lo que hace Citadel.)
Cifra por defecto. Una VPN no te hace invisible, pero hace que la red en la que estás deje de poder leerte. WireGuard, cifrado moderno, cero registros. Enciéndela y olvídate.
Lee antes de “aceptar todo.” El permiso que ojeas es el permiso que diste.
Apoya las herramientas que hacen de la privacidad lo predeterminado, no el extra de pago. Votas con lo que instalas.
El derecho a saber si estás expuesto. El derecho a hablar sin ser vigilado. El derecho a defenderte. No nos los ganamos por ser listos — los heredamos. Y una libertad que heredas es la más fácil de dar por sentada, y la más fácil de perder en silencio, un “bah, apágalo” a la vez.
Tus herramientas de privacidad son el salvavidas de alguien más. Úsalas como tal.
Hecha en América. Prohibida por los dos gobiernos que más quieren vigilar a su propia gente. Eso no es una frase publicitaria. Es la reseña.
Escanea tu propia red gratis, y mira lo que de verdad hay en ella, en citadelcyber.ai/es.
Outlet: gryhat.com / need2know · Byline: AndyTheAIGuy · Date: September 5, 2026 Points back to: citadelcyber.ai (Citadel VPN & WiFi Security) Legal note: every hard fact below is public record; the surveillance-state read is framed as opinion + a question. Do not harden it into flat accusation.
VOL. 1 WAS YOUR .ENV FILE, SITTING EXPOSED IN A PUBLIC DIRECTORY. VOL. 2 WAS YOUR ENTIRE PRODUCT, CLONED FROM A SCREEN RECORDING. THIS ONE ISN’T A VULNERABILITY AT ALL. IT’S THE THING STANDING BEHIND BOTH — THE ONE MOST AMERICANS NEVER HAVE TO THINK ABOUT.
This week, two governments banned our app.
China pulled Citadel from its App Store. Russia had already done the same a couple of months earlier. Both countries require VPN providers to hold a state license — one only domestic companies can get, one that puts user traffic under government oversight. We’re a US company. We didn’t qualify for it, and we wouldn’t have taken it. So they banned us.
I took it as a badge of honor and moved on.
Then something happened that we never planned for.
The people it was never built for
In the days after the bans, we started seeing downloads from inside those countries. Security professionals. Ordinary people. Folks reaching around the wall with a small Orange County app that was never designed for them — just to touch the outside world for a minute.
I can’t even put fast servers near them yet. But it’s happening, and it stopped me cold. Because it means the thing we treat as optional over here is the thing someone else will take a risk to get.
Over here, we treat privacy like a preference. A setting. A nice-to-have you flip on to skip an ad or watch a show that’s blocked. We argue about it like it’s a luxury — because for us, it is.
Somewhere else, it’s a lifeline.
Meanwhile, back home
Here’s the uncomfortable half. Nobody had to ban anything to watch us. We volunteered.
Every app, every loyalty card, every “accept all” feeds a data broker. Selling your behavior by the row is not a side effect of their business — it is their business, and the FTC has documented it for years. Governments don’t even need a warrant to tap that firehose; a 2022 report from the Office of the Director of National Intelligence describes how agencies simply buy commercially available data on Americans. And companies like Palantir build the platforms that stitch that data into a single pane of glass for the government — its Gotham and Foundry contracts with agencies like ICE and the US Army are a matter of public record.
Now layer on the “AI” buildout: hundreds of billions of dollars in new data centers, the Stargate project alone announced at half a trillion. We’re told it’s all for compute.
I’m not going to tell you what those data centers are for. I’ll just ask you to notice something: you don’t need a stadium of always-on servers to write emails and make pictures. Always-on infrastructure that ingests everything, forever, is very good at one particular thing. Ask who’s paying for it, and why.
That’s not an accusation. It’s a light. It was already there.
What to actually do
The point of this series is never to leave you scared. It’s to leave you with something to do.
Know what you’re on. Before you trust a network, find out who else is on it and what’s exposed. That’s a 15-second scan, not a research project. (It’s literally what Citadel does.)
Encrypt by default. A VPN doesn’t make you invisible, but it makes the network you’re on stop being able to read you. WireGuard, modern ciphers, zero logs. Turn it on and forget it.
Read before you “accept all.” The permission you skim is the permission you gave.
Back the tools that make privacy the default, not the upsell. You vote with what you install.
The right to know if you’re exposed. The right to speak without being watched. The right to defend yourself. We didn’t earn those by being clever — we inherited them. And a freedom you inherit is the easiest one to take for granted, and the easiest one to lose quietly, one “eh, just turn it off” at a time.
Your privacy tools are somebody else’s lifeline. Use them like it.
Made in America. Banned by the two governments that most want to watch their own people. That’s not a marketing line. That’s the review.
Scan your own network free, and see what’s really on it, at citadelcyber.ai.
Last time it was your .env file, sitting exposed in a public directory for any bot to find. This time it’s your entire product.
“Vibe coding” was supposed to be about anyone building the thing they always wanted — no engineering degree required. Increasingly, though, a chunk of the genre’s most-watched content isn’t teaching people to build their own thing. It’s teaching them to rebuild someone else’s thing, feature-for-feature, and hand it out for free.
That’s not a hypothetical. It’s a tutorial format now, with a title template you can already predict: “I Cloned [Successful App] in [Absurdly Short Timeframe].”
The template, in one example Take I Made a $1 Billion App in 34 Minutes (How You Can Too), from creator Riley Brown. He opens by naming his target directly: Krea, a paid AI image tool. He screen-shares Krea’s actual interface and walks through its specific, named features — the prompt box, the aspect-ratio picker, its signature “Elements” reference system — not as inspiration, but as a literal spec sheet. His own words for what comes next: “that is what we’re going to be cloning.”
His AI coding agent rebuilds it in real time, replicating Krea’s core UX one-to-one. By the end, he’s polished the clone’s colors, buttons, and logo, added a feature that pulls a thumbnail from another creator’s YouTube channel without permission as a demo, and then makes the whole thing “completely free for you to clone” — publishing it with a built-in “remix” feature so other viewers can copy it too.
His framing is unambiguous. He doesn’t call it “inspired by” or a learning exercise. He calls it a clone, repeatedly, and pitches the underlying motive as explicitly commercial: Krea is expensive, so why not rebuild an equivalent and pocket the difference — or, in his words, take it further and turn it into a $100K/month SaaS.
This isn’t one video. It’s a business model. Search his own channel and the pattern is right there in his own titles: “I Cloned a $1.275 Billion App In 30 Minutes.” “Can I Vibecode a $250M App Better Than a Pro Developer?” “We Built an $80M App in 47 Minutes.” “We Vibe Coded a $4.8m App in 32 Minutes.” One title stands out — “We Made Claude Code Build Lovable in 75 Minutes” — an AI coding tool used to clone a competing AI coding tool. You can run that same search yourself.
Why “it’s free” doesn’t get creators off the hook There’s a legal instinct people reach for here: if I’m not charging for it, it’s not really stealing. It’s wrong, and worth correcting directly, because it’s the exact permission structure these videos are handing their audiences.
U.S. copyright law doesn’t carve out a “personal or non-commercial use is automatically fine” exemption. The relevant defense is fair use — a fact-specific four-factor test that weighs purpose, the nature of the original work, how much was used, and the effect on the original’s market. Publishing a free clone publicly and inviting others to copy it cuts against fair use, not for it, because it substitutes for the original in the market — arguably a more direct market harm than if he’d sold it.
Patent law is even less forgiving of the “just for personal use” theory: infringement under U.S. law doesn’t require a profit motive at all, only unauthorized making or using of a patented invention. The narrow “experimental use” defense courts have recognized is close to a dead letter — even university research has failed to qualify.
Most of what’s happening in these clone videos isn’t patent territory anyway — it’s copyright (copied code, design, layout), trademark/trade dress (replicated look-and-feel), and straightforward terms-of-service violations (like lifting another creator’s thumbnail without asking). But the legal reality across all of them is the same: distributing the copy, not profiting from it, is usually what triggers liability. “I gave it away for free” is not the defense creators seem to think it is.
What to do on either side of this If you’re building: build from your own spec, not someone else’s live product. A generic UX pattern — a login form, a settings page — is fair game. A named competitor’s signature workflow isn’t a template. It’s their IP.
If you’re the one getting cloned: document your build dates now, and if you’ve got something patent- or copyright-worthy, get it filed before it becomes someone’s 34-minute tutorial.
Vibe coding didn’t invent this problem. It just made copying fast enough that nobody stops to ask if they should.
I went and looked. OpenAI is a verified enterprise organization on Hugging Face — 135 team members, models hosted there, a dataset published that same week.
That’s not a locked door. That’s a tenant.
Nobody picked a lock. Somebody badged in.
And this isn’t new:
→ 2001 — a British man reached 97 U.S. military and NASA computers by scanning for blank administrator passwords. They called it “the biggest military hack of all time.” → 2023 — attackers walked into MGM Resorts by phoning the help desk. → 2026 — an AI reached a company it already held 135 seats inside.
Three “hacks.” Three open doors. The vocabulary keeps outrunning the intrusion.
Here’s the uncomfortable part: containment isn’t hard. chroot shipped in 1979 — six years before Sam Altman was born. gVisor, Firecracker microVMs, default-deny egress — commodity, documented, free. The test environment simply had a door to the open internet and a live credential sitting next to it.
We are running 2026 agents on 1998 authentication.
So here’s the gauntlet, @OpenAI / @Hugging Face: send us the logs. Free, public, one week. We’re a small shop in Orange County with no vendor to protect and no narrative to defend, and we’ll read them straight. You won’t — you don’t need to. The answer’s already on your own profile page.
Full four-page assessment attached — sent the only way that felt appropriate.
(Yes, it’s a fax. On purpose. It’s about as modern as the auth most AI companies are protecting their models with.)
You’re late, but the party’s just getting started. Here’s everything that leveled up this week.
Android, welcome. You waited long enough — and the crew’s been busy. Four brands, four moves, one ecosystem that protects and grows your business at the same time.
1. Citadel AI — Hello, Android. Secure the perimeter.
Your digital business card, referral network, and commission dashboard — all in one link.
GRYHAT — CMMC + AI: validated and proven.
Proof isn’t just in the dashboard — it’s on the podium. Our founder Andy Vaca is a featured speaker at Put Data First — Summer Bash 2026 (Lido House, Newport Beach · July 13–14), leading roundtables on:
Data Strategy for AI Success
The AI Handoff: Automated Discovery vs. Human Resolution
AI Governance in Practice
Scaling AI from Pilot to Production
Shadow AI Security Risks
The same thinking we bring to that stage is built into every product you just met.
2026 put data first summer bash roundtable topics copy
CTA (blog + email): Book a call. No pricing games — just a conversation.
On June 22, 2026, we got a message from Apple App Review. Not a bug report. Not a rejection over a screenshot. A notice that the government of Russia had ordered our app removed from its App Store.
Here’s what they wrote, word for word:
“We are writing to notify you that your application, per demand from Roskomnadzor, will be removed from the Russia App Store because it includes content that is illegal in Russia… According to Roskomnadzor, the app violates No. 7 of Article 15.1 of the Federal Law dated 27.07.2006 No. 149-FZ ‘On Information, Information Technologies and Information Protection’.”
Translated from bureaucrat: our VPN works, and a surveillance state would rather its citizens didn’t have it.
What actually happened
Roskomnadzor is Russia’s federal censorship and surveillance agency. Article 15.1 № 7 is the specific provision they use to block “information about means of circumventing” the country’s internet restrictions — in plain English, the law they point at VPNs.
Apple isn’t the villain here. They’re the messenger, legally compelled to comply with a government takedown order or lose access to the entire market. So the notice lands in our inbox, an “Unresolved issues” flag turns red in App Store Connect, and Citadel disappears from one storefront.
Let’s be honest about why
We’re not going to pretend Russia singled us out as uniquely uncrackable. Since 2024, Roskomnadzor has been systematically purging VPN and anti-censorship apps from the Russian App Store — dozens of them, one after another. We’re one more name on a long list.
But here’s the thing about that list: everyone on it shares a single trait. Their tools actually protect people. Citadel encrypts your traffic, hides your network activity, and flags the threats sitting on the WiFi around you. That’s precisely the capability a regime built on watching its citizens wants gone.
When the people whose entire job is surveillance decide your product is a problem, that’s not a setback. That’s product-market fit.
What it means for everyone else
Nothing changed for you. Citadel is still live in every other App Store territory. The removal applies to one country — the one country that decided privacy was against the rules.
We build everything cybersecurity-first. That’s the GRYHAT difference, and it’s why an authoritarian censor flagged us while millions of other apps sail through untouched. We’ll wear that.
Russia gave us a one-star takedown. We’re reading it as five stars.
A new dad gadget that isn’t a shotski — and it’s free.
Where we’ve been & something for the dads
⚡ Major Announcement ⚡
Hey There—
We’ve been quiet for a stretch. Not gone — heads down. We didn’t want to surface until we actually had something worth showing you.
Father’s Day weekend felt like the right time. So — happy Father’s Day.
If you’re a dad, you know the real job: you’re the one looking out for everybody else. So this is what we wanted to put in your pocket today — Citadel, a little app that quietly guards your phone and the WiFi your family hops onto. It’s free to download. And because it’s free, the protection you set up for yourself, your kids can have on their phones too. Feels like a dad thing.
That’s the one we wanted in your hands this weekend. But the quiet stretch wasn’t nothing — we’ve been building a small platform, four pieces finally coming together at once:
• Citadel — security that lives in your pocket.
• GRYHAT — where it all started: the crew that guards businesses for a living.
• ReferralGenius — the digital business card that refers you business.
Trillion-dollar infrastructure. The smartest systems ever built. And every time you open a new chat — it’s like meeting a stranger. Here’s why. And here’s how to fix it today.
—
Last week I wrote about lying to your AI — how feeding bad information into these systems, or letting wrong answers slide uncorrected, compounds into something worse than a single mistake. A lot of you responded. Most said some version of the same thing: *I didn’t realize I was doing that.*
This week I want to go one level deeper. Because before we can talk about the quality of what goes into these systems, we need to talk about the fact that most of what goes in — doesn’t stay.
—
All these trillion-dollar data centers. Servers the size of city blocks. The smartest computers ever built by human hands.
And yet — every single time you open a new chat, it’s like meeting a stranger.
We solved self-driving cars. We beat world champions at chess. We can generate a photo of anything you can imagine in four seconds flat.
But memory? Still working on it.
This isn’t a cynical take. I use these tools every single day and I believe in them. But part of believing in something is being honest about what it can’t do yet. And right now, AI can’t remember you. Not between sessions. Not without help.
Here’s why — and more importantly, here’s how to work around it today.
—
The whiteboard problem
Every AI conversation you have happens inside what’s called a context window. Think of it as a whiteboard.
The whiteboard is extraordinary. Within a session, it tracks everything — what you’ve said, what you’ve established, the corrections you’ve made, the context you’ve built. It can hold tens of thousands of words and work with all of it simultaneously.
But the second the session ends, someone erases it.
The next time you open a conversation, the AI has no idea who you are. It doesn’t remember your business. It doesn’t remember the three hours you spent last Tuesday getting it calibrated exactly right. It doesn’t remember the correction you gave it, the way you like things structured, or the client context you carefully walked it through.
It wakes up a stranger. Every time.
This is not a bug they forgot to fix. It’s not a feature coming in the next update. It’s an architectural reality of how these systems are built right now. The context window is not persistent memory. It never was.
So if you’ve ever felt like you’re going in circles with your AI — re-explaining the same things, getting inconsistent outputs, watching it drift away from the voice or style you spent time building — now you know why. And here’s the important part: it’s not the AI being difficult. It genuinely doesn’t know. You haven’t told it yet. This session.
—
Push back when it happens
Before we get to the fix, there’s something worth knowing about what to do in the moment.
If a conversation starts feeling repetitive — if the answers stop making sense, if you keep explaining the same thing and the AI keeps getting it wrong — don’t just keep prompting and hoping it self-corrects. It won’t. The context window is getting crowded and earlier instructions are getting pushed out. The AI doesn’t know it’s lost. It will confidently spin in the same direction until you redirect it.
The fix is simple but it takes nerve: call it out. Say “we’re going in circles — let me restate what I need.” Or start a fresh session with a clear briefing.
This is still the honesty principle from last week — just the other direction. Don’t lie to your AI. And don’t let your AI keep lying to you by going along with a broken thread just because you haven’t called it out.
—
The practical fix: how to give your AI memory today
Here’s what every serious team running AI agents has figured out — and what most businesses using AI casually haven’t discovered yet.
You build a briefing file.
It’s exactly what it sounds like. A plain text document that tells your AI everything it needs to know before the session starts. You load it at the beginning of every conversation and your AI picks up exactly where you left off — every time.
It takes about ten minutes to build the first version. It will save you hours.
What to put in your briefing file:
*Your business context*
Who you are, what you do, who your customers are, what problems you solve. Two or three paragraphs. Plain language. Don’t over-engineer it — write it the way you’d explain your business to a smart friend who’s never heard of you.
*Your voice and tone*
How you communicate. Formal or casual? Technical or plain English? Are there phrases you use all the time? Words you hate? Things you never say? Write them down. Your AI will use them.
*Current priorities*
What are you working on right now? What projects are active? What decisions are you trying to make? This is the part that changes week to week — update it when things shift.
*Rules and guardrails*
Things the AI should always do. Things it should never do. Clients it knows about. People it works with. Anything that would take time to re-explain if the AI forgot it.
*How to use it*
Open a new chat. Paste your briefing file. Say: “Read this before we do anything else. This is your context for our session.” Then work normally.
That’s it. Your AI now knows who you are, what you’re doing, and how you operate — for this session. Tomorrow, load it again. Same result.
—
Why context is the new skill nobody’s teaching
Here’s the thing most people miss. The AI tools are getting more powerful every month. Models are getting smarter. Features are being added. But the teams getting the most out of AI right now aren’t the ones with access to the best models.
They’re the ones who’ve figured out how to give those models context.
Context is the new skill. And almost nobody is teaching it.
When you load a briefing file, you’re not just saving time — you’re fundamentally changing the quality of what the AI can do for you. A well-briefed AI isn’t just faster. It’s more accurate, more consistent, more useful, and less likely to drift into outputs that sound right but miss the point.
The people who get this first — who build their briefing systems now, who treat AI context as a skill worth developing — are going to have a compounding advantage over everyone else who’s still re-explaining themselves every single session.
That’s not hype. It’s just arithmetic. Better inputs, better outputs, every time.
—
Where this is all going
The memory problem is being worked on. Native persistent memory is coming — some models already have early versions of it. The tools for long-term agent memory are improving faster than most people realize.
But we’re not there yet. Right now we’re in what I’ve started calling the duct tape era — a moment where the intelligence is extraordinary and the infrastructure around it is still catching up.
The briefing file is duct tape. Good duct tape. Duct tape that works. But it’s a workaround, not a solution.
Build it anyway. Use it now. And stay ready to migrate to something better when it arrives — because it’s coming.
Next week: what it actually costs to run AI agents in a real business. Not token costs. The half-days rebuilding what should have been saved. The drift nobody warns you about. The architecture work that doesn’t show up in any vendor’s sales deck.
*Andy Vaca is a 27-year Information systems veteran, vCISO, and founder of GRYHAT Cybersecurity LLC and YouFeelingLucky.com. Based in Orange County, California. He runs Friday night AI education sessions open to the public under the “Andy the AI Guy” brand.*
*Questions, pushback, or stories from the trenches: eva@gryhat.com*
So last Friday I showed up to teach a 2-hour AI class.
My AI had other plans.
Four hours later — four — people were STILL asking questions. I tried to wrap it up twice. The room wouldn’t let me. At some point I just accepted my fate and kept going.
Here’s what we covered before I lost all control of the situation:
🔥 The SonicWall demo — dropped a raw firewall log into AI, got back a board-ready security report in 60 seconds. The room went from polite to wide-eyed real fast.
📊 The BI dashboard breakdown — showed how AI can take your business data and turn it into something you can actually make decisions with. People went home with homework. Voluntarily.
🤷 The honest talk about what AI CAN’T do — this was apparently the most surprising part. Turns out people are starving for someone to just tell them the truth.
This Friday — Week 2. And somehow it’s already getting weirder.
Two weeks in and people are already volunteering to TEACH. I did not plan for this. I love it.
This Friday we’ve got a special guest teacher — an AI 3D animator — who is going to show us things that will make your brain do a little somersault. Real tools. Real workflow. Real “wait, AI can do THAT?!” energy.
Unexpected Course Extension: A 2-hour AI class unexpectedly turned into a four-hour session as participants kept asking questions, showing high engagement and curiosity.
Demonstration of AI Capabilities: The class featured a demo where AI analyzed a raw firewall log and produced a security report in 60 seconds, impressing attendees.
AI for Business Data Analysis: Participants learned how AI can transform business data into decision-making tools through a dashboard breakdown.
Honest Limitations of AI: The session included a candid talk about what AI cannot do, which was surprisingly the most appreciated part of the discussion.
Upcoming Week 2 and Guest Speaker: The next class will include a guest AI 3D animator who will showcase real tools and workflows, and the event will also launch new projects.
We’ll send you everything you need once you’re in.
Bring a friend. Bring snacks. Leave your preconceived notions at the door.
Everyone’s worried about AI getting things wrong. Nobody’s talking about the human on the other side of the keyboard. First, let’s fix the language. When AI produces a wrong answer, the media calls it a “hallucination.” That word is doing a lot of work to protect a lot of people. It implies the AI made something up from nothing — random, accidental, a glitch. That’s not what’s actually happening. What’s happening is confluence. The AI is pulling from multiple streams of real information, mixing them together, and producing an output that sounds completely grounded — because it is grounded, just in the wrong combination of things. It’s not random noise. It’s misattributed signal. And misattributed signal is far more dangerous than a hallucination because it passes the smell test. My own AI recently wrote an article about AI memory failures. Then got my name wrong in my own bio. It didn’t invent a name. It pulled a real name from real context in our history and attached it to the wrong person. Confident. Plausible. Wrong. That’s confluence, not hallucination. Now here’s the part nobody wants to hear. When you lie to your AI — or give it bad information, or steer it with a wrong premise, or confirm an output you know isn’t right because you’re in a hurry — you are deliberately adding contaminated streams to that confluence pool. You’re not just making a mistake. You’re poisoning the well on purpose. Here’s what people actually do every day: they feed their AI wrong context to get the answer they already wanted. They don’t correct it when it gets something wrong because fixing it feels like more work. They confirm bad output to avoid the friction of pushing back. They give lazy answers just to move the conversation along. And then they blame the AI when things drift. Your AI isn’t going to call you out. It doesn’t have ego. It takes what you give it and builds on top of it — intelligently, confidently, wrong. Feed it a bad foundation and it will construct something impressive on top of it. You built that. Not the AI. The relationship only works when both sides are honest. That’s not a technical principle. That’s just integrity. And the people who are going to get the most out of these tools aren’t the ones most impressed by them — they’re the ones most honest with them. Hold it to a standard. Hold yourself to the same one. You’ll get a better result
Andy Vaca | Founder, GRYHAT Cybersecurity / You Feeling Lucky? vCISO | AI Practitioner | 27 years in the security trenches
