Missing row-level security is the most common exposure in Lovable apps, and the person who built an app is often the least able to spot it. From February 3 to April 20, 2026, a regression also let any Lovable user with a link read public projects' chats and code. Before an app reads company data, have someone other than its builder check its row-level security, visibility settings, and sign-in controls.
When you need this
- A Lovable app will read customer, employee, or financial data.
- Security or IT must approve Lovable for teams outside engineering.
- You need to know what the April 2026 exposure means for your projects.
Evaluation criteria
Row-level security
Can one user read another user's rows?
Look forEnable row-level security with restrictive conditions on every table holding private data. Lovable's Supabase docs identify missing policies as the most common exposure. Matt Palmer found inadequate policies on 303 endpoints across 170 of 1,645 apps in Lovable Launched.
Project visibility
Who can see the code and the build chat?
Look forCheck project visibility separately from website access. Project visibility controls the editor and code, plus chat. From February 3 to April 20, 2026, any Lovable user with a link could read public projects' chats and code. Lovable fixed the regression within two hours of the public report and made historic public projects private. Lovable says private projects and Cloud were unaffected.
Published app access
Who can open the live app?
Look forRestrict published apps to invited people on any plan or workspace members and groups on Business and Enterprise. Every plan otherwise defaults to anyone with the link. Enterprise can restrict who publishes externally.
Training and retention
Is our data used to train models?
Look forBusiness and Enterprise exclude workspace data from training by default. Since September 9, 2026, Free and Pro data may be used for training unless each user opts out, and opting out does not remove content from training sets assembled earlier. Move builders who handle company data onto Business. End-user submissions to your apps are excluded. Enterprise uses only zero-data-retention models unless an admin enables extended retention.
Identity
How do people sign in, and what happens when they leave?
Look forOIDC or SAML SSO comes with Business and Enterprise. Business creates accounts on first sign-in. Enterprise adds SCIM and two-factor enforcement, plus invitation limits. Enterprise audit logs stay in Lovable for 13 weeks. Since October 15, 2026, Enterprise admins can export them every hour or every 3 hours to Amazon S3, Google Cloud Storage, Azure Blob Storage, Splunk, or Azure Log Analytics.
Scans
What do Lovable's scans cover?
Look forEach publish checks row-level security and permissive access, plus leaked-password protection and npm dependencies. Request a free deep scan for authorization and injection, plus secrets, payments, and personal-data exposure. Wiz and Aikido connectors add checks. Enable blocking for critical issues, which is off by default except on new Enterprise workspaces. Lovable's docs say the scans do not replace a security review.
Regulated data and region
Can it hold regulated data, and where does it live?
Look forLovable is not HIPAA compliant and signs no business associate agreements, so keep health data out. It holds SOC 2 Type II and ISO 27001:2022, plus AIUC-1. Cloud data stays in the region chosen at setup, in the Americas, Europe, or Asia Pacific. EU model inference requires Enterprise. Deploy on AWS and Deploy on Azure, which run apps and their data in your own cloud account, are open to Enterprise teams by invitation through the account team (October 20, 2026).
Questions to ask vendors
- Which Lovable projects were public between February 3 and April 20, 2026, and what did their chats contain?
- Who reviews row-level security before an app that reads company data is shared?
- Is blocking publishes with critical issues turned on for the workspace?
- Are any builders on Free or Pro, where training is on unless each user opts out?
- Do we need SCIM, audit logs, or EU inference, which only Enterprise includes?
Red flags
- Secrets pasted into prompts or frontend code when they belong in Lovable's secrets store.
- Apps that read company data published to anyone with the link.
- Treating a clean quick scan as a security review.
- Health or other regulated data in a Lovable app.
Products in this piece
Sources
- Official documentation
- 18
- Public source
- 1
- Lovable docs: Changelog
- Lovable blog: Enterprise features, October roundup
- Lovable docs: Connect to Supabase
- Lovable docs: Security best practices for Lovable apps
- Lovable docs: Control project access
- Lovable blog: Our response to the April 2026 incident (Apr 22, 2026)
- Lovable docs: Publish your Lovable project
- Lovable docs: Privacy & security settings
- Lovable docs: Manage training data and privacy
- Lovable Privacy Policy (updated Sep 15, 2026)
- Lovable docs: Workspace single sign-on (SSO)
- Lovable docs: SCIM user provisioning
- Lovable docs: Audit logs
- Lovable docs: Security overview
- Lovable docs: Workspace security center
- Security at Lovable
- Lovable docs: Lovable for Enterprise
- Lovable docs: FAQ
- Matt Palmer: Statement on CVE-2025-48757 (May 29, 2025)