I will check your lovable or bolt supabase app for open rls and exposed keys


Informazioni su questo servizio
Built your app with Lovable, Bolt, v0, Cursor or Replit on Supabase? AI tools often ship tables without Row Level Security, or put secret keys in the code every visitor downloads.
I check your app from the outside, without your passwords:
- Secret keys in your JavaScript, source maps or a public .env
- Which of your tables the public anon key can read (row counts only)
- Security headers and public files
- Standard+: your RLS policies and code (read-only repo invite), plus a cross-user test with 2 throwaway test accounts you create
You get a plain-English PDF: issues ranked by severity, why each matters, and copy-paste fix prompts for your AI tool. If a key is exposed, you rotate it yourself. I never ask for passwords or secret keys.
Order, confirm the short consent form, then share what your tier needs. Everything stays here on Fiverr.
Please note: this is a focused check, not a penetration test or compliance audit. It can't find every issue and doesn't certify your app as secure. You apply or merge every change yourself.
Rispettare i diritti di terzi
Ricorda che è contrario alle politiche di Fiverr per i freelance includere temi, modelli o qualsiasi altro elemento che violi i diritti di terzi o le leggi applicabili nell'opera consegnata. Per saperne di più, consulta Guida alla creazione digitale responsabile.
Scopri di più su Sachin V.
Email deliverability and Google Merchant Center fixes
- DaEmirati Arabi Uniti
- Membro daott 2026
Lingue
Inglese
Altri servizi della categoria Manutenzione del sito web offerti da me
FAQ
Do you need my password or keys?
No. I never take passwords or secret keys. Basic needs only your URL and table names. Standard/Premium add a read-only repo invite and 2 throwaway test accounts that you create and delete afterwards.
Why test accounts?
To check whether one user can see another user's data, I need two logins that aren't real people. Any test writes only touch those test accounts' own sample rows.
A key was exposed. Will you rotate it?
No, you rotate it yourself in your own dashboard. Assume an exposed key was copied. Changing the code doesn't un-leak it.
Will you change my database or app?
No. You apply the SQL or prompts yourself (Basic/Standard), or review and merge my pull request (Premium).
Is a re-check included?
No. A re-check after you've applied fixes is a separate order.
Is my app secure afterwards?
I can't promise that. The report covers the listed items, at the time of the check.
What happens to my data?
It stays confidential. My notes, screenshots and repo copy are deleted 14 days after delivery, or sooner if you ask.

