GDPR for AI-built and vibe-coded apps
If your app processes personal data of people in the EU/UK, GDPR applies regardless of where you're based or that you built it with an AI tool. In practice it means: have a lawful basis to collect data, only collect what you need, secure it properly, let users access and delete their data, and don't leak it. For vibe-coded apps the biggest GDPR risk is the same as the biggest security risk — an exposed database leaking personal data.
- Applies if
- You handle personal data of EU/UK individuals
- Core duties
- Lawful basis, data minimization, security, user rights
- Biggest risk
- Personal data exposed via open database/keys
- Breach rule
- Notify within 72 hours of becoming aware
Does GDPR apply to your app?
If you collect names, emails, IP addresses or any data that can identify a person in the EU or UK, yes — even as a solo founder outside Europe. GDPR follows the data subject, not your location. Most apps with EU users are in scope.
Security is a GDPR requirement, not just good practice
GDPR requires 'appropriate technical measures' to protect personal data. An app that leaves its database publicly readable or ships secrets in the client is, by definition, failing that requirement — and a leak of personal data is a reportable breach (within 72 hours). Locking down RLS, secrets and authorization isn't only security hygiene; it's compliance.
User rights: access and deletion
Users can ask to see their data and to have it deleted. Your app needs a real way to honor that — which is hard if data is scattered or you're not sure what you store. Design for data access and deletion early, and keep a record of what personal data you hold and why.
Get cleared before you launch.
Join the early-access list. We'll prioritize founders with a deployed app and a launch date on the calendar.
Questions
- Does GDPR apply if I'm not in the EU?
- Yes. GDPR applies based on whose data you process. If you have EU or UK users, you're in scope regardless of where you or your servers are located.
- What's the most common GDPR failure for vibe-coded apps?
- Exposed personal data. An open database or leaked key that reveals users' personal information is both a security breach and a GDPR violation. Securing data access is the first compliance step.