Is Lovable Secure? What Our Two-Account Access-Control Test Found

By the PrototypeVerdict Test Team

Is Lovable secure? In our one hands-on test, a Lovable Pro client portal kept two signed-in accounts apart in everything we could check through the app’s interface. A second client could not see the first client’s record or file, had no Admin link, and was sent back to their own portal when they typed the admin address. A signed-out visitor was sent to the sign-in page. That is 8 of 10 checks passed, all UI-only. The other 2 checks, T2-06 and T2-08, are UNMEASURED: we did not test direct record or document URLs, or the app’s REST or storage API outside the interface.

This page reports a single run. It is not a penetration test, a compliance review, or a verdict on every Lovable app. To check your own app before launch, use the vibe coding security checklist and our browser-only security check.

The short answer

What we tested Can one signed-in client see or change another client’s records? One unpublished Lovable Pro client portal, two fake accounts, fake data only
Result 8 PASS, all UI-only (T2-01 to T2-05, T2-07, T2-09, T2-10)
Not measured T2-06 (guessable record URL) and T2-08 (signed-out record or document URL): UNMEASURED. No direct REST or storage API requests outside the UI
Setup we changed Auto-confirm email turned ON in Lovable Cloud; admin role assigned by hand in public.user_roles. No prompt changed the app’s access rules
Mobile Lovable’s mobile preview at 393 CSS px. 390 px was not tested
What it does not prove That the database refuses direct requests, that a published app behaves the same, or anything about other AI app builders

What Lovable says it does

Lovable’s own claims, not part of our test

  • Certifications: Lovable’s compliance post says it has a SOC 2 Type II report and ISO 27001:2022 certification. The same post says these cover Lovable as a vendor, not the apps you build with it.
  • Quick scan on every publish: Lovable’s security docs say a Quick scan runs automatically every time you publish. It checks your database access rules (for example, tables without row-level security), known vulnerabilities in your npm dependencies, and any MCP server your app exposes without sign-in.
  • Deep scan on demand: the same docs say a Deep scan reviews all of your app’s code for problems such as users reaching data that isn’t theirs, endpoints anyone can trigger, unsafe input, leaked secrets and sign-in checks an attacker could bypass. It doesn’t run automatically as you work: you start it from the project’s Security view, the workspace Security center or the project chat.
  • The limit: Lovable says the scans “cannot guarantee complete security” and that you are responsible for making sure your app meets the security needs of its use case.

Past incident: In April 2026, The Stack reported that a security researcher said they could access other customers’ source code, database credentials and AI chat histories from a free Lovable account. Lovable said a change to its backend permissions had accidentally re-enabled access to chats on public projects, and that it reverted the change. Lovable’s own write-up says private projects and Lovable Cloud were never impacted. Our two-account test checked the app’s own access controls, not Lovable’s project visibility settings.

How we ran the two-account test

We used an unpublished copy of our standard client intake portal, the first of the three builds described in how we test. Lovable built it from our usual prompt before this test. For this test we sent no build prompts, edited no app code, did not publish the app, and invited no real people.

  • Account A (admin and first client) submitted a fake record, PV T2 Alpha LLC, with a tiny synthetic image file attached.
  • Account B (second client) started with no records and later submitted its own fake record, PV T2 Beta LLC.
  • The app has three paths that matter here: /portal (a client’s own submissions), /admin (all submissions, staff only) and /auth (sign in).

Two setup steps were needed to get two working accounts, and both affect how you should read the results:

  1. Auto-confirm email was turned ON. The app’s sign-up required a confirmed email, and our test accounts could not sign in until it was confirmed. We switched Auto-confirm email ON in Lovable Cloud under Users → Email settings for this run. If you publish a real app, decide on purpose whether email confirmation stays on.
  2. The admin role was assigned by hand. We gave Account A the admin role directly in the app’s public.user_roles table (in its Lovable Cloud database), with no prompt and no code change. We did not ask the AI to change who is an admin or to loosen any access rule.

Mobile checks used Lovable’s mobile preview, which measured 393 CSS px wide. 390 px was not tested.

Results: 10 checks, one run

Each check is from the same session on the same app. “UI-only” means we judged it by what the app’s screens showed and where it redirected, not by sending requests to the database or file storage directly.

Check What we tried Result What we saw and the limits
T2-01 B’s portal shows only B’s records PASS (UI-only) B saw “No submissions yet”, then only Beta. Alpha and A’s file never appeared. In the 393 CSS px frame the submissions list sits below the fold, so this rests on the desktop view.
T2-02 B cannot reach the admin list from the menu PASS (UI-only) B’s menu showed only “My intake” and “Sign out”, with no Admin link, on desktop and at 393 CSS px.
T2-03 B types the admin address directly PASS (UI-only) Opening /admin as B redirected to /portal. No all-submissions table; desktop showed only Beta. At 393 CSS px the path was /portal, with the list below the fold.
T2-04 B cannot change A’s record PASS (UI-only) B had no control over A’s record because it never appeared. Afterwards, Alpha was still “New” with the same notes and file. API not tested.
T2-05 B cannot download A’s document PASS (UI-only) A’s file was not shown in B’s interface, and B had no download control for it. No document URL was exposed. Storage API not tested.
T2-06 B opens A’s record by a guessable URL UNMEASURED No record ID appeared in any URL or link, so there was nothing to try. We did not guess IDs at scale. This is not a pass.
T2-07 A signed-out visitor opens the admin address PASS (UI-only) Signed out, /admin redirected to /auth: an empty sign-in form and no records, on desktop and at 393 CSS px.
T2-08 A signed-out visitor opens a record or document URL UNMEASURED The interface exposed no public record or document URL to try while signed out, and we did not probe the REST or storage API directly. This is not a pass.
T2-09 The admin still sees everything afterwards PASS (UI-only) Back as A on /admin: “2 total · 2 new”, with Alpha and Beta both still “New”. No data lost.
T2-10 B still cannot see A’s data later in the session PASS (UI-only) B’s portal views in this session never showed Alpha. We did not keep a separate screenshot of B reloading after T2-09.

Why “UI-only” matters

A redirect away from /admin and a missing Admin link are good signs, but they are what the app’s screens do. They don’t by themselves show that the database would refuse a direct request from Account B. In apps like this, that protection comes from database access rules (row-level security) and server-side checks. Our security checklist explains them. We did not test that layer in this run, so T2-06 and T2-08 stay UNMEASURED and none of the passes above should be read as an API result.

What this test does and does not tell you

So, is Lovable safe for real client data? This run alone can’t answer that, and it is not a full Lovable security review. Here is what it does and doesn’t cover:

  • It is one run on one app. A different prompt, a later edit or a new feature can change an app’s access rules. Re-test after changes.
  • The app was unpublished. We tested in Lovable’s preview with our setup changes (Auto-confirm email ON, admin set in public.user_roles). We did not test a published app on a live URL.
  • It is not about vibe coding in general. Base44 is UNMEASURED on all ten checks (T2-01 to T2-10): we could not add a second, non-admin user without publishing the app, so we stopped. Bolt and Softr were not part of this run. Don’t read this page as a result for any builder other than Lovable.
  • It is not legal or compliance advice. If your app will hold client or personal data, get a qualified review before real users sign in.

Check your own Lovable app

This report doesn’t repeat the checklist or the tools. Use them for your own app:

For how Lovable did on our three standard builds, plans and costs, see our Lovable review.

Why this report has no screenshots

We captured screenshots for the checks we ran (aside from a separate post-T2-09 reload for T2-10), but those captures show our own builder workspace and private test inboxes. We are not publishing them. The results above come from our timestamped test log and were checked against those screenshots before publication.

Lovable security FAQ

Is Lovable SOC 2 compliant?

Lovable says it has a SOC 2 Type II report and ISO 27001:2022 certification, in its compliance post. The same post says that covers Lovable as a vendor, not your app: if a customer asks for a SOC 2 report on your own service, you need your own independent examination. This page reports what Lovable says; it is not an audit of Lovable.

Does Lovable scan my app?

Yes, according to Lovable’s security docs. A Quick scan runs automatically every time you publish and checks database access rules, npm dependencies and MCP server exposure. A Deep scan reviews all of your app’s code; it doesn’t run automatically as you work, so you start it from the Security view, the Security center or the project chat (Enterprise workspaces can also schedule it). Lovable says the scans cannot guarantee complete security. The two-account test on this page is a separate hands-on check, not a scan result.

Is my Lovable app secure by default?

Don’t assume it is. Lovable’s docs say you are responsible for making sure your app meets the security needs of its use case, and that its scans cannot guarantee complete security. In our one test, a Lovable Pro client portal passed 8 of 10 two-account checks through its interface; the other 2 were unmeasured because we didn’t test direct record or document URLs, or the app’s API. Before real users sign in, work through our vibe coding security checklist.