Base44 can train AI on your app data. What do I do now?
Since June 21, 2026, Base44's terms give it a license over the content you put into the platform that includes training its AI models, and its privacy page says data on every plan except Enterprise can be used that way. There is no setting to turn it off. The only exclusion Base44 offers is the Enterprise plan.
What to do now depends on what is in your app. If it holds other people's personal information, your own source code, or anything a customer would not want in a model, the first step today is a full export, and the second is a decision: pay for Enterprise, accept the terms, or move the app to an account in your name.
Moving is real work, but it is bounded work, and this is a reasonable moment to do it. Below is what the terms say, what each option costs you in practice, and the order a move goes in so your customers keep working while it happens.
In founders’ words
“On non-Enterprise plans, customer content may be used for AI-model training. That caught me completely off guard.”
“On one hand, the control you feel over software built on your own infrastructure is incredible. Changes feel more effective, fixes feel more solid.”
What changed, in Base44's own words
Base44 published a summary of its new terms, effective June 21, 2026. The terms page itself is marked last updated June 22, 2026. The summary says Base44 made 'some changes to the license to better support our ability to provide our service to you, including by using and training AI models', that the new terms let it 'use certain content you create for promotional purposes', and that 'you are responsible for exporting your data before your subscription ends'.
The terms themselves (section 4.2) grant Base44 and its service providers 'an irrevocable, non-exclusive, worldwide, royalty-free, perpetual, fully paid, sub-licensable right and license' over Customer Data and generated output, for a list of purposes that includes 'train Company software tools (e.g. artificial intelligence and machine learning models)'. Base44 is operated by Wix.com Ltd.
The privacy page is the plainest statement. On Enterprise, 'your data is not used to train AI models'. On all other plans, 'your data can be used to train AI models'. And: 'There is no opt-out setting to find or switch on.' The Enterprise exclusion covers the whole workspace, 'including personal information that people submit through your app's forms'.
Sources: docs.base44.com/Community-and-support/terms-of-service-update-june-2026, base44.com/terms-of-service, docs.base44.com/Community-and-support/Privacy-and-security, all read on October 2, 2026.
What it means for your app and your customers' data
Customer Data in Base44's terms is broad. In practice it covers the prompts you typed, the code the builder wrote, the records in your tables, the files people uploaded, and whatever your app's users entered into forms. The privacy page's note about form submissions is the part that matters if your app holds other people's information: on a non-Enterprise plan, what your customers type into your app is inside the training license.
Two more things sit beside the training question. Base44's servers are in the United States by default; Elite and Enterprise workspaces can choose EU or UK storage, but only for apps created after April 16, 2026. And Base44 names Anthropic, Google and OpenAI as the AI providers behind the builder, each under its own terms.
We are not lawyers, and what these words mean for your business is a question for one. What we can tell you is what to read (the three pages above and the privacy policy linked from them) and what to ask Base44 in writing: whether content uploaded before June 21, 2026 is covered, whether the license ends when the subscription ends, and which plan excludes your workspace from training and from what date.
Your options, honestly
There are three, and each is a fair choice for some apps.
- Stay on your current plan. Reasonable if the app holds no personal data, no trade secrets, and no customer has asked where their data goes. Export anyway, so the choice stays yours.
- Move to Enterprise. This is the only exclusion Base44 offers, and it applies to the whole workspace automatically. Ask for the exclusion in writing, with the start date, and ask whether earlier content is covered. Enterprise and Elite also unlock EU or UK storage for new apps and longer backups.
- Move the app to an account you own. Your code goes to GitHub, your data to a database in your name, your files to your own storage, your users to a login service you control. Base44 then holds nothing of yours. This is the option the rest of this page is about.
Why this can be a good moment to move
A terms change forces the question most founders put off: who holds the app. On Base44 the answer is Base44, for the database, the login, the files, the secrets and the backend that runs it all. On infrastructure you own (an AWS or Google Cloud account in your name, a small server, or Cloudflare), the answer is you. Nobody can change the terms under your data, the bill is for what you use, and a customer's privacy review gets a straight answer about where their records live.
The cost is that each job Base44 was doing becomes your job: hosting, backups, login, file storage, monitoring. None of them is hard on its own. The trap is doing them in the wrong order or switching before the new app has run on real data. With someone who has done it before, a Base44 app of ordinary size is a few weeks of careful work, not a rewrite. That is what our free call is for: we read the app and tell you what a move would take, and whether you need one.
What a move involves, step by step
Keep the Base44 app live until the new one has run clean for a while. The order below keeps customers working throughout.
- Code. Connect GitHub (Builder plan or higher) or download the zip. The export is a standard React frontend plus the backend function files and the table definitions. It still calls Base44 for every login and database read, so this is a copy, not a working app yet.
- Database and files. Table records come out as CSV; on Elite and Enterprise the Backup & Restore tab keeps 7 or 30 days of snapshots. Uploaded files are not in any export and app users are not in backups, so download the files yourself and keep the user list with emails and roles. Create a PostgreSQL database in your own account, recreate the tables from the schemas, import the CSVs.
- Sign-in and users. Passwords do not export. Set up a managed login service (Auth0, Clerk, Supabase Auth or similar) and send users a reset link; write that email before you need it.
- Secrets. Every API key, webhook secret and token gets re-entered in the new host's settings. Rotate anything that was ever pasted into a prompt.
- Payments. If you take money, the Stripe account is already yours; what moves is the webhook address and the code that handles it. Test a real card in test mode before switching.
- Domains and email. Point the domain at the new host only after everything below passes. Transactional email (confirmations, resets) needs a sender you own; set it up early because DNS takes time.
- AI providers. Base44's builder called Anthropic, Google and OpenAI on your behalf. If your app calls a model at runtime, it now calls one on your own key, under terms you chose.
- Rewrite the data calls. The backend functions and the frontend use Base44's kit to read and write. Each call becomes a call to your database and your login service. This is the largest step and the one where a coding agent earns its keep, provided someone reviews what it writes.
- Test before switching. Run both apps side by side on a copy of the data, click through every money flow as a new user, move a few friendly customers, then switch the domain.
Nothing on this list is exotic. It is the same set of parts every web app has, and once they are in your name they stay there.
When you may not need to move
If the app is a prototype, an internal tool with no customer data, or a side project with no revenue, an export in hand and a note in your calendar to re-read the terms is enough. Base44 is doing several jobs for you, and leaving means doing them yourself.
Move when a customer asks where their data lives, when the app holds information you would not want in a model, when you need EU or UK storage on a plan that does not offer it, or when you have already decided the product has outgrown what the platform lets you change. In each of those cases the export is step one, and the steps above are the rest.
| Concern | Stay on a standard plan | Move to Enterprise | Move to your own account |
|---|---|---|---|
| AI training on your content | Allowed by the terms; no opt-out setting | Excluded for the whole workspace, automatically | Not a question; nobody else holds the content |
| Your users' form submissions | Inside the license | Inside the exclusion | In a database you own |
| Where data is stored | United States | US, or EU/UK for apps created after April 16, 2026 | The region you pick |
| Backups | Check your plan's Data tab | 30 days of table snapshots (Elite: 7) | Whatever you set up; your job to keep |
| Hosting, login, files | Done for you | Done for you | Yours to run |
| Effort this month | Export and read the terms | A sales conversation and a contract | A few weeks of staged work |
Questions
Can I opt out of AI training on Base44 without Enterprise?
Base44's privacy page says no: 'There is no opt-out setting to find or switch on.' The exclusion applies automatically on Enterprise and on no other plan. Ask Base44 in writing if you want that confirmed for your workspace.
Does the license cover data I uploaded before June 21, 2026?
The terms do not say so in a way we can summarize safely, and we are not lawyers. Ask Base44 in writing whether earlier content is covered and whether the license ends when your subscription does, and show the answer to someone qualified.
If I delete my app, is the data gone from Base44?
Base44's summary says you are responsible for exporting before your subscription ends. What is kept afterward is a question for Base44's privacy policy and support, so ask before you delete, and export first either way.
Can I keep building on Base44 and move only the data?
Partly. The exported frontend talks to Base44 through its kit, so each data call has to be rewritten to use your database. You can do it one table at a time with both running, which is often the safest route for an app that already has users.
How long does a move off Base44 take?
For an app of ordinary size with one database and a login, a few weeks of staged work with the old app still live. The largest step is rewriting the data calls; the riskiest is switching the domain before testing on real data. Our free call tells you where your app sits on that range.
First look, $750. After a free call, we read your whole product and tell you what is finished, what is not, and what to do first.
Setup, $3,000 fixed. We make it ready for real customers, in accounts you own.
Partner, $2,500 a month. We review what your coding agent writes and keep the checks and tests current. Month to month.