What Happens When Your AI Provider Locks You Out Overnight?
A retired tech consultant recently shared on LinkedIn that his ChatGPT account was compromised, then deactivated by OpenAI with no route to appeal. Gone. Not just the chatbot. Every document, every project, every prompt thread he had stored inside the platform's web app.
He was fortunate. Many of his most critical projects had been built using the desktop application, which meant files lived locally on his own machine. Without that, he said he could have lost years of work overnight.
The post gained serious traction. Hundreds of reactions. Over a hundred comments. And then, after all that public attention, OpenAI reversed course. They sent him an email admitting the deactivation was a mistake and apologizing for the inconvenience.
He got his access back. But only because his post went viral.
Let that sit for a minute.
This Is Not Somebody Else's Problem
If you are a property manager, a regional, a marketing director, or an owner-operator using AI tools to run your business, you need to ask yourself a very uncomfortable question: What would you lose tomorrow if your AI provider shut off your access today?
Not hypothetically. Literally.
Think about what you have built inside these platforms. Custom instructions tuned to your brand voice. Months of prompt history that represents how you think through lease-up strategy, resident communications, market surveys, job descriptions, training content. Projects. Uploaded documents. Entire workflows.
Now think about the fact that none of it belongs to you in the way a file on your desktop belongs to you. It lives on someone else's servers, governed by someone else's terms of service, and subject to someone else's enforcement decisions.
The Risk Is Real and It Is Growing
This is not fear-mongering. This is infrastructure planning.
As our industry moves deeper into AI adoption, the volume of institutional knowledge being deposited into third-party platforms is accelerating. Leasing scripts. Maintenance communication templates. Marketing calendars. Training curricula. Competitive analysis. Budget narratives.
Every one of those represents operational value. And every one of those is vulnerable if you have no continuity plan.
The triggers for losing access are not limited to account compromises. Terms of service violations (real or perceived), billing disputes, platform policy changes, or even simple technical errors can result in suspension. As we just saw, sometimes the provider gets it wrong and admits it. But the reversal only happened because a viral LinkedIn post forced the issue. Most people do not have that leverage.
Five Steps You Can Take Right Now
You do not need to be a technologist to protect yourself. You need to be intentional.
Every major AI platform offers some form of data export. Use it. Set a recurring calendar reminder. Monthly at minimum. Weekly if you are building anything substantial inside the platform.
Do not assume the export will be seamless or complete. Test it. Open the exported files and confirm the content is actually usable outside the platform.
If you upload a property's operating budget, a brand guide, or a set of standard operating procedures into an AI tool, that upload should be a copy, not the original. Your source of truth should always live somewhere you control: your own drive, your own server, your company's document management system.
This sounds obvious. It is not how most people are working. Many teams are uploading files directly into AI platforms and never keeping a separate version.
If you have spent weeks refining the custom instructions, personas, or system prompts that make your AI tools perform the way your business needs, those instructions are intellectual property. Copy them out. Store them in a text file, a shared document, a knowledge base. Somewhere that does not depend on the platform continuing to grant you access.
The best protection against vendor lock-in is refusing to be locked in. Structure your AI workflows so the outputs (not just the prompts, but the actual deliverables) are saved in standard formats in locations you control. If your entire marketing operation depends on a single AI platform's project feature, you have a single point of failure.
Ask yourself: If I lost access to my primary AI tool at 8 AM on a Monday morning, could my team still operate by Wednesday? If the answer is no, you have work to do. Identify which functions depend on AI, which of those are time-sensitive, and what your manual fallback is for each one.
This does not mean abandoning AI. It means treating AI tools the way you treat any other piece of critical infrastructure. You would not run a property without a backup generator plan. Do not run your operations without an AI continuity plan.
Start Here: Export What You Have Built
If you use ChatGPT and have built up custom instructions, preferences, or project context inside the platform, here is a prompt you can paste into a new conversation right now to pull all of it out into a format you can save locally. This is your Step 1 and Step 3 in a single action.
Export all of my stored memories and any context you've learned about me from past conversations. Preserve my words verbatim where possible, especially for instructions and preferences. ## Categories (output in this order): 1. Instructions: Rules I've explicitly asked you to follow going forward — tone, format, style, "always do X", "never do Y", and corrections to your behavior. Only include rules from stored memories, not from conversations. 2. Identity: Name, age, location, education, family, relationships, languages, and personal interests. 3. Career: Current and past roles, companies, and general skill areas. 4. Projects: Projects I meaningfully built or committed to. Ideally ONE entry per project. Include what it does, current status, and any key decisions. Use the project name or a short descriptor as the first words of the entry. 5. Preferences: Opinions, tastes, and working-style preferences that apply broadly. ## Format: Use section headers for each category. Within each category, list one entry per line, sorted by oldest date first. Format each line as: [YYYY-MM-DD] - Entry content here. If no date is known, use [unknown] instead. ## Output: - Wrap the entire export in a single code block for easy copying. - After the code block, state whether this is the complete set or if more remain.
Save the output to a document you control. A simple text file on your desktop or a note in your company's shared drive is enough. The point is that it exists somewhere that does not depend on OpenAI continuing to grant you access.
A note on other platforms: This prompt is written for ChatGPT's memory feature. Claude, Gemini, and Copilot each handle stored context differently, and their export mechanisms vary. Check each platform's current settings and data export options directly. The principle is the same across all of them: if you built it inside the platform, pull a copy out.
The Bigger Lesson
AI platforms are tools. Powerful tools. Tools that are transforming how we operate in multifamily housing. But they are not yours. The servers are not yours. The terms of service are not written in your favor. The enforcement decisions are not subject to your approval.
For anything important, keep your own copy somewhere you control. That is not pessimism. That is professionalism.
Build with AI. Build boldly. But build with a backup plan, because the platform you depend on today does not owe you access tomorrow.
Tami Siewruk is the Founder and CEO of mPro Digital Edge and creator of the Multifamily NEXT AI education conference tour. She writes and speaks on responsible AI adoption in the multifamily housing industry.
