What changes in your live app when someone clicks Accept on a Lovable draft? Lovable's docs say accepting can change your live backend (the part that stores data and runs code) before you publish, with no database backup taken. Drafts are test copies of your app, and some share that live backend. Below: what a copy shares, and five checks.
Lovable builds websites and web apps from a chat, its pricing page says. Its changelog lists drafts from September 9: copies of your project where you can try a change before it reaches your visitors. A November 16 entry says a draft on the built-in backend (the part of an app that stores data and runs code on a server) "now has a backend of its own". Lovable's docs say the copy is not always fully separate: some drafts share your live backend, and accepting a draft can change it before you publish.
Imagine a client tries a change on a copy of your app, likes it, and someone clicks Accept. What just changed in production? Lovable's blog post of November 16, 2026 says "Nothing goes live until you accept a draft and hit publish." Its docs say "Accepting can change your live app's backend immediately, before you publish." The two pages differ in emphasis. We tested nothing; status as of November 17, 2026.
What changed in Lovable drafts, and when?
A draft is a copy of a project with its own chat, preview and edits, the docs say. You accept it to add its changes to your project, or delete it to discard them. Drafts are "available on all plans".
Lovable's changelog dates the first drafts entry September 9, 2026. It said drafts "share your project's data, so anything you add or change while testing is real". A November 16, 2026 entry says that on the built-in backend a draft "now has a backend of its own". The blog and docs we read print no stage label; the docs say own-backend drafts are "rolling out gradually", so your drafts "may share your live backend for now". They do not say who has them yet, or when the rollout ends.
Does a draft use a separate database?
A notice above the preview means the draft has its own backend, filled with example data. No notice means the draft shares your live backend, and what you add, change or delete "changes your live app too".
| Item (as the docs describe it) | Draft with its own backend | Draft that shares the live backend |
|---|---|---|
| Database structure (tables, columns, access rules) | A copy of the live app's structure | The live app's structure |
| Data you add, change or delete | Stays in the draft | Changes in the live app immediately; deleting the draft does not undo it |
| New tables and columns | Added to the draft's database, so you can test them in the preview | Added to the live database only when you accept; until then, pages that use them show an error in the preview |
Files in your project's Files tab (separate from app storage) are shared by the main version and every draft, the docs say, and changes there "save immediately".
The docs say a draft shares the live backend when your project uses your own Supabase project (the Supabase docs page describes "a Supabase project you own" that Lovable uses "as your app's backend"), or when Lovable cannot set one up: a paused or unavailable database, an extension outside its supported list, or a structure it cannot copy.
Accept versus publish: what changes when?
In short: pages wait for publish; the database structure does not. The docs say some of a draft's changes land when you accept; publishing is a separate step.
| Item | When you accept | When you publish |
|---|---|---|
| Pages and screens | Added to unpublished changes; visitors still see the previous version | Visitors see them |
| Database structure, such as new tables and columns | Changes in the live database immediately | No further change |
| Server code the draft changed (backend functions); file-storage settings too, for an own-backend draft | Deployed or changed in the live app immediately | No further change |
| The draft's rows, test accounts and files | Deleted with the draft; they never reach the live app | No change |
The docs say accepting "never copies data from the draft". For a draft that shares your live backend they also describe a rename, or a change to the kind of information a column stores, done by "adding a new column and copying the data over". In our reading, accepting brings in no rows from the draft, but a structure change can still involve rows already in your live database.
Until you publish, visitors still see the previous version of your app, but it already uses the new database structure and backend functions. A change that renames or removes something the old version uses "can break it", the docs say, and they advise publishing right after you accept.
Can you undo an accept?
The blog says that after you accept you can still roll back before you publish, through History. The docs add a limit. Lovable "doesn't take a backup of your database when it accepts a draft", and restoring an earlier version from version history restores code and backend functions, "but not your database". In our reading these are the same revert; neither page says so.
The docs advise exporting your database before you accept, and point to a daily backup to undo a structure change. The backup page says the built-in database is backed up once a day, "up to roughly 14 days" are kept, and you cannot take a backup on demand from that page. In our reading, accepting leaves no restore point of its own.
A few limits to know. "Restoring cannot be undone", data changed after the chosen backup is lost, and files in storage are not covered. On your own Supabase, backups are "Managed by you in Supabase". An export request is not yet a copy: Lovable emails you when it is ready, and you download and keep it elsewhere. A deleted draft cannot be brought back either: "The deleted draft can't be restored."
Who can accept a draft?
Anyone with edit access can accept any draft in the project, the docs say; people with view-only access cannot. They add that "accepting doesn't require anyone's approval" and suggest you "agree on who accepts drafts". A client who builds in a draft needs edit access, "which also lets them accept drafts". If the draft's chat does the accepting, Lovable asks for approval first "unless you've chosen to always allow accepting".
What should you check before you accept a draft?
Five checks, in our reading
Five checks for an owner or team lead. They are our suggestions, in our reading, not Lovable's advice and not legal advice. We do not advise anyone to use the feature or to avoid it.
- Look at the preview before you touch any data: a notice above it means the draft has its own backend; no notice means it shares your live one.
- Before you accept, find out which backup your backend has: the built-in database has a daily backup; a project on your own Supabase is backed up in Supabase. Export your database, as the docs advise, wait for Lovable's email that it is ready, and keep the file outside Lovable (the export does not include files in storage). Then ask Lovable in the draft's chat to explain what will change, especially anything it renames or removes.
- Agree who may accept, before you give a teammate or client edit access. The docs say anyone with edit access can accept any draft, with no one's approval. In our reading, a confirmation prompt for the person who clicks is not a review by a second person.
- Publish right after you accept, as the docs advise, so the live pages and the new database structure match.
- Before copying real records into a draft, read the Terms section below, including the No Sensitive Data clause, leave out personal details you do not need, and ask Lovable in writing what its Terms and Privacy Policy mean for those records. Ask your counsel about the rest.
Are emails and payments in a draft real?
In both kinds of draft, the docs say, stored keys and connected services use their live values, so an API call from a draft is real, and "so is an email your app sends through a connected service". Built-in payments run in test mode; "With your own Stripe account and a live key, the payment is real." A payment confirmation goes to your live app, so "a checkout you test in a draft never completes there". Emails sent through Lovable's built-in email sending are not sent from a draft, except sign-in emails.
To test with real records, the docs say you ask Lovable in the draft's chat to copy them. Lovable "asks you before it copies people's names, email addresses, or other personal details". It adds the copied rows to the project's example data file, db/seed.sql, so every new draft starts with them after you accept.
What does a draft cost?
Creating, updating, accepting and deleting a draft "don't use credits", the docs say. Messages you send in a draft "cost the same as messages in the main version". The credits and drafts docs print no price for drafts and do not say how a draft's own backend is counted. A project can hold "up to 500 open drafts at a time"; accepted or deleted drafts do not count.
Lovable's pricing page (undated) lists Pro at "$25 / month" and Business at "$50 / month" on its Monthly view, each with "100 monthly credits". On Yearly it lists $21 and $42 "/ month, billed annually". A further line, "100 Pro credits" or "100 Business credits", is not explained, so we do not add it to the monthly credits; the page's FAQ says credits "are not necessarily equal in value across different plans", so we do not compare the plans.
What do the Terms and Privacy Policy say about data in a copy?
Lovable's Terms (last updated August 28, 2026) say you grant Lovable a "worldwide, perpetual" license to use your Customer Data for its business purposes, and that Lovable may use it to "develop and train artificial intelligence and machine learning models". You may tell Lovable you do not want that, and it will "honor that request for prospective use". That clause names no form or setting; the Terms list a support email address for notices.
Lovable's Privacy Policy (last updated September 15, 2026) and training-data docs add limits. The docs say customer data from Free and Pro plans may be used for training unless the user opts out, and that Lovable does not use your apps' end-user data, your account and billing details, or Business and Enterprise workspace data for training. For Free and Pro, the docs name the opt-out: Account settings, then Preferences, then AI model training. It applies going forward and does not remove content from datasets assembled earlier.
The Terms say the Privacy Policy "governs and prevails" over this section in a conflict. The Terms do not mention drafts, and we did not find on these pages how rows copied into a draft's example data file are classified.
A second clause matters if you copy real rows into a draft. Under "No Sensitive Data", the Terms say you agree not to provide health information subject to HIPAA or other sensitive data (including "financial account numbers, payment card data, government identifiers, or biometric data"), unless your plan or a written agreement permits it.
The Terms cap Lovable's total liability at what you paid it in the twelve months before the claim, except where law does not allow a cap. We do not interpret these words. We are not lawyers; ask your counsel.
On November 17, 2026 we read the ten pages under Sources, between 13:26 and about 13:58 PST (pricing in a browser). The docs and pricing pages print no date on the page. We did not read the data processing terms, the Enterprise terms or the trust center, and make no claim about them.
Read next
The November 16 Replit teardown (who approves the spend), our Copilot cloud agents teardown and why AI-built software needs staging, approval steps and a rollback plan. The November 17 Signal / Noise and the teardowns hub.
Need written rules for who may change what? AI agent development.
Sources
- Lovable blog: Now you can explore any idea in parallel without touching what's live ("Published November 16, 2026"), read November 17, 2026
- Lovable docs: Explore changes with drafts (no date printed), read November 17, 2026
- Lovable changelog (entries "Sep 9, 2026" and "Nov 16, 2026"), read November 17, 2026
- Lovable pricing (undated; Monthly and Yearly views and credit-size dropdowns read in a browser), read November 17, 2026
- Lovable Terms of Service ("Last Updated: August 28, 2026"; "Effective Date*: August 15, 2026"), read November 17, 2026
- Lovable Privacy Policy ("Last Updated: September 15th, 2026"), read November 17, 2026
- Lovable docs: Manage training data and privacy (no date printed), read November 17, 2026
- Lovable docs: Back up, restore, and export your project's database (no date printed), read November 17, 2026
- Lovable docs: Supabase integration (no date printed), read November 17, 2026
- Lovable docs: Credits and usage (no date printed), read November 17, 2026