# Is your app public?

> Canonical: https://teamonly.dev/tools/is-my-app-public

A free check for apps built with Lovable, Bolt, Replit, Vercel or any AI tool. Paste the link at https://teamonly.dev/tools/is-my-app-public and it opens the app the way a stranger would, then tells you what they can see.

## What the check looks at

- **Can a stranger open it?** It opens the link with no cookies and no login, like someone who was sent the link. If it lands on a sign-in page, the app is protected.
- **Can search engines list it?** It reads the page's robots settings and the site's robots.txt.
- **Are keys in the code?** It reads the page and up to eight scripts it loads from the same site, and looks for the patterns of common secret keys (OpenAI, Anthropic, OpenRouter, Stripe secret, AWS, GitHub, Supabase service role and secret keys, private keys).
- **Does the database rely on the browser?** It notes when the app talks to Supabase or Firebase from the browser, where the database rules are all that protects the data.

It never tries other addresses, never logs in, and never uses a key it finds. Keys are shown shortened. The link is not stored.

## Questions

**My app has a sign-in screen. Does that make it private?** Not always. In many apps built with AI, the sign-in runs inside the page, so the page and all its code load for anyone first. What protects the data is the database rules. A login in front of the app, like TeamOnly's, stops strangers before any of it loads.

**It found a secret key. What now?** Revoke the key in the service's dashboard and make a new one, today. Then ask your AI tool to move that call to the server side of the app, so the key never reaches the browser. See https://teamonly.dev/guides/secure-vibe-coded-apps for the rest of the checklist.

**I set my Lovable or Vercel app to private. Why does it say public?** Some private settings only cover preview links, or only hide the editor and not the published site. The check shows what a stranger sees right now.
