Interesting time we are in. So many people are jumping into building with whatever value we could offer to the society, myself included (yay!), instead of letting the opportunity pass them by. About me, I spent 6 years in data security & privacy, so checking and ensuring data is actually protected is the one part of building I am very excited about. Here is the pattern I kept seeing. A solo builder ships on Supabase, sees RLS on, and assumes their users' data is protected. But RLS on is a setting, not a proof. Also not every way of creating a table gets the safe defaults, especially the AI-generated ones, and a policy can look right while quietly letting everyone through. So the questions that actually decide it are basic ones. Is there any guarantee that a complete stranger, no login at all, cannot read your users' data? That a signed-in user cannot pull up another user's data? That none of your storage buckets are open to anyone with the link? That your master key is not sitting inside your website's public code? So my hypothesis is, we as solo builders hardly test our product the way a stranger would, because there has been no easy way to and also hey, arent we supposed to move fastttt. So, I packaged those basic security checks into a single HTML file for every solo-builder for FREE -> https://midnightbuilds.fyi/makerguard/ It runs in your browser against your own Supabase, with your project data staying completely private to you (because that's all I know we need, privacy) Have you run checks like these on your product? If yes, which tools did you use? And if you haven't tested it this way, would you be open to trying this checker and telling me whether it is truly helpful to you? Anything else costing you the most today?   submitted by   /u/swati425 [link]   [comments]