Guide
How to check if your Base44 app is secure
Base44 can turn a prompt into a working app, with its own database and sign-in, 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.
Base44 has its own security scan, and it is worth running. This is the second look: four things to check on what is actually live, each with a way to check it yourself and what to do. You do not need to be a developer.
1Who can read each kind of record
Base44 keeps your data in entities, such as users, orders or messages, and each entity has access settings. Its documentation says visitors who are not signed in can reach only the entities marked as public. A record type that holds anything private should not be public.
Check it yourself: Open the access settings of each entity and note which are public and which are restricted. Then open your app in a private window where you are signed out and see what you can read.
What to do: Make every entity that holds anything personal restricted, and write its rules so that each person can reach only their own records. Then test with two accounts.
2Sensitive fields inside a record
Base44's documentation also describes rules for single fields, apart from rules for whole records. Someone who is allowed to read a record can usually read all of its fields, including ones you did not think about, such as an email address, a phone number or a private note.
Check it yourself: List the fields of each entity and mark the ones that should not be shown to every person who can read the record. Then sign in as an ordinary user and see which of those fields you can read.
What to do: Add field rules so that a sensitive field is shown only to its owner or to the people who need it, or move it to a record that only they can read.
3Backend functions that skip the rules
Base44's documentation says that a backend function using the service role skips the entity access rules and the field rules, and that checking who is asking is then your own job. A function like that can return anyone's data to anyone who calls it.
Check it yourself: Ask your AI builder to list every backend function that uses the service role and say what each one returns. For each, ask: does it check who is calling before it returns or changes data?
What to do: Add a check of the signed-in user to each of them, so that it returns or changes only what that user may see. Use the service role only for work that really needs it.
4Keys left where visitors can find them
Base44's documentation describes an exposed-secrets check in its security scan. It is worth running, and it is worth looking yourself too: a key left in a page or in a file that visitors can open can be copied by anyone.
Check it yourself: Open your live app and press F12. In Chrome, go to the Sources or Network tab and search the files for words like key, secret, token and sk-.
What to do: Move any private key to a backend function and keep it in a place meant for secrets. Then create a new key and delete the old one.
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 appHardex is an independent product made by AryonX. Base44 is named here only to say what this guide is about.