Horror Story: $1,000+ and 1,000 hours building on Lovable—they just wiped my entire database and locked me out with no warning or proof

I’ve been a top 10% Lovable builder for the past 6 months. I’ve burned through well over $1,000 in credits and poured roughly 1,000 hours into building an application where the entire core product *is* the database.

Yesterday, they completely locked my project out: front end, back end, all of it!

Because I was using their hosted Supabase instance, I have zero access to my 12GB of proprietary data. It’s hostage.

Here is the current state of "support" when you build on Lovable:

* **Appeal form:** Filled out 24+ hours ago. Zero response. * **Direct Tweets:** DMed multiple founders directly. Dead silence. * **Public Tweets:** Tagged [u/Lovable](https://www.reddit.com/user/Lovable/). Radio silence. * **Support:** Just an AI support bot running in circles.

It is one thing to lean heavily on AI support for basic troubleshooting. It is a completely different nightmare when an automated AI "trust and safety" flag can instantly nuke a paying user's account, steal their data, and leave them with literally no appeal path.

**To anyone currently considering Lovable: Be extremely cautious.**

I was actively considering an enterprise contract at work with them. Knowing they can nuke any paying customer's account and you get no recourse, there's no way in hell I would ever recommend that for an enterprise.

**My advice:** Build using Cursor, Codex, CC, etc. Its cheaper anyway. Keep your Supabase (or any database) on your *own* self-hosted/independent infrastructure from day one. Do not trust them with your data hosting. Luckily I didn't lose source code because I had GitHub connected but I wasn't as wise with the database.

**Update:** 4 days later, Lovable got back to me after I started blowing up every Linkedin post they made with a comment similar to above. Project is back now. Their response was pathetic:

"I’m sorry for the repeated disruption and the impact on your business.

Your project URL was reported again for potential impersonation, which prompted a precautionary review. Reports involving similarities in names or concepts may require human review to confirm that a project complies with our policies and does not impersonate another organization.

The review found that there was no basis to keep the project blocked. Access has now been restored."