Lovable
AI tools · lovable.dev · last read 2026-11-09
At a glance
- Is Lovable GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Lovable itself publishes, each answer linked to its source and the date we read it.
- Does Lovable have a data processing agreement (DPA)?
- Yes. Lovable publishes a data processing agreement at lovable.dev. It describes how a new subprocessor is announced but states no notice period. It promises breach notification "without undue delay", with no number of hours. Source and date
- Which version of the Lovable DPA is current?
- On 2026-11-09, Lovable's DPA at lovable.dev printed “Last updated: November 6, 2025”. Source and date
- Does Lovable have a SOC 2 report?
- Lovable says SOC 2 Type 1 and Type 2 reports are available on request. In Lovable's words: “We're pleased to share that Lovable has completed its SOC 2 Type II audit, covering the observation period from February 1 to August 1, 2026. The report is available on our Trust Center upon request.” We read this on 2026-10-29. Source and date
- Is Lovable ISO 27001 certified?
- Lovable states ISO/IEC 27001 certification (2022 edition, as Lovable names it), and says the certificate or audit report is available on request. In Lovable's words: “ISO 27001:2022 - Certificate of Registration.” We read this on 2026-10-29. Source and date
- Where is Lovable's trust center?
- Lovable publishes a page it calls “Trust Center” at trust.lovable.dev. Some of its documents sit behind a request or sign-in: the page says “Request access”. Its text appears only after JavaScript runs: a client without it, as most tooling is, gets an empty page. The page mentions SOC 2, ISO 27001, subprocessors and a DPA. We read it on 2026-11-03. Source and date
- Does Lovable use your data to train AI models?
- For consumer plans (Lovable Free and Pro): Customer data (prompts, code, project files, outputs) may be used to train Lovable's AI models as of September 9, 2026; users can opt out with an account-level setting. App end-user data and account/billing details are not used. For business plans (Lovable Business and Enterprise): Business and Enterprise Customer Content or Usage Data not used for training; prohibition set out in the DPA. Source and date
- What is Lovable's data retention for AI prompts and outputs?
- For consumer plans (Lovable): Customer Content kept while the account is open, then deleted or de-identified after closure or a verified deletion request. Source and date
- Can Lovable process AI data in the EU?
- For business plans (Lovable Enterprise workspaces): Optional EU inference workspace setting for Enterprise plans sends AI model requests to EU endpoints (building and published app AI features); web search, web fetch and browser automation agent tools still process data in the US. Source and date
- How does Lovable transfer personal data out of the EU?
- Lovable's agreement relies on the EU standard contractual clauses and the UK transfer addendum. We found no entry for Lovable on the official Data Privacy Framework List. Source and date
- Does Lovable offer EU data residency?
- The vendor documents an EU region but states nothing about which plan reaches it or what it costs. Source and date
- Who are Lovable's subprocessors?
- Lovable lists 46 third-party subprocessors; 24 of them name at least one processing country outside the EEA. We last read the list on 2026-11-02. We have recorded 1 change to it, the latest on 2026-11-02. Source and date
- How do you report a security vulnerability to Lovable?
- Lovable publishes a security.txt at lovable.dev naming [email protected]. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Lovable Labs Incorporated |
|---|---|
| HQ | US |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | — |
| LEI | — |
| US CLOUD Act reach | Contracting entity incorporated in the US |
| Source | lovable.dev · 2026-10-29 |
Lovable data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | Terms not stated | — | docs.lovable.dev | 2026-10-29 |
EU: Any user can pick Europe in their own Where project data is stored setting, and the page names no plan or cost for that. Only the workspace-wide Default data hosting region is limited to Business and Enterprise workspaces.
The same question for every vendor: where SaaS vendors store EU data.
Lovable's subprocessor list names AWS and Google for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
46 third parties · 24 with a country outside the EEA · all read 2026-11-02
| Subprocessor | Country | Purpose |
|---|---|---|
| Altinity | EU | Operates the production ClickHouse cluster. |
| Amazon Web Services | GB, US | Customer applications, databases, file storage and AI model inference. Services: S3, SES, Bedrock |
| Anthropic (Claude) | US | Customer prompts, generated code, AI interactions |
| Baseten | — | AI model inference for the Lovable agent. |
| Braintrust | EU | LLM evaluation and tracing. Stores prompts and responses. |
| Browserbase | US | Customer projects |
| Castle.io | US | Data analytics and fraud detection |
| Cinder | EU | Safety and moderation service |
| ClickHouse | EU | Analytics database. Holds platform usage data and end-user analytics from customers’ published apps. |
| Cloudflare | — | Edge routing, DNS & Workers |
| Customer.io | US | Customer engagement |
| ElevenLabs | US | Speech-to-text, text-to-speech, and music generation for voice and audio features |
| Entri | US | Custom domain connection and DNS records. |
| Firecrawl | US | Web crawling on customer-supplied URLs. |
| Fireworks | — | AI model inference for the Lovable agent. |
| GitHub | US | Code Repository |
| Google Cloud Platform | NL | Customer applications, databases and platform infrastructure. Services: Google Kubernetes Engine, Cloud Run, Spanner, Cloud KMS, Vertex AI |
| Google Cloud Vertex | US | AI model inference (Gemini models) for customer prompts and responses. |
| Google Maps Platform | — | Add-on Service provider; maps and places data for customer apps. |
| Grafana | US | Log/trace/metrics storage |
| Hex | EU | Customer & Platform analytics |
| HubSpot | US | Marketing & CRM |
| Intercom | US | Customer support communications |
| Lightspeed | — | Add-on Service provider; retail and transaction data for customer apps. |
| LlamaIndex (LlamaParse) | — | Add-on Service provider; parses user-uploaded documents and audio. |
| Mailgun | US | Transactional email, email domain management |
| Meta Platforms (WhatsApp Business) | — | Add-on Service provider; messaging from published customer apps. |
| Microsoft (Azure AI Foundry) | EU, FR, DE, US | AI model inference for the AI Gateway |
| Modal | — | Executes customer project code |
| OpenAI | US | Customer prompts, generated code, AI interactions |
| OpenRouter | US | LLM inference routing |
| Ouraring Inc. | — | Add-on Service provider; health and activity data for customer apps. |
| Parallel | — | Add-on Service provider; index, search and research for customer apps. |
| Perplexity | US | Web search for customer apps and the agent. |
| Pierre | EU | Customer Code Repository |
| Pipedrive | — | Add-on Service provider; CRM records for customer apps. |
| Posthog | US | Data analytics |
| Rudderstack | US | Customer analytics and usage data |
| Sentry | US | Performance monitoring |
| Stripe | US | Payment processing |
| Supabase | EU | Customer databases, user authentication data |
| TanStack | — | Application stack for customer apps |
| Temporal Technologies Inc. | GB | Workflow orchestration. Workflow payloads are retained in event history |
| Turbopuffer | EU | Indexing customer data to power search |
| TypeSafe AI | US | Decision models for generated code and actions |
| Whitecircle.ai | EU | Safety and Security |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
From the vendor's data processing agreement · read 2026-10-29 · lovable.dev
| Term | What the agreement says |
|---|---|
| Transfer mechanism | SCC module 2 |
| Transfer mechanism | SCC module 3 |
| Transfer mechanism | UK Addendum |
| Notice of new subprocessors | By updating the sub-processor list at lovable.dev/subprocessors; no advance notice period stated |
| If you object to one | Object on reasonable data-protection grounds within 20 business days of notice by emailing [email protected]; parties seek a good-faith resolution; if none is reached, the customer's sole remedy is to terminate the Agreement and get a refund of prepaid fees |
| Obligations passed to subprocessors | Same data protection obligations as in this DPA imposed on other processors by contract |
| Breach notification | May be delayed if law enforcement determines disclosure would impede a criminal investigation; notice as soon as the restriction is lifted |
| Breach notification | without undue delay after confirming a data breach |
| Deletion when the service ends | upon termination, returns or deletes personal data processed on Customer's behalf, subject to applicable legal retention obligations |
| Getting your data back | Customer may instruct Lovable in writing, within 30 calendar days after termination, to return all Customer Personal Data, unless the law requires storage. Lovable may charge reasonable costs where export work exceeds two person-hours. |
| Requests from data subjects | reports data subject requests to Customer without undue delay and promptly forwards requests received directly to Customer; no responsibility to interact directly with data subjects |
| Audit | third-party reports only: Lovable may share recent SOC 2 Type II and ISO 27001 reports on request, after approval and acceptance of confidentiality obligations |
| Processing on your instructions | processes Customer Personal Data solely on behalf of and under the instructions of the Customer |
| Confidentiality of staff | personnel bound by contractual or statutory confidentiality obligations; access limited to personnel who require it |
| Security measures | appropriate administrative, physical, technical and organizational security measures, as outlined on Lovable's Security Page (https://lovable.dev/security) |
Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.
Which version applies
On 2026-11-09, the agreement printed: Last updated: November 6, 2025
at lovable.dev
Last updated 2025-11-06
This version is in our copies from 2026-10-29.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
AI and your data
What Lovable's own pages state about the data you send its AI products, plan by plan. Compared with other vendors on AI vendors and your data.
| Plans | Term | What the page says | Source | Observed |
|---|---|---|---|---|
| Consumer Lovable Free and Pro | Training on your data | Used unless you opt out Customer data (prompts, code, project files, outputs) may be used to train Lovable's AI models as of September 9, 2026; users can opt out with an account-level setting. App end-user data and account/billing details are not used. | docs.lovable.dev | 2026-10-29 |
| Consumer Lovable | Data retention | Until deleted Customer Content kept while the account is open, then deleted or de-identified after closure or a verified deletion request | lovable.dev | 2026-10-29 |
| Business Lovable Business and Enterprise | Training on your data | Not used Business and Enterprise Customer Content or Usage Data not used for training; prohibition set out in the DPA | lovable.dev | 2026-10-29 |
| Business Lovable Enterprise workspaces | EU processing | In the EU Optional EU inference workspace setting for Enterprise plans sends AI model requests to EU endpoints (building and published app AI features); web search, web fetch and browser automation agent tools still process data in the US | docs.lovable.dev | 2026-10-29 |
| Business Lovable EU inference | Model providers | Amazon Web Services Bedrock | docs.lovable.dev | 2026-10-29 |
| Business Lovable EU inference | Model providers | Google Cloud Vertex AI | docs.lovable.dev | 2026-10-29 |
| Business Lovable EU inference | Model providers | Microsoft Azure AI Foundry | docs.lovable.dev | 2026-10-29 |
Assurance
Does Lovable have a SOC 2 report?
Lovable says SOC 2 Type 1 and Type 2 reports are available on request. We read this on 2026-10-29.
- Available on request “We're pleased to share that Lovable has completed its SOC 2 Type II audit, covering the observation period from February 1 to August 1, 2026. The report is available on our Trust Center upon request.”
Source: trust.lovable.dev, 2026-10-29
Of the 114 vendors in this registry whose own pages mention SOC 2, 57 say the report is available on request, 1 links to the report itself, and 56 state it without saying how to get it. The type is the one the vendor names.
Is Lovable ISO 27001 certified?
Lovable states ISO/IEC 27001 certification (2022 edition, as Lovable names it), and says the certificate or audit report is available on request. We read this on 2026-10-29.
- Available on request “ISO 27001:2022 - Certificate of Registration”
Source: trust.lovable.dev, 2026-10-29
Of the 122 vendors in this registry whose own pages state ISO/IEC 27001, 16 link to the certificate, 43 say it is available on request, and 63 state it without saying how to get it. A certificate names the certification body, the scope and the expiry date: those are the three things to check.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| GDPR | Claimed | — | trust.lovable.dev | 2026-10-29 |
| ISO 27001:2022 · ISO27001 | Available on request | — | trust.lovable.dev | 2026-10-29 |
| AIUC-1 | Available on request | — | trust.lovable.dev | 2026-10-29 |
| SOC 2 Type I · SOC2T1 | Available on request | — | trust.lovable.dev | 2026-10-29 |
| SOC 2 Type II · SOC2T2 | Available on request | covering the observation period from February 1 to August 1, 2026 | trust.lovable.dev | 2026-10-29 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
- ACN qualified cloud (Italy): checked 2026-11-09, no entry under Lovable; Lovable Labs Incorporated
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-09, no entry under Lovable; Lovable Labs Incorporated
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-09, no entry under Lovable; Lovable Labs Incorporated
- DORA critical ICT third-party providers (ESAs): checked 2026-11-09, no entry under Lovable; Lovable Labs Incorporated
- Data Privacy Framework List (US): checked 2026-11-09, no entry under Lovable; Lovable Labs Incorporated
- ENS certificates of conformity (CCN, Spain): checked 2026-11-09, no entry under Lovable; Lovable Labs Incorporated
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-09, no entry under Lovable; Lovable Labs Incorporated
- FedRAMP Marketplace (US): checked 2026-11-09, no entry under Lovable; Lovable Labs Incorporated
- GPAI Code of Practice signatories (European Commission): checked 2026-11-09, no entry under Lovable; Lovable Labs Incorporated
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-09, no entry under Lovable; Lovable Labs Incorporated
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
What an entry on the Data Privacy Framework List covers, and which vendors hold one: EU-US Data Privacy Framework.
Support window
Not yet collected. This row will say not declared only once we have read a lifecycle or security page and found no period stated — see support windows.
Vulnerability reporting: [email protected] (security.txt, expires 2027-06-19; read 2026-10-29)
How other vendors publish theirs: security.txt across the registry.
Documents
Where is Lovable's trust center?
Lovable publishes a page it calls “Trust Center” at trust.lovable.dev. Some of its documents sit behind a request or sign-in. Its text appears only after JavaScript runs: a client without it, as most tooling is, gets an empty page. The page mentions SOC 2, ISO 27001, subprocessors and a DPA. We read it on 2026-11-03. Open trust.lovable.dev
- Name “Lovable's Trust Center”
- Request step “Request access”
Source: trust.lovable.dev, 2026-11-03. Read from the page's text, without a model; every vendor's trust center.
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| ai | Public | full | 200 | 2026-10-29 |
| ai-2 | Public | full | 200 | 2026-10-29 |
| ai-3 | Public | full | 200 | 2026-10-29 |
| certifications | Public | full | 200 | 2026-10-29 |
| dpa | Public | full | 200 | 2026-10-29 |
| identity | Public | full | 200 | 2026-10-29 |
| residency | Public | full | 200 | 2026-10-29 |
| subprocessors | Public | full | 200 | 2026-11-02 |
History
| Detected | What moved | Why | Source |
|---|---|---|---|
| 2026-11-02 | Subprocessors added TypeSafe AI | the vendor changed it | trust.lovable.dev |
Every reviewed change across the registry, newest first: vendor changes.