Default security settings of AI app builders, from their own docs
By default, a published app is open to anyone on Lovable's Free and Pro plans, on Bolt, and in a personal Replit workspace, while Google AI Studio keeps a new app private. Every builder below has a way to keep secret keys on the server. The tables give each default, one builder per row.
Each row quotes the builder's own docs, read on the date in the sources list. Builders change these defaults often, so check your own settings before you rely on a row. Where a builder's docs say nothing, the row says "Not stated in the docs we read", which does not mean the feature is missing.
Who can open a published app?
| Builder | Default, from its own docs |
|---|---|
| Lovable | On Lovable's Free and Pro plans, anyone with the link can visit your published app. Lovable's Business and Enterprise plans let you choose who can access a published app |
| Bolt | In Bolt's Publish menu, the default visibility is public. Bolt's paid plans let you publish a private site for your team and people you invite |
| Replit | Replit apps in a personal workspace default to Public, and apps in an organization workspace default to a private option. Replit's development URLs are public to the web by default |
| v0 | v0 asks you to choose who can access the deployed app at first publish, with choices set by your team's plan and deployment protection settings |
| Base44 | Base44 sets apps that act like public sites, such as landing pages or portfolios, to Public without requiring login |
| Google AI Studio | Google AI Studio keeps a new app private by default, and deploying it to Cloud Run gives it a public URL |
Who sets the data access rules?
| Builder | Default, from its own docs |
|---|---|
| Lovable | Lovable sets up row level security rules automatically when it builds features that store user data |
| Bolt | Bolt's database settings flag problems such as a missing row-level security policy or a permission that is too open, on all plans, and leaked password protection is on by default for Bolt databases |
| Replit | Replit says current development databases are only accessible from within your app and never exposed publicly |
| v0 | Not stated in the docs we read |
| Base44 | Base44 recommends data access rules as you build |
| Google AI Studio | The Google AI Studio agent generates Firebase Security Rules designed to be "default deny", so end users can only access the data they own. Firebase says reviewing and testing those rules before production is your responsibility |
Which security check runs, and when?
| Builder | Default, from its own docs |
|---|---|
| Lovable | Lovable's Quick scan runs a fixed set of checks in seconds every time you publish, and its Deep scan does not run automatically as you work |
| Bolt | Bolt's project security audit reviews your code and database and is available on paid plans, with up to 30 audits a day. Bolt recommends running a security check at least once before you publish |
| Replit | Replit runs a security scan before publishing, and its dependency scans are free and run automatically |
| v0 | v0 says all generated code undergoes security analysis before execution, and it warns about risky NEXT_PUBLIC_ usage |
| Base44 | Base44's security scan is available on all plans, including the free plan, and the scan does not apply fixes automatically. Base44 says to run it before publishing |
| Google AI Studio | Not stated in the docs we read |
Where do secret keys go?
| Builder | Default, from its own docs |
|---|---|
| Lovable | Lovable secrets are encrypted, injected into your Edge Functions and never reach the browser, while anything prefixed with VITE_ is a browser-exposed value |
| Bolt | Bolt secrets are used by server functions, so private information never ends up in your users' browsers or devices |
| Replit | Replit encrypts each secret and makes it available to your project as an environment variable, and secrets are not available to Static Deployments |
| v0 | In v0, environment variables without the NEXT_PUBLIC_ prefix remain secure on the server, and only variables prefixed with NEXT_PUBLIC_ are exposed to the browser |
| Base44 | Base44 keeps API keys and credentials in an encrypted vault, only accessible from your app's backend |
| Google AI Studio | Google AI Studio makes Gemini API calls from server-side code, so the key is never exposed in the browser |
What can an outside check confirm?
A check from outside your app sees what any visitor sees. That confirms some defaults and says nothing about others.
| Default | What an outside check can see | What it cannot see |
|---|---|---|
| A published app is public | Whether the address answers without signing in | Whether you meant it to be public |
| Keys stay on the server | Whether a secret key shows up in the JavaScript the browser downloads | Keys held in server environment variables, which never reach the browser |
| Data rules are set up for you | What a request without signing in gets back | Whether row level security is on, or why a read was refused |
| The builder runs its own scan | Nothing, because the scan runs inside the builder | Whether the scan ran or what it found |
A public publishable key in the browser is expected and is not a secret. Rows coming back to a request without signing in do not prove row level security is off, and an empty or refused read does not prove a table is protected. A missing security header is a hardening gap, not proof of an attack.
How to check
- Find your builder above, then open its settings and confirm the default still holds for your plan.
- Run your builder's own security check and fix what it finds. Our guides for Lovable, Bolt, Replit, v0 and Supabase walk through each one.
- Run a quick check on your published address to see what a stranger sees, and read how we check for what it covers.
Questions people ask
Are AI app builders secure by default?
Partly. Every builder in these tables has a way to keep secret keys on the server, but who can open your app and who writes your data rules differ, and Lovable says its scans cannot guarantee complete security. Check your own settings.
Is my Lovable or Bolt app public as soon as I publish it?
Usually. On Lovable's Free and Pro plans, anyone with the link can visit your published app. In Bolt's Publish menu, the default visibility is public. Lovable's Business and Enterprise plans let you choose who can access a published app, and Bolt's paid plans let you publish a private site for your team and people you invite.
How often do these defaults change?
Often. Builders add scans and change publishing defaults through the year, so treat each row as true on the day in its source and check your own settings.
See what your site shows from outside
A quick check reads your homepage the way a visitor would and gives you a score. No account needed.
Check your siteSources
- Add Cloud Firestore and Authentication to your Google AI Studio app Firebase docs, read on October 6, 2026
- Build apps in Google AI Studio Google AI for Developers, read on October 6, 2026
- Check your project's security Bolt support, read on October 6, 2026
- Choosing who can access your app Base44 docs, read on October 6, 2026
- Database Lovable docs, read on October 6, 2026
- Database secrets settings Bolt support, read on October 6, 2026
- Database security settings Bolt support, read on October 6, 2026
- Deployments v0 docs, read on October 6, 2026
- Development and production databases Replit docs, read on October 6, 2026
- Development URLs Replit docs, read on October 6, 2026
- Project Security Center Replit docs, read on October 6, 2026
- Publish your project Lovable docs, read on October 6, 2026
- Publish your project to a live website