Duvaxa

Free tool

Is your AI-built app leaking secret keys?

Enter your app's address. We look at it the way any visitor's browser does and tell you if it gives away keys that let strangers read your database or spend your money.

We only load public pages, like a browser. We never log in or touch your database. Keys we find are masked, never shown in full or stored, and results are cached for an hour.

Why AI-built apps leak keys

Tools like Lovable, Bolt, v0, Replit and Cursor build a working app in minutes, and the fastest way to make something work is often to put a key straight into the front end. Everything in the front end is downloaded by every visitor's browser. A key there is a key you've published: anyone can open the browser's developer tools and copy it.

What we look for

  • Keys that must stay on a server: the Supabase service-role or secret key (it ignores every security rule), OpenAI and Anthropic keys (anyone can spend your credit), Stripe secret keys, AWS access keys, GitHub tokens, SendGrid keys and private keys.
  • Files that should never be public: .env, which usually holds every secret the app has, and the .git folder, which lets anyone download your source code and its history.
  • Source maps: they hand out your original source code and comments.
  • Supabase and Firebase projects: their public keys are fine in the browser, but only if your database rules are right.

The anon key is public. Your database rules are what protect you.

Supabase's anon (or publishable) key and Firebase's config are designed to be in the browser. What stops a stranger from reading every row is row-level security (RLS) in Supabase, or security rules in Firebase. If a table has RLS turned off, or a policy that says "true", anyone with the public key can read or change it. That's the most common serious problem in AI-built apps, and it can't be seen from outside without querying your database, which we won't do to someone else's app. LaunchLock does it for you, from your own computer, with your own key.

If we found a key

  1. Rotate it now, in the provider's dashboard. Deleting it from your code isn't enough: it's already been published.
  2. Move the call that needs it into a server function (a Supabase Edge Function, a Vercel or Netlify function, or your backend), and keep the key in that platform's secret settings.
  3. Check the provider's logs and bills for use you don't recognise.

FAQ

Questions

Is it safe to run this on my app?

Yes. We load the same public page and JavaScript files any visitor's browser loads, and ask for /.env and /.git/config. We don't log in, submit forms or query your database.

Can I check someone else's app?

The check only reads what's already public, but please check apps you own or have permission to test, and tell the owner privately if you find something.

Is the Supabase anon key a problem?

No, it's meant to be public. The question is whether your row-level security policies stop it from reading data it shouldn't. LaunchLock tests that with your key.

Do you see or keep the keys?

Keys are masked to their first few and last four characters before the result leaves our server. Nothing is stored except daily usage counts, and results are cached for an hour.

Does an A mean my app is secure?

It means nothing secret is visible in what a browser downloads. Server code, database rules, logins and payments still need checking. That's what LaunchLock and our audit cover.

Which platforms does it work with?

Any public website: Lovable, Bolt, v0, Replit, Cursor-built apps, Bubble, Webflow, or hand-written code. We read up to 12 of the app's own JavaScript files, including pages that only load after login.