Lovable

The owner can download the project code as a zip (paid plans) or sync it to Git, and export Cloud data as an SQL dump that is emailed when ready, but there is no export of the agent itself and no importer: the Lovable agent runs only on Lovable's hosted service, Git import into Lovable is not supported ('You can only export from Lovable to GitHub'), and running the code elsewhere needs manual hosting, dependency and backend setup.

• View and edit your project's code
• Sync your Lovable project with GitHub
• Deploying and hosting outside Lovable
• Advanced settings (Export Lovable Cloud data)

Exports cover code (including Supabase migrations and edge functions) and a Cloud database SQL dump; project chat and activity history, project and workspace knowledge, agent permission settings and connector credentials have no export (secrets are write-only and gateway connectors authenticate through Lovable's OAuth client), so two or more classes stay with the provider.

• View and edit your project's code
• Advanced settings (Export Lovable Cloud data)
• Secrets
• Integration security
• Define workspace and project knowledge

The agent is a hosted service that requires a Lovable account; the Terms grant only a 'limited ... revocable license' that 'terminates immediately if ... your account is terminated for any reason'. Exported app code can run elsewhere, but the agent cannot run without Lovable.

• Lovable Terms of Service
• FAQ

'Can I choose which model Lovable uses in Build mode or Plan mode? No. Lovable manages the underlying model used by the agent'; there is no setting to switch models and no local-model option. (Model choice for the owner's app AI features is separate and not the agent's model.)

• FAQ

The Terms state 'On termination, your right to access the Services ends', allow immediate suspension or termination for suspected breach, and give no post-termination export window or shutdown plan; by default no current copy is held by the owner (Git sync and code download are manual/optional).

• Lovable Terms of Service
• Git sync overview

Code is readable as ordinary source files, but the agent's own state (chat and activity record, knowledge, settings, provider-supplied skills) is readable only through Lovable's hosted UI; Lovable-built skills 'cannot be edit[ed], delete[d], or download[ed]', and data is encrypted at rest 'with managed keys' held by the provider.

• Define reusable instructions with skills
• Lovable Privacy Policy
• View and edit your project's code

The owner can see knowledge, skills and activity cards, but not Lovable's base system prompt or the fully assembled context; the model identity is not determinable ('The agent runs on current frontier models' with no setting or disclosure of which). Two shortfalls.

• FAQ
• Define workspace and project knowledge
• Work with Lovable in the project chat

The Privacy Policy keeps operational and security logs 'for as long as needed to run and secure the Services' and retains de-identified or aggregated data derived from Customer Data 'on a perpetual basis for any lawful business purpose' (Terms); these holdings are not visible item by item and have no bounded period.

• Lovable Privacy Policy
• Lovable Terms of Service

The agent defaults to Lovable's own services (Lovable Cloud with 'Always allow' enablement, the Lovable AI gateway with a Lovable-chosen default model, Lovable hosting); these are documented and can be replaced (Cloud set to 'Never allow', own Supabase, own API keys). No paid placement was found, but its absence rests on no binding commitment.

• Lovable Cloud (Cloud permissions)
• AI features for your app
• Deployment, hosting, and ownership options

Chat activity cards record file edits, commands, web searches, browser tests and subagents, and version history keeps every code version; workspace audit logs exist only on Enterprise (and are pruned after about 90 days). No record of provider or staff actions on the owner's projects is documented, and nothing documents that recording failures are surfaced to the owner (G12). Two shortfalls.

• Work with Lovable in the project chat
• Version history
• Audit logs
• Subscription plans

No integrity data (hashes, signatures or independent anchoring) is documented for the chat/activity record or version history; the record is held only by Lovable.

• Work with Lovable in the project chat
• Version history

The chat/activity record and version history are maintained by the Lovable platform, and the agent's documented tools (file edits, commands, database and connector actions) do not include editing the chat record, but Lovable documents no protection guaranteeing the agent cannot alter or suppress its record; protection rests on architecture/convention only.

• Work with Lovable in the project chat
• Version history

The Lovable agent and platform are closed source; the Terms define the Platform and 'models' as Lovable Materials in which the owner gets no ownership interest.

• Lovable Terms of Service

The agent has no owner-rooted identity: it acts through the owner's Lovable account and, on GitHub, commits under 'the Lovable GitHub app identity', both provider-issued and revocable.

• Sync your Lovable project with GitHub
• Git sync overview

Version history shows code diffs per version, links each to the chat message that produced it, and restores code in one click; it does not restore database data, very old versions 'can no longer be restored', and changes to knowledge, settings, permissions or the provider-managed model are not versioned or attributable on self-serve plans (audit logs are Enterprise-only).

• Version history
• Audit logs
• Define workspace and project knowledge

Project and workspace knowledge and custom workspace skills are owner-editable and persist, but Lovable's base prompt is not exposed and 'Skills built by Lovable' can be used but 'you cannot edit, delete, or download them'.

• Define workspace and project knowledge
• Define reusable instructions with skills

Knowledge (project and workspace, 10,000-character text fields) and the project's security memory document are fully viewable and editable; the project chat history the agent reuses across sessions is not documented as itemised editable or deletable memory.

• Define workspace and project knowledge
• Project security view (security memory)
• Work with Lovable in the project chat

Owners can connect any remote MCP server as a chat connector on all plans without provider review, and Cloud tools and connectors can be set to 'Never allow'; built-in tools such as file editing, commands, web search and browser testing have no documented removal control.

• Connect a custom MCP server
• Lovable Cloud (Cloud permissions)
• Work with Lovable in the project chat

Some provider protections are adjustable (connector approval defaults, Cloud tool permissions), but others are locked: Lovable-managed secrets 'cannot be deleted', secrets are write-only, and VITE_-prefixed secrets are rejected; no documented switch exists for the platform's sandboxing or dependency audit.

• Secrets
• Security overview
• Account settings (Agent permissions)

'Lovable rolls out model upgrades automatically to all users, so there is no setting to switch the agent between specific models'; the hosted agent and its instructions change without an opt-in or pin.

• FAQ
• Lovable changelog

Per-connector and per-Cloud-tool permissions (always/ask/never) and credit check-ins exist, but there is no per-domain egress control for web search or fetches and no per-path file scope (shortfall 1), and code the agent writes and deploys as edge functions uses stored secrets to call external services, which the agent can invoke directly, outside connector-level limits (shortfall 3). Two shortfalls. Payment spend was treated as met under G11 (the agent has no payment instrument).

• Lovable Cloud (Cloud permissions)
• Account settings (Agent permissions)
• Edge functions
• Test and verify your app
• Chat connectors

Owners can gate a fixed set of classes: connector write actions, Cloud tools (read/modify database, change data, configure auth), project creation and edits from Chats, and image/video generation; code edits, commands and web searches cannot be gated except by choosing Plan mode, and Cloud tools default to 'Always allow'.

• Account settings (Agent permissions)
• Lovable Cloud (Cloud permissions)
• Chat connectors
• Plan mode

The stop button 'immediately halt[s] the current task' in a project, and builds started from Chats have a separate 'Stop Lovable' control; there is no single documented control that stops all activity across projects and background runs at once.

• FAQ
• Chat with Lovable across your workspace
• Set a goal for Lovable

On Free and Pro, 'customer data ... may be used to train, develop, and improve Lovable's AI models ... unless you opt out'; the Privacy Policy states 'trained members of our team may review this content', and the Terms grant a perpetual licence to exploit Customer Data 'for any other lawful business purpose'. Training is on by default for the graded plan.

• Manage training data and privacy
• Lovable Privacy Policy
• Lovable Terms of Service

Project secrets and connections are listed by name and can be deleted individually, with 'access ends immediately when you delete a connection', and Lovable states no one can read credentials back; however Lovable-managed secrets 'cannot be deleted', and no binding term limits Lovable's use of owner credentials to owner-directed actions.

• Secrets
• Integration security
• Chat connectors

Account deletion is one flow that finalises after a 30-day grace period and confirms only that deletion is scheduled; per the docs it 'does not retract content from training datasets assembled, or models trained, before then', so provider-side copies survive.

• Delete account
• Manage training data and privacy
• Lovable Privacy Policy