Can user B see user A's data? Free Launch Check, written report in 48 hours.
Apps built fast with Lovable, Bolt, Replit, v0 or Cursor usually work in the demo and break when real users arrive. The most expensive failure is quiet: one customer can open another customer's records. We check that first.
Who this is for
Founders whose app is live with real users, or about to be. You probably need it if one of these is true:
- You built the app with Lovable, Bolt, Replit, v0 or Cursor and never tested what one account can see of another.
- Supabase or Firebase shows security warnings you have not cleared.
- You are about to take payments, or a bigger customer has started asking about security.
- A user reported seeing something that was not theirs.
What we check
- Whether one user can read, change or delete another user's data.
- Keys exposed in the browser.
- Missing rate limits on login and public endpoints.
- Backups that do not exist or were never restored.
- Payment webhooks that fail silently.
How it works
- Send your app URL and 2 test logins for 2 different accounts.
- We test only with those logins, never with real user data, and never anything you did not approve.
- You get a written report in 48 hours: what we found, how serious it is, and how to fix it.
- Keep the report and fix it yourself, or have us fix every item in a 1 week Fix Sprint for $2,500 fixed, with tests, and you own the code.
What the report looks like
Every finding has the same shape, so you can act on it the same day. This one is from a made-up app, not a real customer.
Any logged-in user can open invoices that belong to another team
- What we did
- Logged in as test account B, opened one of its invoices, then changed the invoice id in the request to an id that belongs to test account A.
- What happened
- The app returned the full invoice of account A: customer name, amounts and line items.
- The fix
- A row level security policy on the invoices table that only returns rows for the team of the signed-in user.
What is not included
- No access to your code or your database.
- Not a certified penetration test, and no compliance sign-off.
- No load or performance testing.
- Nothing outside the 2 test logins you send us.
Our own standard
How we prove data isolation on our own builds: a query with no workspace filter returns 0 rows from the other workspace, and the tests run against real Postgres in CI.
Read the SaleQue case studyAI on Microsoft Graph inside a live, multi-tenant Microsoft 365 product: no task, invite or reminder is created until a person accepts the suggestion, with 48 tests in the public repo.
Read the OfficeSyncPro case studyRow Level Security forced on every clinic table, owner and pet details encrypted with AES-256-GCM, and a test that proves one clinic cannot read another clinic's rows.
Read the Attendra case studyRequest your free Launch Check
Tell us where the app lives. We reply within 24 hours to arrange the 2 test logins, and the 48 hours start when they arrive.