Skip to content
HARDEX

Guide

How to check if your Firebase app is open to everyone

Firebase lets an app save and read data straight from the browser, with no server of your own. That is quick to build, and it means the rules you set in Firebase are the only thing between your data and everyone else.

This is a short checklist for apps that use Firebase, whoever or whatever wrote them: four things to check, each with a way to check it yourself and what to do. You do not need to be a developer.

1Database rules that allow everyone

A Firebase project has rules that say who may read and write. The console offers a “test mode” that leaves the data open so you can build quickly, and it asks you to replace those rules later. If they were never replaced, anyone who has your app's settings, which are visible in its pages, can read and change the data.

Check it yourself: In the Firebase console, open the rules of each database you use and look for a rule that allows everyone, such as allow read, write: if true or ".read": true. Also look for an expiry date in the rules.

What to do: Replace open rules with rules that let each signed-in person reach only their own data. You can ask your AI builder: “Write Firebase rules so that each signed-in user can read and write only their own documents, and deny everything else.” Then test with two accounts.

2Storage rules that allow everyone

Files that people upload go to Firebase Storage, which has rules of its own, separate from the database's. The same test-mode setup can leave them open, so anyone can read, replace or add files.

Check it yourself: Open the Storage rules in the console and look for a rule that allows everyone to read or write. Then open the address of a file that should be private in a window where you are signed out.

What to do: Replace open rules with ones that let people read and write only their own files, and keep public only what has to be, such as logo images.

3The settings in your pages are not the secret

The settings your web app uses to find your Firebase project, including its API key, are meant to be in the pages, and Firebase's documentation says that key is not a secret. What protects your data is the rules. So finding these settings in your pages is normal, and not a reason to panic, but it is a reason to make sure the rules are right.

Check it yourself: Open your live app, press F12 and search the files for firebase to see which settings are in the pages. Make sure no admin credentials and no private keys of other services sit next to them.

What to do: Leave the web settings where they are, fix the rules in the first two parts, and move any private key you find to a server.

4Anonymous sign-in, and rules that only ask for “signed in”

If anonymous sign-in is switched on, anyone can get a signed-in session without giving a name or an email. A rule that only requires the user to be signed in then lets everyone in.

Check it yourself: In the console, look at the sign-in methods and see whether anonymous sign-in is on. Then read your rules: if the only condition is that a user is signed in, anyone can pass it.

What to do: Switch off anonymous sign-in if you do not use it, and write rules around who the user is and which data is theirs, not only around the fact that they are signed in.

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 made by AryonX. Firebase is named here only to say what this guide is about.