Skip to main content

Supabase security review and Row Level Security hardening

Supabase exposes your Postgres tables through an API that any browser can call with the public anon key. Whether your data is safe depends almost entirely on Row Level Security and a few settings that are easy to get wrong.

ISO 9001 & ISO/IEC 27001Certified quality and information securitySince 2014, made in GermanyDiese Seite auf Deutsch

Why Supabase projects leak data

The anon key in your frontend is meant to be public. It is safe only because every table in an exposed schema should have Row Level Security enabled with policies that limit rows to the right user or role. If RLS is disabled on one table, or a policy simply returns true, anyone who opens the browser's developer tools can query that table directly.

This happens often in apps generated with Lovable, Bolt or similar tools, where tables are created quickly and policies are added later or not at all. Our AI Code Engineers at neooutput review Supabase projects systematically, write and test the missing policies, and leave you with a setup your team understands. For larger products, OnlineAppCreator can take over ongoing development and operations.

Supabase pitfalls to watch for

  • Views in the public schema bypass RLS by default unless they are created with security invoker. A view joining user data can expose more than the underlying tables allow.
  • Functions marked security definer run with the creator's rights. If they are callable through the API without checks, they become a back door around your policies.
  • Policies that compare against data the user can edit, such as a role column in their own profile row, let users promote themselves. Keep authorisation data in tables or claims that users cannot write.
  • RLS policies with subqueries on large tables can slow every request. Index the columns used in policies and test performance with realistic data volumes.
  • Auth settings matter too: email confirmation, redirect URL allow lists and rate limits on sign-up should match your production domain before launch.

What the review covers

Every table and policy checked

We list each table, view and function in exposed schemas and test policies as anonymous, authenticated and other-user roles. You see exactly which queries succeed that should not.

Keys and secrets cleaned up

We check that the service role key and third-party secrets never reach the client and live only in edge functions or your backend. Exposed keys are rotated, not just removed.

Storage and functions included

Storage buckets need their own policies, and edge functions often skip JWT checks. Both are reviewed alongside the database.

Tests that keep it fixed

Policies get automated tests in your repository, so a future migration or AI-generated change cannot silently reopen a hole.

How the Supabase review works

  1. Read-only access

    You grant access to the project and repository. We work on a branch or staging project, never directly on production data.

  2. Exposure scan

    We query the API with the public key and test accounts to find readable or writable data, then review policies, grants and security definer functions.

  3. Fix and migrate

    Policies, indexes and function changes are written as versioned migrations and reviewed with your team before deployment.

  4. Report and handover

    You receive a findings report with what was fixed, remaining risks and a checklist for future tables.

Matching products

neooutput

Agentic coding workshops and AI services. Hands-on agentic coding workshops for teams on Claude Code, OpenAI Codex and Cursor, remote or on-site, in English or German. Plus AI Code Engineers on demand who deploy, secure and scale AI-built apps.

Explore neooutput workshops

OnlineAppCreator Custom Development

Idea to operating product, built by AI Code Engineers. We take ideas to operating digital products: discovery, AI-native engineering by our AI Code Engineers, launch, SLAs and scale. B2B and public sector, from an ISO 9001 and ISO 27001 certified team in Germany.

See how we build products

Frequently asked questions

Is the Supabase anon key a secret?

No. It is designed to be used in the browser and app. Security comes from Row Level Security and grants, which is why a missing policy is a serious problem.

Can you review a project created by Lovable?

Yes. Lovable and similar tools connect to a regular Supabase project, so we review it the same way. We also check the generated frontend for keys and calls that should run server side.

Will the review break our app?

We test every policy change on staging first, using the same flows your users run. Changes go live only after your team has reviewed them, typically during a quiet period.

Do you also handle GDPR questions around Supabase?

We look at region selection, data minimisation and access logging as part of the review. Legal assessment remains with your data protection officer, and we provide the technical facts they need.

Let's talk about your project.

15 minutes with an AI Code Engineer, free and without obligation. Or call our team around the clock.