Lovable apps left passport data and 200K+ private messages exposed online
By AI Update World · 2026-11-14

The way software gets built has changed radically over the past decade. Where developers once had to write thousands of lines of code by hand, they can now use platforms that let them assemble applications visually, with fewer or no traditional coding skills required. This shift has opened software development to millions of new people, but it has also created a parallel set of technical and security considerations that deserve serious attention.
What no code platforms actually are
No code and low code platforms are development environments where users build applications primarily through graphical interfaces, drag and drop interactions, and configuration rather than writing code. A user might click to connect a database, drag a form element onto a canvas, set conditions visually, and deploy a working application without ever touching a command line. The platforms themselves run on cloud infrastructure and handle much of the underlying technical infrastructure that a traditional developer would have to build and manage manually.
The convenience abstraction layer
What makes these platforms appealing is genuine and real. Traditional software development requires specialists who understand databases, security protocols, server architecture, API design, and dozens of other technical domains. No code platforms attempt to abstract away those complexities by making decisions on behalf of the builder. When someone uses a no code tool, they are essentially trusting the platform's creators to have made secure and sensible choices about how data moves, where it gets stored, and how authentication works. This abstraction layer solves a real problem: it democratizes the ability to build. But abstraction, by its nature, can obscure what is actually happening underneath.
How conventional software risks still apply
The fundamental logic of security vulnerabilities has not changed. Databases can be misconfigured. Access controls can be set too permissively. Data can be left unencrypted. API endpoints can expose information they should not. Credentials can be left in plain text. These are not new problems. They are problems that have existed since the earliest days of networked computing. A no code platform does not eliminate these categories of risk; it simply changes who is responsible for managing them and where the configuration choices happen.
The responsibility question
When a developer writes code, they are making explicit decisions about how data flows and who can access it. Those decisions are visible in the code itself. When someone uses a no code platform, many of those decisions are made by the platform's interface and defaults. This creates a critical ambiguity: a builder might not realize that a particular setting or configuration choice is exposing data. The platform itself might not make it immediately obvious. The creators of the platform are handling some security concerns automatically, but they cannot handle the configuration choices th