Skip to content
HARDEX

Guide

How to check if your Lovable app is secure

Lovable can turn a prompt into a working app, with sign-in and a database, in an afternoon. What it builds is real software that real visitors can reach, so it is worth a look from the outside before you share it.

Lovable offers its own security scan when you publish, and it is worth running. This is the second look: five things to check on what is actually live, the way a stranger on the internet would see it, each with a way to check it yourself and what to do. You do not need to be a developer.

1Access rules on every table

A Lovable app keeps its data in a Supabase database, either one you connected yourself or the one that comes with Lovable's own backend. The app's pages usually talk to that database straight from the visitor's browser, so what protects your data is the set of access rules on each table, not the screens of your app. A table with no rules, or a rule that says “allow everyone”, is open to anyone who has the app's public key, and that key is visible in the app. A rule written to make an error go away can end up allowing everyone.

Check it yourself: Open the database view from your Lovable project and look at each table that holds anything personal: emails, messages, orders, files. A table with its access rules switched off, or with a rule that allows everyone, is open. Then look as a stranger: sign out, open your app in a private window and see whether any page shows records that are not yours.

What to do: Turn the rules on and write them so that each person can reach only their own rows. You can ask Lovable: “Turn on access rules for every table, and let each signed-in user read and change only their own rows.” Then test the app with two different accounts.

2Keys in the pages everyone downloads

In a Lovable project, a value whose name starts with VITE_ is built into the pages every visitor downloads, on purpose, so anyone can read it. A public key, such as the one your app uses to talk to the database, is meant to be there. An admin key, a payment key or an AI service key is not, and Lovable's documentation describes its Secrets feature as the place for values that must stay private.

Check it yourself: Open your live app and press F12 to open the browser's developer tools. In Chrome, go to the Sources or Network tab and search the files for words like key, secret, token and sk-. Anything that looks like an admin, payment or AI key should not be there.

What to do: Move the key into Lovable's Secrets so that it is used only on the backend. Then create a new key and delete the old one, because anyone who saw the old one can still use it.

3Who can sign up

Lovable can add sign-in for you, with email and password or with Google. If anyone can create an account without confirming an email address, anyone can fill your app with accounts, use whatever signed-in people get for free, or sign up with someone else's address. For a public app that can be fine, but it should be your choice.

Check it yourself: Try to create an account with a made-up address and see whether the app lets you in without a confirmation email. Then look through your project's backend sign-in settings for open sign-up, email confirmation and password length.

What to do: Turn on email confirmation if your app is for a limited group of people, and turn off the sign-in options you do not use.

4Uploaded files that anyone can open

If your app lets people upload photos or documents, they are kept in file storage. If an area of the storage is public, anyone who finds its address can open its files, and sometimes see a list of everything inside it, including files you thought were private.

Check it yourself: Open the storage section of your project's backend and see which areas are marked public. Then open the address of a private file in a window where you are signed out. If it opens, it is not private.

What to do: Make storage private by default and make public only what has to be, such as logo images. Serve private files through links that stop working after a short time.

5Pages you forgot about

The address your visitors use shows what you published, which may not be what you are looking at while you edit. Admin screens, test pages and old versions made while building are easy to leave behind, and anyone who types or finds their address can open them.

Check it yourself: Open your public address in a private window, where you are signed out, and click through every page. Try the addresses you used while building, such as an admin or test page. Anything that should be private must ask for a sign-in or answer “not found”.

What to do: Remove the pages you no longer need, put anything private behind sign-in, and publish again.

What a check can and cannot tell you

Passing these checks does not prove an app is safe. It means these problems were not found. A full review also looks at how your app handles each person's data, and that takes someone who reads the code or tries to get past the sign-in.

Check them all from the outside

Hardex scans a live app the way a stranger on the internet would, with nothing to install. By default it only reads: it never changes anything in your app. It looks for the problems above where they apply to your app, and more, then reports what it found.

What each plan includes is on the plans page.

Scan your app

Hardex is an independent product. It is not made by, or affiliated with, Lovable or Supabase.