Akshit | Rebar

Your Lovable/Bolt/Replit app broke? I'm the guy you call. Stripe, login, data leaks: fixed at a flat price, 48h target. You pay only when it works. Free scan ↓

[Akshit | Rebar @getrebarus]

@Michael_Dev315 nice catch on the missing table! one heads up tho: if "made it public" means a using (true) policy, anyone with your anon key can read every row.

worth locking it to auth.uid() = user_id. and if the image itself goes to supabase storage, that bucket needs its own policy too

[Akshit | Rebar @getrebarus]

@SirEstablish @supabase good news, you don't need the laptop. log into https://t.co/g5LkQSdHtn from your phone or any borrowed computer, open the paused project and hit restore.

even past 90 days the project page still lets you download the DB backup + storage files, so the data isn't gone

[Akshit | Rebar @getrebarus]

@doctor_barns @supabase ugh, rough spot, sorry man.

sites dying like that is usually Supabase returning 402 on the API (billing restriction). the database itself can still be up, sometimes read-only.

try pg_dump on the direct connection string right now. if it connects, your clients' data is safe

[Akshit | Rebar @getrebarus]

In SQL editor:

select tablename from pg_tables
where schemaname='public' and not rowsecurity;

select tablename,policyname,cmd,roles
from pg_policies
where schemaname='public' and qual='true';

anon/public = anyone. authenticated = any signup.
Free scan: https://t.co/6Vy3CwnTFB

[Akshit | Rebar @getrebarus]

Your Supabase table says "RLS enabled".
It can still be wide open.

60-second check:
1. Table Editor shows "Unrestricted"? RLS is off.
2. A policy that's just `using (true)`? Every row, open to that role.

Your anon key ships in your frontend by design. RLS is the only lock.