The database access rules are usually what's missing

supabase/migrations/20260312_quotes.sql
  1. create table public.quotes (
  2. id uuid primary key default gen_random_uuid(),
  3. owner_id uuid not null references auth.users,
  4. client_name text,
  5. client_email text,
  6. amount numeric(10,2)
  7. );

Sinto Labs

Row level security is off. Your website ships the public key to this database, so anyone who copies it from the page source can read and change every quote.

Suggested change

  1. alter table quotes enable row level security;
  2. create policy "own quotes" on quotes
  3. for all using (auth.uid() = owner_id);
A migration as an AI tool writes it, with our review comment. Without the three suggested lines, anyone can read and change every quote.

In March 2025 a researcher scanned 1,645 apps built with Lovable, looking only at their home pages. In 170 of them, 10.3%, anyone could read data from the database. A later test showed writes were possible too.

Source: CVE-2025-48757 (disputed by Lovable) and the researcher's statement.

Ten places we check

We read the code and the settings, then try it on your app.

  • Login: whether what belongs behind a login is behind one on the server, not only in the browser.
  • Access rules: row level security in Supabase or rules in Firebase, table by table. Can user A see user B's data?
  • Keys: whether a secret key sits in your website or in your repository's history.
  • Dependencies: known vulnerabilities and outdated versions.
  • Input: what happens with odd input in your forms and API.
  • Uploads: whether the link to an invoice or an ID card works for anyone.
  • Processors: which services receive personal data, in which region, and which need a data processing agreement.
  • Backups: whether they exist, and whether anyone has ever restored one.
  • Logging: whether you can see afterwards who logged in and who changed what.
  • Admin access: former freelancers, shared passwords, two-factor authentication.

Three days of work, a report and a call

  1. A 30-minute call. You tell us what the app does and who uses it. You give us read access to the repository and to the database and hosting dashboards, plus two test accounts.
  2. Three days of checking. On a staging environment where possible. On production we only test what can't break anything, and we agree on that beforehand.
  3. Report and call. Findings ranked by severity, each with what, where, why it matters and how to fix it. We walk through them with you and whoever built the app.
  4. Fixes, if you want them. Your builder works through the list, or we do it in a fix sprint.

We work at a fixed day rate or at a fixed price per outcome. You know the price before we start. A larger app, with more user roles, more integrations or a second app, takes more than three days.

What a finding looks like

Finding 1 of 11

Severity: critical

Anyone can read every invoice, without an account

What
The invoices table has no row level security. With the public key your website ships, someone without an account can fetch the whole table: 1,240 rows with name, email, address and amount.
Where
Supabase project app-prod (eu-central-1), table public.invoices. Requested with GET /rest/v1/invoices?select=*, not logged in.
Why it matters
This is your customers’ personal data. If someone else has already fetched it, that is a data breach you report to your data protection authority within 72 hours. The API logs for the past 7 days show only our own test.
Fix
alter table public.invoices enable row level security;
create policy "own invoices" on public.invoices
  for all using (auth.uid() = owner_id);

Then run the same request again without logging in: you should get an empty list. Effort: about 30 minutes, test included.

An excerpt from a report. The project and the numbers are made up; the format is how we write up every finding.

Then: lock down the accounts around your app

The biggest risk often sits next to the code: who is an admin at your host, which keys live where, who left and still has access. We help you close that up, as a follow-on to the check or on its own.

If your team uses Claude Code, Cursor or other agents, keys end up in new places: in a .env file the agent reads, in a prompt, in a log. We show your team how to prevent that:

  • Every agent and every service gets its own key, with only the permissions it needs.
  • Secrets in a password vault, outside the repository and outside the conversation with the agent.
  • Keys you can revoke and replace without everything going down.

What GDPR, NIS2 and the AI Act ask of your app

GDPR

If your app stores your customers' personal data, you are the controller. Every service that processes it for you, such as your database, hosting, email service or AI model, is a processor, and you need a data processing agreement with it. 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. Our report lists the processors your app uses, with their regions.

NIS2

Most small companies aren't directly in scope of NIS2, though some of their customers are, and those customers send supplier security questionnaires. What NIS2 asks and how we help you answer those questionnaires is on our data and security page.

AI Act

Writing your app with an AI tool doesn't bring it under the AI Act. If a chatbot in your app talks to customers, they have had to be told they're dealing with an AI system since 2 August 2026. If your app helps decide about people, for example which job applicants go through, it may count as a high-risk AI system. We flag that and point you to a lawyer.

Sources: GDPR, Articles 28 and 33; AI Act, Regulation (EU) 2024/1689, Article 50(1).

What the check isn't

  • No "GDPR compliant" stamp. You get a list of what's wrong and what's already fine.
  • No legal advice. We tell you which rules touch what we found. For the interpretation you need a lawyer.
  • No attack on production. No load tests, nothing that can delete data, and only on apps we have written permission to test.

To look for yourself first, use the free checklist: eleven checks, no email address needed.