Vibe coding compliance: what GDPR, SOC 2 and HIPAA ask of an AI-built app

Compliance rules attach to the data and to whoever runs the app, whatever wrote the code. Your platform's SOC 2 report covers the platform: Supabase says its compliance does not transfer outside its control, and Replit lists GDPR, HIPAA and PCI DSS among your responsibilities. For a vibe-coded app the work is to know where personal data sits, sign the right agreements, and keep dated proof that access was tested.

The team behind Keybrum's attacksUpdated 11 min read

In short

  • No framework has an exemption for AI-written code. Under GDPR you are the controller as soon as you decide why and how personal data is processed, even in a weekend project with real users.
  • A platform's certificate stops at the platform. Supabase's docs say its SOC 2 compliance does not transfer to environments outside its product or control, and that the remaining controls are the customer's.
  • Lovable's FAQ states that Lovable is not HIPAA-compliant and does not sign business associate agreements. Supabase and Vercel sign them on certain plans, with settings you must turn on yourself.
  • GDPR Article 32 asks for a process for regularly testing your security measures. Article 25 asks that personal data is not open to an indefinite number of people by default, which is what a table without access rules is.
  • Keep an evidence file: a map of where personal data sits, your agreements with each provider, dated test results for access controls, and a log of who approved each change.
On this page

Does it matter to a regulator that AI wrote the code?

No. The rules that apply to an app follow the data it holds and the organization that runs it. The GDPR, the EU's data protection law, defines the controller as whoever "determines the purposes and means of the processing of personal data". If you built a sign-up form and a users table, that is you. HIPAA follows health information. PCI DSS follows card numbers. SOC 2 examines the controls of your company. None of them asks which tool typed the code.

What vibe coding changes is how easily the gap opens. An app that stores personal data now takes an afternoon to publish, often by someone who has never read a data processing agreement. The public cases show the result. In May 2026 the firm RedAccess reported about 5,000 publicly reachable AI-built apps holding sensitive corporate information, including a hospital app with summaries of doctor and patient conversations. In February 2026 one showcased app exposed 18,697 user records, students among them. The incident timeline lists the rest.

What your platform's certificates cover, and where they stop

The builders and hosts behind AI-built apps hold real certifications, and say plainly where they end. These are their own statements, read in November 2026.

PlatformWhat it holds or offersWhat it says stays yours
LovableSOC 2 Type II, ISO 27001:2022 and AIUC-1. A data processing agreement on Business and Enterprise plans. Not HIPAA-compliant, and it does not sign business associate agreementsIts security scans support secure development but do not guarantee it. It recommends a professional security review for apps that handle sensitive data
SupabaseSOC 2 Type 2, with the report available to Team and Enterprise customers. A business associate agreement from the Team plan, with a HIPAA add-on requestYour application architecture, row level security on tables with sensitive data, your secrets and API keys, the third-party services you connect
VercelSOC 2 Type 2, ISO 27001:2022, PCI DSS attestations. Business associate agreements for eligible Pro and Enterprise customersCompliance is described as a shared responsibility. For payments, it tells customers to use a payment provider's iframe so card data never touches the app
ReplitSOC 2 Type II for the platformReviewing the code Agent generates, your app's authentication and access rules, penetration testing of your app, and regulatory compliance: its docs name GDPR, CCPA, HIPAA, PCI DSS and SOC 2

Supabase's SOC 2 page has the sentence that sums up all four: its compliance "does not transfer to environments outside of the Supabase product or Supabase's control", and controls outside that boundary "are the responsibility of the customer". Your customers will not ask how your host runs its data centers. They will ask who can read their data in your app, and that answer lives in rules you or your agent wrote.

GDPR: the four articles a vibe-coded app meets first

If people in the EU use your app and you store anything about them, four articles become concrete quickly.

ArticleWhat it asksWhere AI-built apps trip
25, data protection by defaultPersonal data must not be made accessible to an indefinite number of people without the person's interventionA table created without row level security is readable by anyone who holds the public key from your page
28, processorsA contract with every company that processes personal data on your behalfEach service the agent wired in is a processor: the database, the host, the email sender, the model provider. Lovable's FAQ says its agreement is not included on Free and Pro plans
32, security of processingMeasures appropriate to the risk, including a process for regularly testing and evaluating themNobody tested the app as a stranger or as a second user, and nothing retests it after each new prompt
33, breach notificationTell the supervisory authority within 72 hours of becoming aware of a breach, where feasible, unless it is unlikely to put people at riskNo logs to say what was read and since when, and no contact address for the researcher who found it
Infringements of Articles 25 to 39 can be fined up to 10 million euros or 2% of worldwide annual turnover, whichever is higher (Article 83).

Article 32 names the risk in plain terms: unauthorised disclosure of, or access to, personal data. That is exactly what an open table or a missing ownership check produces. The practical reading for a small team is short. Close the data by default, with row level security on every table. Test it from outside on a schedule and after changes. Keep the result. And prepare the 72 hours before you need them: the guide on what to do when your app is hacked has the order of operations, and a security.txt file gives a researcher somewhere to write.

SOC 2: what an auditor will ask about AI-written code

A SOC 2 report is issued by a CPA firm after it examines the controls of your company, against criteria published by the AICPA. Building on certified platforms helps, because their reports cover the layers they run. It does not give you a report. Two areas get harder when an agent writes the code.

Change management. The criteria expect changes to be authorized, tested and approved before they reach production, and auditors ask for the evidence. "I asked the AI and published" leaves no approver and no test. Work on a branch, open a pull request even when you are alone, and let the record show what changed, what checks ran and who merged. On a builder without branches, keep a dated note of each publish and what you verified.

Evaluating your controls. SOC 2 has no explicit penetration test requirement. A CPA writing for the Cloud Security Alliance puts it this way: "there are no explicit requirements for penetration testing (or any controls) within a SOC 2 report". The criteria still ask that you evaluate your controls and detect new vulnerabilities, and a dated outside test is common evidence for both. A customer contract that asks for a pentest makes it required anyway. The guides on pentests for startups and security questionnaires cover what buyers accept.

HIPAA: the platform decides before the code does

HIPAA applies to US health data held by covered entities and the vendors that serve them, called business associates. Every vendor that touches protected health information needs a signed business associate agreement (BAA). That makes the first question a platform question, and some answers are no.

  • Lovable: its FAQ says Lovable is not HIPAA-compliant and does not sign BAAs, and that its terms do not permit protected health information or payment card data. It suggests contacting sales before building with regulated data.
  • Supabase: a BAA is available from the Team plan, after a HIPAA add-on request. Its shared responsibility page then lists what you must enable yourself, including point in time recovery, SSL enforcement and network restrictions, and its HIPAA page says the responsibility of applying the recommended controls falls directly to the customer.
  • Vercel: it signs BAAs with eligible Pro and Enterprise customers. Pro teams buy a HIPAA BAA add-on from their billing settings.

A BAA is the start. The Security Rule's technical safeguards ask you to allow access only to the persons or programs that have been granted access rights, to record and examine activity in systems that hold health information, and to verify that a person seeking access is the one claimed. It also requires an accurate and thorough risk assessment and a periodic technical evaluation. In app terms: per-user access rules that hold, audit logs, real authentication, and a recurring test. A generated app gets none of these by default. Count the model provider too: if a prompt carries patient data to an AI API, that provider is one more vendor in the chain.

Payments: stay out of PCI scope

The simplest compliance decision in a generated app is to never see a card number. Use your payment provider's hosted checkout or embedded fields, so card data goes from the browser to the provider. Vercel's compliance page gives the same advice, and Lovable's terms do not permit payment card data. Then check what the agent built around it: no table with card numbers, a webhook that verifies the signature, and prices computed on the server. The PCI DSS guide explains who needs a penetration test under requirement 11.4.

The evidence file: what to keep, and how to start it today

Every framework above ends with the same request: show me. Start with a map of where personal data sits. On a Postgres or Supabase database, this query lists the columns whose names suggest personal data. It reads the catalog and changes nothing:

sql
select table_name, column_name
from information_schema.columns
where table_schema = 'public'
  and column_name ~* '(email|phone|name|address|birth|dob|ssn|passport|iban|card|diagnos|health|patient)'
order by 1, 2;
A starting list, not a complete one: free-text columns, file uploads and JSON fields can hold personal data under any name.

For each table it returns, write down why you store the data, who may read it, and when it is deleted. Then build the rest of the file.

  • A data map: the tables and buckets that hold personal data, and the purpose of each.
  • The list of your providers (database, host, email, payments, model API), with the agreement signed with each: a data processing agreement, and a BAA where health data is involved.
  • The dated output of a query listing tables without row level security, showing none.
  • The result of a test with two accounts: the second could not read or change the first one's records.
  • A dated report of an outside test of the live app, and the retest that closed each finding.
  • A change log: for each release, what changed, which checks ran, who approved it.
  • An incident note template with the time you became aware, and the address where a breach can be reported to you.
  • The procedure for deleting a user's data on request, tried once.

If your buyers are companies, the same file answers most of a vendor questionnaire, and a trust page is the public version of it. The vibe coding policy template turns these habits into rules for a team.

What Keybrum gives you for compliance, and what it does not

Keybrum is not a compliance product and not an auditor. It does not make an app GDPR, SOC 2 or HIPAA compliant, it issues no certificate, and it does not review your contracts, your logging, your backups or your encryption at rest. Those need the work described above.

What it produces is evidence for one line that every framework contains: that access to the data was tested from outside, on a date, with a result. Keybrum attacks the deployed app as a stranger and as accounts it creates. It reads the tables your public key can reach, tries writes that are rolled back, has one account try to read and change another account's object, calls your API routes with no session, looks for secret keys in the bundle and requests files such as .env. Each finding comes with the request that worked. A finding closes when the same attack fails on the live app.

  • The report: a PDF that lists what was attacked, what failed and what worked, with the date. It also states what was not tested.
  • Retests: the record shows a finding opened and closed, which is the evidence an auditor or a buyer asks for after a problem.
  • Every deploy: on a plan, the attack runs again after each deploy and on a schedule, which is one way to do the regular testing Article 32 describes.
  • A trust page: plans include a public page that shows what was tested and when. On the Team plan, reports and trust pages carry your brand.

Two limits matter for regulated data. Keybrum only attacks apps whose owner proved ownership, and it keeps counts, column names and one redacted row as proof, never the data. Even so, an outside test that can read a row is itself something to clear with your compliance contact when the app holds health data, before you run any third-party test, ours included. A one-time report costs €49. Plans start at €29 a month excluding VAT, and the Team plan is €99 a month for 25 apps.

Questions

Is a vibe-coded app GDPR compliant?

Not by default, and not because of how it was built. GDPR compliance depends on what you do with personal data: access closed by default, agreements with each provider, regular testing of your security measures and a way to report a breach within 72 hours. An app generated by AI needs the same work as any other.

Is Lovable HIPAA compliant?

No. Lovable's FAQ states that Lovable is not HIPAA-compliant and does not sign business associate agreements, and that its terms do not permit protected health information. For an app that handles US health data, choose providers that sign a BAA, such as Supabase from the Team plan or Vercel on eligible plans.

Does my platform's SOC 2 report cover my app?

It covers how the platform runs its own service. Supabase states that its SOC 2 compliance does not transfer to environments outside its product or control. Your access rules, your API routes and your own company's processes are examined only if you get your own report.

Who is responsible if my AI-built app leaks data?

You are, as the one who decided to collect the data. Under GDPR that makes you the controller. Platform documentation says the same from the other side: Replit's shared responsibility model lists your app's access rules, security testing and regulatory compliance as yours.

Does SOC 2 require a penetration test?

Not explicitly. The criteria do not list a pentest as a required control, and auditors accept other evidence that you evaluate your controls. In practice many buyers expect one, and a contract that asks for it makes it required.

Do I need a data processing agreement with my AI app builder?

If the builder hosts or processes personal data of people in the EU for you, GDPR Article 28 asks for a contract with it. Check your plan: Lovable's FAQ says its agreement is included on Business and Enterprise plans and not on Free and Pro. The same question applies to your database, host, email and model providers.

Sources

  1. 1.GDPR Article 4: Definitions, Regulation (EU) 2016/679, gdpr-info.eu
  2. 2.GDPR Article 25: Data protection by design and by default, Regulation (EU) 2016/679, gdpr-info.eu
  3. 3.GDPR Article 32: Security of processing, Regulation (EU) 2016/679, gdpr-info.eu
  4. 4.GDPR Article 33: Notification of a personal data breach to the supervisory authority, Regulation (EU) 2016/679, gdpr-info.eu
  5. 5.GDPR Article 83: General conditions for imposing administrative fines, Regulation (EU) 2016/679, gdpr-info.eu
  6. 6.45 CFR 164.308: Administrative safeguards, Legal Information Institute, Cornell Law School
  7. 7.45 CFR 164.312: Technical safeguards, Legal Information Institute, Cornell Law School
  8. 8.FAQ: tech stack and compliance, Lovable Docs
  9. 9.SOC 2 compliance and Supabase, Supabase Docs
  10. 10.HIPAA Compliance and Supabase, Supabase Docs
  11. 11.Shared responsibility model, Supabase Docs
  12. 12.Security & Compliance Measures, Vercel Docs
  13. 13.Replit shared responsibility model, Replit Docs
  14. 14.SOC 2 Reports and Penetration Tests, Cloud Security Alliance
  15. 15.Thousands of Vibe-Coded Apps Exposing Corporate, Personal Data: RedAccess, Security Boulevard
  16. 16.Lovable-hosted app littered with basic flaws exposed 18K users, researcher claims, The Register

Your app is public. So are its mistakes.

Check what any attacker can already see in it, free, in ten seconds. The full attack, with proof and fixes: €49 once, or €29 a month on a plan.

or continue with Google or GitHub