News · October 17, 2026
Why Exotool apps do not leak their database: the client/server split
In 2025 a researcher scanned 1,645 apps built with one of the popular AI app builders and found 170 with their database tables open to anyone: e-mail addresses, home addresses, in some cases API keys. Nothing had been hacked. The apps were built the way the builder builds them, and a rule had been left off.
How the leak happens
A common design in AI and no-code builders is to let the app in the browser talk to its database directly. The browser holds a client key; every table is reachable from any user's device; and what stops one user from reading another's rows is a per-row policy on each table. The design is fast to generate, which is why models and builders like it. It is also one omission from public: a table created without its policy is readable by everyone who can open the app, and the browser's own developer tools show how. The scan above (CVE-2025-48757) found exactly that, 170 times. Bubble's own documentation says the same of its data types: one with no privacy rule is readable by everyone.
What Exotool does instead
Exotool's patented engine decides what runs on the device and what runs on the server, and generates the APIs between them. The database is addressed only from the generated server side. The browser never holds a database key; the device side gets only what the server side sends it, through APIs the engine made for that app and nothing else. There is no per-row rule to forget because the browser cannot reach a table in the first place.
If a value must never reach the device at all, you say so, and the engine keeps it on the server. If a statement must run on the server, if_on_server pins it there.
Why this matters more with AI
When a language model writes an app, it writes the plumbing too, and it writes it differently each time. The policy that guards a table is one more thing it may forget, and nobody reads thousands of generated lines to check. In Exotool the model, Claude through the Exotool connector, does not write the plumbing: it edits the diagram, the engine generates the rest the same way every time, and the diagram is what you read to see what was built.
The comparisons with Lovable, Bolt, FlutterFlow and Bubble state each tool's model of database access, as published by the vendor.