Database rules switched off
Tables anyone can read, or change, with the public key every app ships with.
✓Access rules on every table, tested from the outside.
Sept 2026 · 16,326 open databases
No hacking needed: one request from a browser. I check your app the way an attacker would, close every door, and explain it in plain words.
UpGuard research · September 2026
16,326
app databases anyone could read.
Names, addresses, phone numbers, private conversations — many of them in apps built quickly with AI coding tools. Read the report coverage
What AI tools often leave open
Tables anyone can read, or change, with the public key every app ships with.
✓Access rules on every table, tested from the outside.
Payment, email or AI keys anyone can pull out of the app and run up your bill with.
✓Keys moved to the server; the old ones replaced.
The screen hides other people's data. The server still hands it out.
✓Every request checks who is asking.
Uploaded photos, IDs and documents open to anyone who has the link.
✓Private storage with links that expire.
How it works
Your app or website, and what you built it with. No passwords, no code needed to start.
From the outside, the way someone would who wants your users' data: the database, keys, logins and files.
What's open, how bad it is, and the exact request that proved it. I fix it, or your developer does — then I test again.
No obligation. I read every message myself and reply within one working day.
Not to start. The first look is from the outside, like an attacker's. For fixes you add me to the project, and remove me when we're done.
That's the best time. Closing the doors before launch is quicker than writing a breach email after.
No. What I find stays between us, and I delete any data I happen to see.
Web apps and iOS / Android apps built with Lovable, Bolt, Cursor, Replit, Base44, v0 or FlutterFlow, on Supabase, Firebase or your own server.