I will write and test secure firebase firestore security rules

Most Firebase apps ship with rules that look safe and are not. "allow read, write: if request.auth != null" lets any signed-in user read and overwrite every other user's data, and the Firebase console will not warn you.

I write Firestore and Storage security rules that enforce your real access model, and I prove it with automated tests against the Firebase emulator, not by clicking around the app.

What I cover:

• Per-user data: users can only read and change their own documents
• Roles: admin, manager, staff, customer, or whatever your app uses
• Multi-tenant isolation: one company can never see another company's data
• Field validation: types, required fields, immutable fields like createdAt or ownerId
• Storage rules for uploads: file type, size, and owner checks

You get the rules file, the test file you can run yourself with one command, and a short plain-English note explaining every rule.

I have written and tested rules for production apps, including a multi-tenant SaaS used by restaurants in 8 languages.

Please send me your current rules and a short description of who should see what before ordering.