Login and access

  • 1. What belongs behind a login really is behind it

    How Log out, open a private window and paste in the addresses of pages for logged-in users, such as /dashboard or /admin. If you see any data, even briefly before you are redirected, it is exposed.

    Why AI tools often hide a page only in the browser, while the data still arrives.

  • 2. Users can’t see each other’s data

    How Create two test accounts, A and B. As A, create a quote and copy its address, for example /quotes/123. Open that address as B, and try 122 and 124 too.

    Why This is the mistake we see most: the app checks that you are logged in, but not that the record is yours.

  • 3. You know who has admin rights

    How List everyone with admin rights in the app, your database, your host, your AI tool and on GitHub. Remove former freelancers and interns, and turn on two-factor authentication everywhere.

    Why Whoever has your hosting or database account has your whole app and all its data.

Data and keys

  • 4. Your database returns nothing without a login

    How Supabase: every table flagged "RLS disabled" in the Security Advisor is a problem. Test it too: press F12 in your app, open the Network tab, and copy the apikey header from a request to supabase.co/rest/v1/. Run in a terminal (curl.exe on Windows): curl "https://YOURPROJECT.supabase.co/rest/v1/TABLE?select=*" -H "apikey: KEY", for a table you know has rows. If rows come back, anyone can read them. Firebase: if true, a test-mode rule on request.time, or a rule that only checks request.auth != null lets too many people read.

    Why The public key is in your website on purpose. Without access rules on each table, a table is usually public. This is the flaw behind CVE-2025-48757.

  • 5. There are no secret keys in your website or your code

    How First click through every page, because the search only sees loaded files. Then search in Chrome (F12, Sources tab, Ctrl+Shift+F or Cmd+Option+F on a Mac) for sk_live, rk_live, sk-proj, sk-svcacct, sk-admin, sk-ant and sb_secret. A public or "anon" key may be there. On GitHub, check that the repository is private and has no .env file.

    Why With a Stripe, OpenAI or Anthropic secret key, someone else runs up costs on your account. If a key was ever in the code, replace it: it stays in the history.

  • 6. Uploaded files aren’t readable by anyone

    How Upload a PDF as user A, copy the link and open it in a private window. In Supabase, check under Storage whether the bucket is "Public". A link with token= that expires is fine by design.

    Why Invoices and ID cards often end up in a public bucket, behind a link that can be guessed or forwarded.

Where the data lives, and GDPR

  • 7. You know which services get your data, and where

    How Use your app for five minutes with the Network tab open and note every domain. Ask your builder which other services the server uses, such as email or an AI model. For each one, note which data it gets, in which region, and whether you have a data processing agreement.

    Why Every service that processes personal data on your behalf is a processor. You need a data processing agreement with it, and it belongs in your privacy notice.

Backups and recovery

  • 8. Your backup works, and you’ve tried it

    How Check in your database dashboard whether backups exist and how long they’re kept. Some free plans have none. Restore one once into a separate test project.

    Why One wrong migration from an AI assistant can empty a table in one go.

  • 9. You can see who did what, and you know what to do after a leak

    How Ask your builder where you can see who logged in and who changed data, and how long those logs are kept. Write one page on who you call when something goes wrong and how to replace a leaked key.

    Why You report a personal data breach to your data protection authority within 72 hours of becoming aware of it, unless it is unlikely to put the people concerned at risk.

Before you launch

  • 10. Your forms handle odd input

    How Type <b>test</b> into a name field. If the name shows up in bold anywhere, ask your builder whether input is sanitised everywhere. Also paste 10,000 characters into a text field and try a 100 MB upload.

    Why What ends up on the page as formatting can sometimes end up there as a script. Only the server can check input reliably.

  • 11. Costs and abuse have a ceiling

    How Set a spending limit or budget alert on your AI service, your host and your database. Ask your builder whether there is a limit on attempts for login, sign-up and your contact form.

    Why A bot that fills in your form 50,000 times, or someone using your AI feature for their own work, sends you the bill.

What this list won't catch

An access rule that is almost right, a key in a server log or an integration that passes on more than it needs only shows up when someone reads the code. That is what the vibe-coded app check does: three days, with a report ranked by severity.

Book a call

Sources: CVE-2025-48757 (disputed by Lovable); GDPR, Articles 28 (processors) and 33 (breach notification).