Fix your Base44 app

Run Base44’s security scan first

Base44 has its own security scan. It reads your app’s code in the background and looks at:

• Data rules that let too many people see or change records.
• Passwords and keys written into the app’s code.
• Backend functions anyone can call, on apps that don’t need a login.
• Outdated packages with known problems, and missing protections on your published site.

Where your data rules are too open, it suggests tighter ones you can apply. Run it again afterwards. When the same warning returns, or a rule change breaks something your users rely on, bring in an engineer.

What to know about Base44

• Your data rules decide who sees what. Each kind of data has rules for who can create, read, change and delete records, and can hide single fields, like a phone number, from most people.
• Backend functions can skip those rules. Code that runs as the app itself bypasses them, so it has to check who’s asking on its own.
• A scan goes out of date when the app changes. Scan again after each change you publish.

What we do

1. Describe the problem the way your users would.
2. Pay the set price up front. If it turns out bigger, you see the new price and decide.
3. Add the engineer to your Base44 app with their own login. They tighten the rules or repair the code.
4. Try it yourself, then publish.

Questions