Skip to content
HARDEX

Guide

Is your AI-built app safe to share?

Apps built with AI tools such as Lovable, Replit, Bolt, Cursor or Claude Code can go from idea to live in a day. The checks a security team would do rarely happen on the way.

This is a short checklist of seven problems worth looking for before you share an app, with a way to check each one yourself and what to do if you find it. You do not need to be a developer to follow it.

1Keys and passwords visible in the browser

Everything your app sends to a visitor's browser, the code included, can be read by that visitor. If a secret key ends up there, anyone can copy it and use your account, your email service or your AI credits. This can happen by accident: build tools such as Next.js and Vite send any variable named NEXT_PUBLIC_ or VITE_ to every visitor, on purpose, so a secret kept under such a name is not secret.

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-. Some keys are meant to be public, such as the one your app uses to talk to your database. An admin key, a payment key or an AI service key is never meant to be there.

What to do: Take the key out of the part your browser receives and keep it on a server. Then create a new key and delete the old one, because anyone who saw the old one can still use it.

2A database that anyone can read or change

Tools like Supabase and Firebase let your app talk to the database straight from the browser. That is safe only when access rules say who can see which rows. A table with no rules, or a rule that says “allow everyone”, is open to anyone who has the public key, and that key is visible in your app. Rules sometimes get switched off, for example to make an error message go away.

Check it yourself: In your database dashboard, open each table and look at its access rules. In Supabase, a table with its access rules switched off, or with a rule that allows everyone, is open. In Firebase, a rule that lets everyone read or write is open.

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

3Sign-up that is more open than you meant

If anyone can create an account without confirming an email address, anyone can fill your app with accounts, use whatever signed-in users 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. Look through your platform's sign-in settings for options like 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-up options you do not use.

4Uploaded files that anyone can open

Photos, documents and exports that people upload 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 your storage settings 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.

5Files that should never be on a live site

Files such as .env, .git, database backups and a page that shows your server's settings are meant for your own use. If they are published with the app, anyone who asks for them by address can get keys, passwords or all your code. They can end up there through a build or hosting setting nobody looked at.

Check it yourself: In your browser, try to open these addresses on your own app: yourapp.com/.env and yourapp.com/.git/config. You should see a “not found” page. If anything that looks like settings or code appears, it is exposed.

What to do: Remove the files from what is published, change every key or password that was in them, and ask your AI builder to make the app answer “not found” for these addresses.

6Missing protections in your pages

A website can send settings that tell the browser to protect its visitors: use only secure connections, refuse to be shown inside another site, and limit which scripts may run. They are easy to forget, and a new app does not always send them.

Check it yourself: These settings are invisible on the page, so the practical way to look is a free security header checker or a scanner. Enter your app's address and see which protections it reports as missing.

What to do: Ask your AI builder to add the standard security settings for your hosting platform, then check again.

7Email that can be faked in your name

If your app sends email, such as sign-up links or receipts, your domain needs records that prove the email really comes from you. Without them, anyone can send email that looks like it came from your address, and your real emails are more likely to land in spam.

Check it yourself: Look up your domain in a free SPF and DMARC checker. Both should be found.

What to do: Add the records your email service asks for. The service shows the exact values to add.

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