An interesting detail missing here is that there are two types of scans: “quick scans” and “deep scans.” Quick scans run automatically whenever a user publishes a project, while deep scans must be triggered manually -- except for enterprise customers.
Although already mentioned in the research report, the following links show that Lovable explicitly targets non-technical customers, stating that no technical expertise is required:
This fundamentally changes the startup equation:
- No need to convince a developer to join before validation.
- No delays from back-and-forth translation between business and tech.
- Immediate product iterations, turning feedback into new features
within hours.
With Lovable, non-technical founders cut months of friction and focus
entirely on product-market fit, rather than struggling to find a
development team.
All you need to kick off your vibe coding journey is an AI-powered
no-code builder (like Lovable). As long as you can describe what
you're looking to build, you can build it.
# AI Output
The Services may use artificial intelligence models to
generate code, content, or other outputs ("AI Output").
AI Output may contain errors, inaccuracies, or other
issues and should not be relied upon without
independent review and testing. You are solely
responsible for reviewing, validating, and using any
AI Output, whether it is generated through:
- our Platform's integrated AI;
- the AI Gateway (via Third-Party AI Providers); or
- any model or API that you connect to the Services.
I've never used lovable; do they have any sort of human-approval gate step between (or around) generating an app and deployment/availability? INAL but I wonder if that would CYA for responsibility of releasing bad code created by their AI...
To clarify: no PII leaked from Lovable apps ended up in Common Crawl. Common Crawl was used solely to identify Lovable apps—not to retrieve leaked data. It does not store XHR responses, which are how data is retrieved from Supabase.
Any data fetched during the analysis was deleted long ago, though you’ll have to take my word for that. Only metadata was retained.
That said, I fully agree that no one can say for certain whether anyone else collected this data or what happened to it afterward.
Each psychotic vibecoder making 50 slop projects on an account. Also probably counting demo projects. Idk, if I had to bet against any company it would be lovable.
But they have tons of VC money so they'll get aquired by someone in the incestuous circle of SV investors.
The analysis was conducted with the assistance of a lawyer specializing in data protection. A deliberate decision was made to share the dataset with Lovable so they could contact their customers and have the database access issues resolved.
1. The website owners should be informed so they can investigate how many of their customers are affected, notify them of the leak, and report it to the relevant authorities. However, we did not necessarily have their contact details or another way to reach them.
2. Sending thousands of emails to the leaked addresses could further expose that data, as the addresses would then be stored in our email client, on the mail server, and elsewhere. We would have needed to automate this, meaning a service like Mailgun would also receive the data. There was also a significant risk that these emails would end up in spam.
3. The most responsible path forward seemed to be sharing the website URLs and some metadata with Lovable, allowing them to contact the website owners through the appropriate channels.
IANAL, but I've had several hosting companies. And while most situations where a customers' site is hacked and/or their data leaked, is clear and not the hosters' responsibility. That hoster does have an obligation to provide good tooling (i.e. ssh, not telnet, sftp, not ftp) and to promote good behaviour (i.e. not allowing the backup system to write the backups to public hosted directories). Or else can be held (partially) responsible for breaches.
Lovable has a responsibility, and, as you pointed out in your article, their proposition of "building apps without technical knowledge" (my words), might make theirs to be more than just putting lines in a EULA to waver that responsibility.
Sorry, I was flippant in my previous comment -- they SAY they can’t be sued. I’d hope those “non-technical founders” wouldn’t be left out in the cold and that Lovable would be held liable as well.
That's not a run race. They are a processor and this definitely was on their watch. Both controller (the website owner) and the processor and sub-processor (Lovable, Supabase) all have pretty clear joint and individual responsibilities here and all of them have failed to greater or lesser degree. The Controller may even be in the better position of the three.
https://docs.lovable.dev/features/security#built-in-security...
reply