Terms of Service

lavela — Terms of Service

Last updated: October 17, 2026 Version: 2026-10-22

These Terms of Service ("Terms") are a binding agreement between you ("you," "your," or "Customer") and lavela, which operates the lavela platform ("lavela," "we," "us," or "our"). They govern your access to and use of the lavela website, GUI console, MCP server, APIs, and related services (together, the "Service").

Please read these Terms carefully. They include important provisions about how lavela acts on your behalf (Section 3), how the prepaid balance, welcome credit, card bonus, automatic top-ups, and refunds work (Section 6 and the Credits & Refunds Policy), what happens when your balance runs out (Section 7), limits on our liability (Section 12), and how disputes are resolved (Section 16). By creating an account, clicking "I agree," or otherwise using the Service, you accept these Terms.

This document is written in plain English to be understood, not to obscure. It is provided for your reference and is not legal advice. lavela recommends that the operator of any business review these Terms with a qualified lawyer in your jurisdiction.

---

1. Acceptance and Eligibility

1.1 Acceptance. You accept these Terms when you (a) click "I agree" in the signup clickwrap, (b) create an account, or (c) use any part of the Service. If you do not agree, do not use the Service.

1.2 The clickwrap record. Before lavela first provisions infrastructure or connects an account on your behalf, you must accept a versioned consent (the "Consent"). When you accept, we record the version accepted, the language of the text shown and a fingerprint (hash) of its exact wording, the date and time, and your IP address and browser (user agent) so both of us have a clear record of what you agreed to and when. If we materially change the Consent or these Terms, we bump the version, and you will be asked to accept the new version before lavela provisions, deploys or starts anything billed, adds funds (other than by an automatic top-up you already turned on, Section 14.3), or starts or raises ad spend at your request (see Section 14).

1.3 Eligibility. The Service is for adults only. You must be at least 18 years old and at least the age of legal majority where you live (whichever is higher), and able to form a binding contract; you confirm this when you accept the Consent (Section 1.2). lavela does not knowingly provide the Service to anyone below that age. If you use the Service on behalf of a company or other entity, you represent that you are authorized to bind that entity, and "you" refers to that entity.

1.4 Where paid features are available. A card issued in the United States or Canada pays lavela directly (Section 6.4), and so does a card issued in South Korea where lavela offers it — a Korean card must have overseas payments turned on by its issuer, and if it is declined you can ask your issuer to turn them on; automatic top-up (Section 6.6) needs a card that pays lavela directly. For a direct payment, the country that issued your card decides (as reported by Stripe) — not the billing address you type. If a direct top-up is paid with a card issued in a country that cannot pay lavela directly, it is not added to your balance and the full charge is refunded; such a card is removed if you save it for automatic top-up. If the billing country you enter differs from your card's issuing country, we may pause direct top-ups until we review it. A card issued in any other country is not supported for direct payment or automatic top-up; Section 6.4A covers any other checkout lavela offers. The welcome credit and other features may also be limited by region. You must give us accurate billing details; we may ask you to confirm them.

1.5 Account security. You are responsible for your account credentials and for all activity under your account, including actions taken by any AI agent (such as Claude or Cursor) that you connect to the Service. Tell us promptly if you suspect unauthorized use. If we learn that a token that gives access to your account has been exposed — for example posted in a public place — we may revoke it at once (any agent connected with it stops working) and will try to let you know; you can then create a new one.

---

2. Description of the Service

2.1 What lavela is. lavela is an MCP-first launch and operations platform for the app you built. Acting as your agent (see Section 3), lavela:

• Provisions and operates cloud infrastructure on your behalf — web hosting and CDN, compute and containers, databases, domains, transactional email, caching, object storage, logging/error monitoring, and web analytics;
• Connects payment and advertising accounts you authorize (for example, your Stripe Connect account and ad platform accounts);
• Runs day-1 through day-90 operations — monitoring and recovery (Section 2.1A — for web-hosting sites on the date of these Terms, and for servers only where lavela offers it), security scans, compliance document generation, and daily AI summaries.

2.1A Monitoring, alerts and rollback. lavela checks some of what it runs for you — web-hosting sites, and servers only where lavela offers it — and tries to tell you when something stops answering; these are best-effort tools, not a guarantee (Sections 10 and 11.2). Wherever these Terms say "where lavela offers it" (or that lavela offers a particular feature, such as "where lavela offers billed builds"), what these Terms say about that feature — in that sentence and in the sentences that go on to describe it — applies only from the time lavela makes that feature available to you; until then it describes nothing you can use and nothing you are charged for. This does not make conditional anything these Terms present as available on the date of these Terms, such as the uptime checks, the alerts to your notification channels and the automatic rollback of web-hosting sites in (a) and (d), or the billing of the data your servers send in response to visitors in Section 6.2. (a) A web-hosting site gets an uptime check about every 15 minutes and, if a new deploy of it does not answer, lavela may roll the site back to a recent earlier deploy on its own. (b) Where lavela offers it, an always-on server (Section 6.2) is checked about every five minutes — a server that is open to the internet by a request to its address, and any other server (one that is not open to the internet, such as a background worker or a database server) by reading its state from our compute provider — and a server that repeatedly does not answer is reported as down. (c) Where lavela offers it, a server that sleeps when idle is not checked unless you switch on, for that server separately, a check that wakes it (off unless you switch it on; you choose every hour, every six hours, every day or every three days, and it is set to every day when you first switch it on); the time the server is awake because of that check is billed as awake time (Section 6.2), and the console shows what one check costs before you switch it on. (d) When a web-hosting site (and, where lavela offers it, a server) is reported as down, and again when it answers, lavela sends an alert to the notification channels you set up and, where lavela offers it and unless you switch this off in your settings, an email to your account address or to one other address you choose (which you confirm you are entitled to use). lavela may limit how many of these emails it sends, and may not send them while a problem on lavela's own side is affecting many sites at once; an alert can arrive late or not at all, and no alert is a promise that lavela has found every problem. (e) Where lavela offers it, you can ask lavela to roll a server back to the version that was running before the one that failed (the last version of it that deployed successfully and answered before the failed deploy) or, if that deploy is no longer on record but lavela still keeps a saved copy of that version, to the saved copy. A rollback changes the code a server runs, not its data: databases, disks and files written since are not undone, and a newer version may have changed data in a way an older one cannot read. Where lavela offers it, if a newly deployed version of a server does not answer, lavela may switch the server back to the version that was running before the one that failed to answer, without waiting for a request (an automatic operation you authorize in Section 3.1; lavela remains responsible under these Terms, within the limits of Section 12, if it carries it out wrongly — that is, other than as described here, for example by switching to a version other than the one described here, or when the new version was in fact answering; this does not limit Section 3.2A), and will try to tell you; the caution about data above applies to this switch as well.

2.2 What lavela is not. lavela is an operations layer that runs on top of your app. lavela never modifies your source code. lavela does not own, write, or take responsibility for the functionality of the app you build; you do (see Sections 4 and 5).

2.3 Two ways to use lavela. You can use the GUI console (built for non-developers) or the MCP server (built for developers and AI agents). The same actions and the same Terms apply through either interface.

2.4 Changes to the Service. lavela is actively developed. We may add, change, or remove features. If a change materially reduces core functionality you rely on, we will make reasonable efforts to give you notice.

---

3. The Agency / Delegation Grant

This Section is the heart of how lavela works. Read it carefully.

3.1 You appoint lavela as your agent. You authorize and instruct lavela to act on your behalf and at your direction to carry out the operations described in Section 2 — specifically:

• to create, configure, operate, scale, and tear down infrastructure resources (hosting, compute/containers, databases, domains, email, caching, storage, logging, analytics) using lavela's pooled provider accounts or accounts you connect;
• to connect, configure, and operate payment accounts (such as Stripe Connect) and advertising accounts that you authorize, and to manage advertising campaigns you ask us to run;
• to take routine operational actions to keep your app running — for example monitoring, security scanning, automated rollback/recovery, backups where offered, and generating compliance documents and daily summaries.

3.2 Scope is limited to what you (or your agent) request. lavela acts only within the scope you grant: the actions you, or an AI agent you have connected, request through the console or the MCP server. A request your connected agent makes within the permissions you granted it is handled as a request from your account. The actions lavela carries out at your or your connected agent's request are recorded in an audit log that you can review in the console (Section 9.7 says what may not appear there).

3.2A Confirmation steps and your controls. lavela's own confirmation steps still apply to an agent's requests, and an agent cannot skip them: deleting a project needs the project's exact name; launching an ad, or changing its budget, needs the daily budget repeated; and accepting these Terms in your browser and turning on automatic top-up in the console (Section 6.6) can be done only by you. lavela adds no other confirmation prompts to an agent's requests, so whether your agent checks with you before it acts is up to the agent and its own settings. You control what an agent can do through the permissions you grant it (the approval screen of a browser sign-in lists them; for a manual token you choose them when you create it), and you can disconnect an app or revoke a token at any time under Connect your agent → Manage connections (see Section 3.5): a revoked token stops working at once, and a disconnected app's current access ends within about an hour. Handling a request as yours does not make lavela's own errors yours: a request lavela carries out wrongly, an action nobody requested, or a confirmation step lavela fails to apply remains lavela's responsibility under these Terms.

3.3 lavela never edits your source code. Under no circumstances does lavela modify, rewrite, or commit changes to the source code of the app you built. lavela operates the infrastructure around your code, not the code itself.

3.4 You remain the principal. You are the principal and the decision-maker. lavela acts as your delegate. You are responsible for the instructions you (and any AI agent you connect) give, and for the lawfulness and consequences of the operations you direct (subject to Sections 4, 5, 11, and 12).

3.5 Revocation. You may revoke or narrow this authority at any time — by changing your settings, disconnecting an account, or closing your account. Revocation is not retroactive: it does not undo actions lawfully taken before we received it, and it does not relieve you of fees already incurred (see Section 6). On revocation or account closure, lavela will, on request, tear down what it provisioned for you and hand back the accounts you connected (see Sections 7 and 15).

3.6 Connected accounts remain yours. Where lavela connects an account that belongs to you (for example your Stripe Connect account or an ad platform account), that account remains yours. You can disconnect it, and we will hand back control on request.

---

4. Your Responsibilities and Acceptable Use

4.1 Your app is yours. You own — and are solely responsible for — the app you build, its content, its data, its users, and its compliance with all laws that apply to it (including consumer-protection, tax, data-protection, licensing, and industry-specific rules). lavela provides tools and operations; it does not assume responsibility for your app's legality, accuracy, or fitness for any purpose.

4.2 Acceptable use. You agree not to use the Service, and not to direct lavela to provision or operate infrastructure, for any of the following:

• anything illegal, fraudulent, infringing, or that violates the rights of others;
• malware, cryptomining, spam, phishing, denial-of-service, or other abusive or deceptive activity;
• content that is unlawful, that sexually exploits minors, or that violates a third party's intellectual property or privacy;
• circumventing usage limits, safety guardrails, rate limits, or trust controls, or attempting to access another customer's data or resources;
• using payment or advertising connections to launder money, evade sanctions, or run prohibited or high-risk activities barred by the relevant provider; or
• any use that could cause lavela's shared/pooled provider accounts to be suspended, banned, or rate-limited to the detriment of other customers.

4.2A Automatic stops for abuse. lavela may stop a server automatically — only that server, never the account's other servers — if lavela's automatic checks find the signs of cryptocurrency mining (a server open to the internet that keeps its processor busy with no visitors) or of flooding other systems (outgoing traffic, including responses to your visitors, at an hourly rate far above what an ordinary app sends — judged by how much a server sends in an hour, not by the day's total). This applies to an account that has only the welcome credit (before its first paid top-up, or again once every paid top-up has been refunded in full) and to a new payer: an account whose paid top-ups total less than US$50 after refunds, whose first paid top-up is less than 30 days old, or that has had a top-up refunded or disputed. We email you when it happens. A server stopped this way is not billed while it stays stopped (its disks are); no request, start, redeploy or top-up lifts it, and a person at lavela reviews it when you write to support@lavela.dev.

4.3 Why some limits exist, and the welcome credit. Because lavela runs your compute inside pooled, shared provider accounts, abuse by one customer can harm everyone. We therefore apply safety guardrails — for example limits on how large a resource a newer or less-verified account can spin up, and rate limits — and we may add other abuse controls. These are safety controls, not spending caps — your spending is governed by your balance and the fees in Section 6. Accounts using only the welcome credit — before their first paid top-up, or again once every paid top-up has been refunded in full — can run up to two servers, each of the 512 MB size (Section 6.2), which share the welcome credit and the shared pool of Section 6.5: while that pool is full, a new server or build may have to wait. The data transfer that lavela bills (Section 6.2) is taken from the welcome credit as it is used, like any other usage (Section 6.5). On a day (UTC) when the data an account's servers have sent passes 2 GB, lavela may email you, once that day, to say so and to tell you what data transfer lavela has counted as costing you this month so far; 2 GB is the point for that email, not a free allowance. (For this, data a server sends on its own counts (Section 6.2); data sent by builds, database servers and cache servers does not.) lavela does not stop a server because an account has sent more than 2 GB in a day. Data transfer is paid from your balance like any other usage, and when the balance is used up Section 7.1 applies. Separately, Section 4.2A lets lavela stop a server whose outgoing traffic shows the signs of flooding other systems.

4.4 Identity and anti-fraud. To add funds, run larger compute, advertising, or payments, you may be required to add a payment card (card verification may place a small temporary authorization that is released) and to complete identity verification (such as Stripe KYC). Larger compute limits may depend on such verification; the console or the MCP server tells you when you reach a limit on your account. We may decline, limit, suspend, or unwind any action — including a top-up, an automatic top-up, or a welcome-credit grant — we reasonably believe is fraudulent, abusive, or a risk to lavela's provider accounts or other customers.

4.5 Cooperation. You agree to provide accurate information and to keep your billing details current.

4.6 Variables, secrets and public build settings. Where lavela offers it, you can give lavela variables for your app in the console, through your AI agent, or with our command-line tool, which uploads the variables of a local .env file from your computer after you approve the upload in your browser (you can leave variables out). A secret is stored with our compute provider, given to your servers when they start, and is not shown back to you by the console or the MCP server, which show only its name. A public build setting (a name that starts with a framework's public prefix such as VITE_ or NEXT_PUBLIC_) is stored in lavela's database, can be read by you, is passed to your app's build, and is normally compiled into the files your app sends to every visitor — anyone who visits your app can read it. Never put a secret in a public build setting. lavela's checks (names, sizes and the recognition of common key formats) are a safety net, not a guarantee. Unless lavela's own error caused the exposure (see Section 3.2A), you remain responsible for what you store, for replacing a key that was exposed (revoke it with the provider that issued it), and for the values your AI agent chooses to send (Section 8.3).

---

5. Intellectual Property

5.1 You own your code and content. As between you and lavela, you retain all right, title, and interest in your app's source code, content, data, trademarks, and other materials ("Your Materials"). lavela claims no ownership of Your Materials.

5.2 License to operate. You grant lavela a limited, non-exclusive license to access, host, process, transmit, and operate Your Materials only as necessary to provide the Service and carry out the delegated actions you request. This license ends when you remove the materials or close your account, except for residual copies in routine backups or logs that age out in the ordinary course, and as needed to comply with law.

5.3 lavela owns the platform. lavela owns all right, title, and interest in the Service itself — the console, the MCP server, the APIs, the workflows, the templates, the software, and the lavela name and marks ("Platform IP"). These Terms grant you a limited, non-exclusive, non-transferable right to use the Service; they do not transfer any Platform IP to you.

5.4 Feedback. If you send us suggestions or feedback, you grant us a perpetual, royalty-free right to use it to improve the Service, with no obligation to you.

---

6. Fees, Prepaid Balance, and Payments

This Section states exactly how lavela makes money from you. The Credits & Refunds Policy at /credits is part of these Terms and gives the operational detail (amounts, notices, and how to request a refund). If the two ever conflict, this Section controls.

6.1 Prepaid balance, no subscription. lavela uses a prepaid balance ("wallet") in US dollars. You add funds to your wallet, and the services you run are paid from it as you use them. There is no subscription and no monthly platform fee. lavela does not charge your card for compute except when you (or an automatic top-up you have turned on under Section 6.6) add funds — or, for an account still on the older monthly card plan, as Section 6.13 says.

6.2 Server pricing. A server's price depends on its size (shared vCPUs and memory) and on whether it is asleep or awake. Prices are per server per calendar month and the same in every region:

A server is billed by the second and deducted from your balance as it accrues; each calendar month's price is spread over that month's own seconds. A server that sleeps when idle sleeps when nobody is using it and wakes on the next request, after a short start-up delay. Each second it exists, except while it is stopped or paused (below), is billed at one of its size's two prices: the asleep price while it is asleep, and its always-on price while it is awake. It is awake from the moment a request wakes it until it is back asleep, which happens a few minutes after the last request: a single request keeps it awake for a few minutes, and requests every few minutes (for example from an uptime monitor) can keep it awake all the time. Any request wakes it, including those lavela makes, such as the check that a new deploy answers or a health check you or your agent ask for. Where lavela offers it, a wake-up check you switch on (Section 2.1A) wakes it too. Awake time is the time lavela's metering observes the server running; time it does not observe is billed at the asleep price, and there is no minimum charge per wake. So no second of a server that sleeps when idle costs more than the same second of the same server kept always on, and it never costs more than the same server kept always on: a whole month of it costs between its size's two prices, depending on how long it was awake (a 512 MB server: US$2 asleep all month, US$2.25 awake 5% of the month, US$3.50 awake 30% of the month, US$7 awake all month), and a server that exists for part of a month pays for that part (for example, 10 days of a 30-day month of a 512 MB server cost US$0.67 asleep and US$2.33 awake). An always-on server — one set never to sleep — is billed its size's always-on price (US$7 a month for 512 MB) for every second its deployed setting is always-on; switching it back to sleeping bills it as a server that sleeps when idle from the switch. Sizes. An account that has only the welcome credit (Section 6.5) runs the 512 MB size. After the account's first paid top-up has settled (Sections 6.4, 6.4A and 6.6) you can choose any size in the table for a new server and change the size of an existing one; every size is still paid from your balance. If every paid top-up is later refunded in full while welcome credit is left, the account has only the welcome credit again: until its next paid top-up settles, you cannot choose a size above 512 MB for a new server or make a server bigger. A server already running at a bigger size when that happens keeps running at that size, billed at its prices, until you change its size, stop it or delete it; redeploying it follows the welcome-credit limits, so its size must first be changed to 512 MB. A size change takes effect at once (the server restarts) and is billed by the second from the change at the new size's prices — metering runs in short intervals, so the interval in which you change the size may be priced at the new size. Changing a server back to 512 MB is always possible, with no top-up and even before you accept a later version of these Terms, except that a stopped or paused server must be started first, and a running build of its service must finish first. When you stop a server, it stops answering within a couple of minutes and cannot be reached until you start it again, and it is not billed from the stop, always-on or not. A server lavela pauses or stops (for example when your balance runs out — see Section 7) is not billed while it stays paused or stopped, and no server is billed while your account is paused; but if a pause does not take effect and the server keeps running while your account is active, the time lavela's metering observes it running is billed as awake time, at its size's always-on price. Billing ends when you delete it.

Builds are included in the server price: up to 60 builds a month for each server you have (counted when a build starts, including the server that build creates, and at least 60 per account), and at most 10 builds per account per day — months and days are UTC calendar months and days — and each build may run up to 30 minutes. While your account has only the welcome credit (before its first paid top-up, and again once every paid top-up has been refunded in full while welcome credit is left — the accounts limited to the 512 MB size), it may start at most 20 builds a month in total (still at most 10 a day), each running up to 10 minutes; its next paid top-up lifts these to the limits above. The limits a build runs under are fixed when it starts, and every build that starts counts, a failed one included — except a build that fails only because lavela's own build machine ran out of disk space or memory (decided from lavela's own records), which does not count toward these limits, for up to 10 such builds in any 24 hours; further ones count. An account that has only the welcome credit may have to wait for a new build while the shared pool is full (Section 6.5). Where lavela offers it, a build beyond the included ones that you start in a way that shows you its price per minute first is not refused; it starts and is billed as described here, and is called a billed build in this paragraph. Until lavela offers billed builds there are none: nothing in this paragraph that speaks of a billed build applies, nothing is charged for one, and a build beyond the included ones is refused. Each month you can start up to 60 billed builds for each server you have (40 in all for an account with only the welcome credit), and still at most 10 builds a day. A billed build is billed by the second for the time lavela's build machine runs, measured from lavela's own records and up to the build's time limit (the time counted can be up to about 20 seconds longer than the build itself ran). The price per minute of a billed build is shown to you before the build starts, and is also listed at /pricing; the build prices listed there form part of these Terms. That price will never be more than US$0.01 per minute unless you accept a later version of these Terms; below that limit, Section 6.12 applies to a change. If the price shown to you before the build starts and the price listed at /pricing when the build starts are not the same, the lower of the two applies to that build; in every case the price is never more than US$0.01 per minute, unless you accept a later version of these Terms. A billed build starts only in a way that shows you its price first: a build that would be beyond the included ones but is started in a way that shows no price first (for example with the command-line tool, or by uploading a folder in the browser, including from a deploy link that your agent gives you) is refused, and nothing is charged for it. A build within the included ones is not affected by how it is started. The price of a billed build is taken from your balance (from the welcome credit for an account that has only that), like the other usage in this Section. A billed build is billed even if your code makes it fail or it reaches its time limit, and even if the deploy that follows a finished build fails; a build that fails only because of lavela's own build machine or image storage, or that is cancelled because its project was deleted, is not billed. A billed build does not start if your available balance does not cover the build's time limit at that price, or if you have an unpaid amount (Section 7.1). Whether a build is included or billed is fixed when it starts. Builds end for the month when the included ones are used up and, where lavela offers billed builds, the billed ones too. Further builds are refused until the count resets, and a build still running at its time limit is stopped (it fails, and nothing is deployed).

One-off jobs and scheduled jobs are billed by the second for the time they run, at the always-on price of a 512 MB server (US$7 a month), whatever the size of the server they belong to. A one-off job still running after about three minutes keeps running in the background on its own 512 MB server, which from then on is billed like a server that sleeps when idle — at its always-on price while the job runs and at its asleep price after it ends — until that server is deleted; delete it once the job is done. Data transfer out of your servers is billed by use, by the region the traffic leaves from: US$0.023 per GB in North America and Europe, US$0.046 per GB in Asia-Pacific (Tokyo included), Oceania and South America, and US$0.138 per GB in India and Africa. It includes your servers' responses to visitors and, where lavela offers it, the data your servers send on their own — for example files they upload to other services or calls they make to other services. Data that your own servers exchange with each other over lavela's private network, and data used while building, is not billed. Data transfer is billed from the first byte, with no free amount, for every account; for an account that has only the welcome credit it is taken from the welcome credit (Section 6.5). Disks (persistent volumes) cost US$0.1725 per GB per month, billed for as long as the disk exists, whether or not its server runs — including while the server is stopped. These prices are shown in the console or through the MCP server before you create a resource. That service price is a bundled price that includes lavela's margin; we do not itemize that margin, and we do not claim that any price is "at cost." New servers run in Tokyo. A server run from an image can be placed in another available region when it is created, and a server attached to a disk runs in that disk's region (a disk, too, can be created in another available region); builds always run in Tokyo. A server keeps its region when it is redeployed, unless the redeploy attaches a different disk, which moves it to that disk's region. Metering runs slightly behind real time, so a small amount of usage can be recorded after the fact. The current prices are listed at /pricing.

6.3 What is billed from your balance, and what is not.

• Billed from your balance: servers (the prices in Section 6.2), builds beyond the included ones, where lavela offers them (Section 6.2), one-off and scheduled jobs, data transfer, disks, and any other resource that shows a price before you create it.
• Not separately billed unless the console states otherwise: supporting resources lavela provisions for your compute (such as caching, object storage, and logging/error monitoring), and web analytics.
• Not charged today; if that changes, passed through at provider cost (no lavela markup): transactional email and domains. Domains are connect-only where applicable (you own the domain).
• Advertising: see Section 6.9. Your balance cannot currently be used to pay advertising platforms.

6.4 Adding funds (top-ups). You can add funds by card, processed by Stripe — a card issued in the United States or Canada, or in South Korea where lavela offers it, pays lavela directly (Section 1.4). A direct top-up is charged in US dollars. The minimum top-up is US$10. Each US$1 of top-up adds US$1 of paid balance — lavela charges no top-up fee. For a direct top-up with a card issued in South Korea, lavela adds Korean value-added tax (VAT) of 10% to the card charge and shows it separately before you pay — for example, a US$10 top-up is charged US$11 — and the full amount of credit is added to your balance; the tax is never taken out of the credit (Section 6.8). Paid balance does not expire and there is no inactivity fee. If you hold welcome credit, a first paid top-up of US$10 or more with a card that pays lavela directly can also earn the one-time card bonus (Section 6.5A). Your card issuer may require additional authentication (such as 3-D Secure), and a top-up is credited only after the payment succeeds. Your bank may charge currency-conversion or foreign-transaction fees, and a Korean debit card may be declined unless overseas payments are turned on with its issuer; those are between you and your bank. We may set or change per-top-up or per-account limits for risk reasons; the current limits are shown before you pay. Daily limit. An account can add at most US$1,999 (of credit) in total from the top-ups it starts on one UTC day, counting every top-up however it is paid — by card, through Stripe's Link checkout where offered, and automatic top-ups — including top-ups still in progress (an unfinished checkout counts until it is paid, canceled or expires, up to 24 hours). The limit resets at 00:00 UTC, and a refund does not restore it. A top-up that would go over it is declined before any charge, and the console shows how much you can still add today.

6.4A Paying through Stripe's Link checkout (only where offered). Where lavela offers it — and lavela may stop offering it at any time — funds can also be added through Link, Stripe's merchant-of-record service ("Sold through Link"), with a card or payment method that checkout accepts: Link sells you the credit, and its terms and privacy policy, shown at checkout, apply to that payment, while these Terms continue to govern the Service and how the credit is used; Link adds the VAT, GST or sales tax of your country on top of the price of the credit at checkout and remits it, and the full amount of credit is added to your balance; the checkout may show the price in your local currency, converted by Stripe — your credit is always the US-dollar amount shown in lavela; your card statement shows LINK.COM* LAVELA; if Link refunds such a purchase under its own policy within 60 days of it, the refunded credit leaves your balance, which can go below zero if you already used it (Section 7 then applies); where Link does not handle the tax for your billing country, the payment is not added to your balance and is refunded in full; and the automatic top-up in Section 6.6 is not available for these purchases.

6.5 Welcome credit (promotional). New accounts may receive a one-time US$3 promotional compute credit — about two weeks of one 512 MB server that is always on or always awake, and up to about one and a half months of one that sleeps almost all the time, at the prices in Section 6.2 — as described in the Credits & Refunds Policy. In summary: it is a promotional offer that may end, or change for future sign-ups, at any time without notice; it is given only to eligible new accounts (the Credits & Refunds Policy, Section 2, says which); it is limited to one per person (we check your verified email address and may use other signals to enforce this); it can be used only for lavela compute, and while only welcome credit is used — before the account's first paid top-up, or again once every paid top-up has been refunded in full — the account runs up to two servers, each of the 512 MB size (Section 6.2 covers a bigger server already running then); it is not refundable, has no cash value, and cannot be transferred or sold; in this version it does not expire; and we may revoke it, including any unused amount, if we reasonably believe it was obtained or used through abuse, fraud, multiple accounts, or a breach of these Terms. Welcome credit is used before your paid balance. The welcome credit pays for all of the account's servers together, so two servers that stay awake use it up in about half the time one server does. Servers on the welcome credit run in a shared pool of fixed size: while that pool is full, lavela may refuse a new server or a build of such an account until room frees up or you add funds; a server you already run is not affected, and the credit you were given stays on your account, subject to the rest of this Section. An account that holds welcome credit can also earn a one-time card bonus, which is added to it (Section 6.5A). Nothing in this Section obliges lavela to offer promotional credit to anyone.

6.5A Card bonus (promotional). An account that holds welcome credit (Section 6.5) earns one additional US$2 of promotional credit, once per account, the first time either (a) it saves a card that pays lavela directly (Section 1.4) while it still has welcome credit left, or (b) a paid top-up of US$10 or more paid directly with such a card settles on the account, whichever comes first; after the welcome credit is used up, it comes with the first such top-up. For a card that pays lavela directly, the card bonus is given once per card: the card must be a credit or debit card — not a prepaid card or a card whose type is unknown — that has not already earned this bonus on another account, and if lavela cannot read the card's details for this check, the card bonus is not given. To check a card, lavela stores a one-way fingerprint (hash) of it and its type, never the card number — the Privacy Policy, Section 2.9, says how and for how long. The card bonus is added to your welcome credit and is welcome credit in everything Section 6.5 says: it is used before your paid balance, can be used only for lavela compute, has no cash value, is not refundable and cannot be transferred or sold, does not expire in this version, and may be revoked, including any unused amount, if we reasonably believe it was obtained or used through abuse, fraud, multiple accounts, or a breach of these Terms. lavela may change or end the card bonus for future accounts at any time; card bonus already added stays, except as this paragraph says.

6.6 Automatic top-up (you can turn it off at any time). Automatic top-up charges your saved card when your balance is low, so your servers keep running. Automatic top-up is never turned on by a switch that is already set to on. It turns on only when you take a step that names it: ticking the box in the console's card window where that box names automatic top-up and states the balance level, the amount and the tax that would be added (a first card's box also states the limit of 3 attempts a day), which also turns automatic top-up on when the card is saved; pressing the button that turns it on, where a card form has two buttons; ticking the separate box on the Add funds screen, which starts unticked; or confirming it in the console after the card is saved. Where the card window's box names automatic top-up, you must tick it to save a card in that window, so a first card is saved with automatic top-up on, and you can turn it off right after you save it. When you add a card while automatic top-up is already off, or where the box does not name automatic top-up, saving the card does not turn it on. You can turn it off at any time in the console, including right after you save the card, and turning it on again later needs your separate confirmation. When you save a card, lavela records the exact wording you were shown (including the sentence next to the box, where there is one), the screen it appeared on, the numbers shown to you, the time, and your IP address and browser, as evidence of what you agreed to (Privacy Policy, Sections 2.6 and 8); where the box carries the agreement, the record also shows that the box was unticked when it appeared and that you ticked it, and where a card form has two buttons, which one you pressed. The IP address and browser information in this record are erased when we delete your account, as a step of that deletion; what you agreed to, and when and how (the hash of the wording, the time, and what you ticked or pressed), is kept for three years after your account is closed in case of a dispute. While it is on, you authorize lavela (through Stripe) to charge your saved card the amount you chose (plus any tax shown to you) each time your available balance falls below the level you chose. The balance level and the charge are named in the box when you save a card — for a first card they are the console's suggestion for the servers you run, and when you change the card while automatic top-up is on they are your current settings — and you can change both in the console, within the range shown there (today a balance level of US$1–US$100 and a charge of US$10–US$100, the charge at least US$5 more than the level); changing them needs your confirmation again. We make at most 3 automatic charge attempts per day (UTC) — declined and canceled attempts count — so the most that can be charged in a day is 3 times your chosen amount, plus tax. For a card issued in South Korea (where lavela offers it) the tax is 10% Korean VAT: an automatic top-up of US$10 is charged as US$11, and the wording you are shown when you turn automatic top-up on states the charge with the VAT included. If you still have welcome credit, the first automatic charge waits until that credit, a card bonus included, is fully used. An automatic charge that the daily top-up limit in Section 6.4 would exceed is not attempted; it is not counted as a failed charge and automatic top-up stays on.

There is no fixed monthly limit — instead, a pause for your confirmation. If the automatic charges of a calendar month (UTC), tax included, would grow beyond the larger of US$100 and 1.5 times what your running servers cost for a month at their always-on prices — or, for an account whose paid top-ups total less than US$50 after refunds, or whose first paid top-up is less than 30 days old, beyond the larger of US$100 and that same monthly cost — lavela does not make that charge, pauses automatic top-up and emails you; nothing is taken for the paused charge. Automatic top-up continues only when you sign in and press "Continue automatic top-up" on the wallet page (the email has no confirmation link); after you continue, that month's automatic charges can grow by up to the same limit again, on top of what has been charged so far, before it pauses and asks again. If lavela cannot read what your running servers cost when it needs to judge a charge, it does not make that automatic charge.

If an automatic charge needs your bank's authentication, we email you a link to confirm it; if it is not confirmed within 72 hours, the charge is canceled — nothing is taken — and later automatic top-ups can go ahead. You can turn automatic top-up off at any time in the console; turning it off stops future automatic charges and cancels any automatic charge still waiting for your confirmation, but does not cancel a payment that is already being processed. If an automatic charge is declined or canceled unconfirmed, or an automatic charge is paused as above, we will tell you by email, and your services then follow Section 7 if your balance runs out. If your card issuer declines an automatic charge in a way that means the card can't be charged again, or 3 automatic charges in a row are declined, or canceled because they were not confirmed with your bank within 72 hours, we turn automatic top-up off and tell you by email; you can turn it on again in the console (with another card, if your card issuer declined that one). Any refund of a top-up — requested by you (Section 6.7), or made by lavela or by Link (Section 6.4A) — also turns automatic top-up off, and so does a payment dispute (Section 7.3). Each charge appears in your wallet's billing activity.

6.7 Refunds. You may request a refund of your unused paid balance at any time, as set out in the Credits & Refunds Policy. In summary: the refundable amount is the unused paid balance from top-ups that have settled, less usage already incurred but not yet deducted, applicable tax, amounts held for running resources or pending payments, amounts already refunded, and amounts subject to a payment dispute. Refunds go to the original payment method; lavela charges no refund fee and applies no fixed deadline for requesting one. Refund requests are reviewed by a person and are not instant; your bank's processing time varies. Promotional credit is never refundable. Usage already consumed is generally not refundable, but we will review and correct billing errors, duplicate charges, and services we did not provide. A refund of a top-up that carried tax — one bought through Link (Section 6.4A), or one paid directly with a card issued in South Korea (Section 6.4) — returns the refunded credit together with its share of the tax you paid. Requesting a refund also turns off automatic top-up (Section 6.6); you can turn it back on afterwards. Nothing in these Terms limits any refund right you have under law that cannot be waived — if you are in South Korea, this includes the right to withdraw, within 7 days, from a purchase of credit you have not used, and the refund of unused paid balance described here is available well beyond those 7 days.

6.8 Taxes. Prices and top-up amounts are stated exclusive of tax. If lavela adds tax to a payment, it is shown separately before you pay and added to the card charge; it is not deducted from the amount credited to your balance. For a direct top-up with a card issued in South Korea (where lavela offers it), the tax lavela adds is Korean VAT at 10% (Section 6.4). Where lavela does not add a tax, that is not a statement that the purchase is exempt from it. For a top-up through Stripe's Link checkout (Section 6.4A), Link calculates, collects and remits the tax on that purchase. You are responsible for any taxes that apply to your purchases from lavela other than taxes on lavela's income, and you are solely responsible for the taxes arising from your business and your sales to your customers.

6.9 Advertising commission (~10%). If you run advertising through lavela, lavela charges a commission of approximately 10% on the advertising spend in the ad account lavela set up for you (every campaign in it, including any you run there yourself). The current rate is listed at /pricing. The commission is charged to your card on file once a month, for the previous month, and is separate from your wallet balance; advertising spend itself is paid to the advertising platform under your account with that platform, under the campaign budgets you (or your agent) approve and that platform's budget rules. Ad commissions already incurred are non-refundable, except for billing errors.

6.10 lavela takes 0% of your own sales. This is important and we mean it precisely:

• When your customers pay you, those payments are processed through your own Stripe Connect account. You are the merchant of record for your sales; the funds settle to you in full.
• lavela is not a party to those transactions, does not touch that money, and charges no per-transaction fee and no percentage of your revenue. lavela's fees are only those in this Section 6. (Separately, lavela is the merchant of record for its own charges to you — top-ups and ad commissions — except top-ups bought through Stripe's Link checkout, where Link is (Section 6.4A); neither makes lavela a party to your sales to your customers.)

6.11 Payment authorization. You authorize lavela (and its payment processor, Stripe) to charge your payment method for the top-ups you confirm, for automatic top-ups while you have them turned on, for ad commissions and, for an account on the older monthly card plan, for that plan's monthly advance charge and its month-end settlement charges (Section 6.13). A top-up through Stripe's Link checkout is charged by Link under the authorization you give at that checkout. Each top-up you confirm is a separate payment you approve at that time.

6.12 Changes to prices. We may change service prices, promotional terms, or the commission rate prospectively. For an increase in a price you are already paying, we will give you at least 14 days' notice by email or in the console before it applies; the new price applies only to usage after it takes effect, never to balance use that has already happened. If you do not accept a change, you can stop the affected resources and request a refund of your unused paid balance under Section 6.7.

6.13 Older monthly card plan. If your account is billed under lavela's older monthly card plan — a monthly advance charge to your card — instead of from the prepaid balance, lavela will not move it onto the wallet without telling you first. On that plan, your card is charged at the start of each calendar month (UTC) for that month's estimated use of your servers and disks. After the month, that charge is settled against the use lavela's metering recorded — your servers and disks, plus data transfer and one-off and scheduled job runs as used: the difference is refunded to your card or charged to it (a difference under US$0.50 is neither). The Billing page shows the month's use so far and the payments on that plan. On that plan, a server is billed by its size for the time it runs (not while it is asleep or stopped), at the plan's service price shown for each such server in the console — not the prices in Section 6.2; a job run is billed the same way for the time it runs; a disk is billed by its size for the time it exists, and data transfer by use, also at the plan's service price. These are bundled prices that include lavela's margin. While an account stays on that plan, a monthly payment that fails follows that plan's schedule: we email you when it fails; your servers are suspended 5 days after the failure (14 days for a verified or established account) and we email you again; and if the payment is still not made, those servers and their data are deleted 30 days after the failure. Section 7.1(4) (stopped servers kept until you delete them) applies to the prepaid balance, not to this plan.

---

7. Low Balance, Stopping, and Data Retention

Because services are paid from a prepaid balance, lavela does not chase you for unpaid invoices. Instead, when your balance runs low we warn you, give you time, and then stop your servers — keeping them, and your data, until you delete them.

7.1 The sequence. This is what happens when the balance of an account that has servers runs out. It does not apply — your servers stop at once, without the grace period or its emails — if the account has never made a paid top-up and its welcome credit was revoked (Section 6.5) or never granted, if its servers are already stopped or restricted (for example after an earlier run-out, or under Section 7.3 or 15.3), or if a fault keeps lavela from starting the grace period while your balance is already below zero.

1. Low-balance notice. When your remaining welcome credit or balance reaches US$2 or less, we send you an email — unless an automatic top-up (Section 6.6) is already on its way to refill it.
2. Balance used up — grace period. When your available balance (promotional and paid) runs out, we email you with the exact time your servers will stop, and remind you about 12 hours before that time. Your servers keep running for a grace period of 48 hours — unless the unpaid amount during the grace period grows beyond US$5 or half of your paid top-ups after refunds, whichever is larger: then lavela stops them right away instead and emails you why. While your account is using only welcome credit, usage during the grace period is at lavela's cost, up to US$1 in total: if the usage lavela absorbs in that grace period grows beyond US$1, lavela stops your servers right away instead and emails you why. If your account has paid balance, usage during the grace period and usage recorded late by metering may take your balance below zero; that amount is settled from your next top-up — an automatic top-up (Section 6.6) included — and lavela will not otherwise charge your card to collect it. A top-up during the grace period that brings your balance back above zero keeps your servers running; a smaller one reduces the unpaid amount, but the servers still stop when the grace period ends.
3. Stop (data kept). At the end of the grace period (or once the unpaid amount passes that limit), lavela stops your servers (a stopped server is not billed while it stays stopped — Section 6.2). Your data, volumes, and databases are kept, and you can start the servers again from the console or MCP server after you add funds.
4. Kept until you delete them — with one exception. Servers stopped for insufficient balance — with their disks and data — are kept until you delete them; lavela does not delete them automatically (an account still on the older monthly card plan follows that plan's schedule instead — Section 6.13). Their disks keep being billed while they exist (Section 6.2), so delete what you no longer need. The exception is an account that has only the welcome credit (before its first paid top-up, or again once every paid top-up has been refunded in full): lavela removes the machine of a server of such an account that stopped because the credit ran out, or that you stopped yourself and have not started since, after telling you. It emails you first, and removes the machine 7 days after the latest of: the day the server stopped (for a server you stopped yourself, the day it had been stopped for 14 days), the day you accepted these Terms, and the day of that email; on day 5 of the 7 days it reminds you. The server's settings, built image and variables are kept 30 more days: if you add funds and press "Start again" in that time, the server is recreated as it was. 5 days before the 30 days end lavela emails you again; after that it deletes the variables and the built image, and "Start again" rebuilds the server from your repository, so you set the variables again. lavela does not remove a server this way if it has a disk or is stopped under Section 4.2A. Apart from this exception, if lavela ever introduces automatic deletion of stopped servers, it will do so only through a change to these Terms, and we will email you before anything is deleted.

7.2 Automatic top-up and card problems. If automatic top-up is on and a charge succeeds, your balance is refilled and nothing stops. If a charge fails, needs authentication (and is canceled if not confirmed in time — Section 6.6), or automatic top-up is paused for your confirmation (Section 6.6), you are notified and the sequence in 7.1 continues from wherever your balance stands.

7.3 Disputes, chargebacks, and fraud. If you dispute a top-up with your card issuer — a chargeback, or an inquiry the issuer opens before one — whether you paid lavela directly or bought the credit through Link (Section 6.4A), lavela may immediately hold your whole wallet while the dispute is open and until we resolve it with you after its outcome, which can take weeks: your servers stop without a grace period, even if balance is left (the email we send may say your balance ran out and suggest adding funds — while the hold lasts, funds you add are held too, so contact support@lavela.dev instead), your balance cannot be spent, refund requests for your account are held, and automatic top-up is turned off. Data is kept as in 7.1(3)–(4). A hold is not a seizure: balance unrelated to the disputed payment stays yours, and once the dispute is resolved you can use it or request its refund under Section 6.7. We never pay the same amount back twice: an amount returned to you through a dispute is not also refundable under Section 6.7. A dispute of another payment to lavela (for example a charge under the older monthly card plan, Section 6.13) may also stop your servers at once. Suspected fraud is handled under Section 4.4.

7.4 Other amounts you owe. If an amount you owe lavela outside your wallet (for example, an ad commission) is not paid, we will notify you and may pause the related service (such as advertising campaigns) until it is resolved.

7.5 Inactive resources. Apart from preview environments — a pull request's own deployment and database branch, which lavela deletes when the pull request is closed, or about 72 hours after the pull request was opened or last pushed to (about an hour after a failed build) — and the machines of stopped servers of an account that has only the welcome credit (Section 7.1(4)), lavela does not delete your resources because they are inactive, and it does not stop a server because it is inactive (a server that sleeps when idle wakes on the next request — Section 6.2). If we ever start removing other resources for inactivity, we will do so only through a change to these Terms (Section 14), and we will email you before anything is removed.

7.6 Export before deletion. You can request an export of your data throughout (Section 15.5). If you do not intend to add funds, request it promptly.

---

8. Third-Party Services and Subprocessors

8.1 lavela runs on third-party providers. lavela provisions and operates your infrastructure using third-party services ("Subprocessors"), currently including:

• Supabase — sign-in and lavela’s own application database
• Vercel — web hosting and CDN
• Fly.io — compute and containers
• Neon — Postgres databases
• Resend — transactional email
• Stripe / Stripe Connect — payments, your connected accounts, and lavela’s own billing (and, for top-ups through Stripe’s Link checkout, Link, LLC)
• Inngest — background and scheduled jobs (an open-source Inngest server run by lavela on Fly.io)
• Cloudflare — DNS, R2 object storage, encrypted backups of lavela’s own database, and inbound-email routing
• GitHub — reading your repositories when you connect GitHub
• Google — sign-in with Google, if you choose it
• DeepSeek — server-side background AI for summaries, compliance drafts and stack detection
• Plausible — privacy-friendly web analytics (visitor and pageview counts) for lavela’s public homepage and guide and, if you turn it on, for your app
• Upstash — Redis cache and rate limiting
• Axiom and Sentry — logging (the logs of every server lavela runs) and error monitoring (only if you turn it on)

This list is the authoritative subprocessor list and is kept identical to the list in the Privacy Policy, which also gives each provider's country, the data it receives and how long it is kept.

8.2 You are bound by provider terms for your connected accounts. Where you connect an account that is yours — for example Stripe / Stripe Connect (you are the merchant of record) or an advertising platform — you are also bound by that provider's terms and policies for that account, and you are responsible for complying with them. lavela operates those connections at your direction but is not a party to your agreement with the provider, and is not responsible for the provider's decisions (for example a payout hold, an account review, or a policy enforcement by Stripe or an ad platform).

8.3 Your own AI agent. If you use lavela through an AI agent such as Claude or Cursor, most in-conversation generation happens on your side, under your relationship with that AI provider. You are responsible for what your agent instructs lavela to do.

8.4 Provider changes and your right to notice. Subprocessors may change. If you are an EU/UK controller of personal data, the advance-notice and objection process in Section 9.5 applies to new subprocessors. For all users, the current list is maintained in this Section and in the Privacy Policy.

---

9. Data, Privacy, and Data Processing

9.1 Roles. lavela is the data controller for your account and platform data (your identity/email, projects, provisioning configuration, module status, usage/metering, audit logs, connected-account identifiers, and the IP + timestamp of your consent). lavela is a data processor for the data and content it provisions and operates on your behalf; for that data, you are the controller.

9.2 Connected-account identifiers, not card numbers. lavela stores identifiers for your connected accounts (for example a Stripe account ID). lavela does not store your full payment card numbers — Stripe holds those. What lavela keeps about a card you save is limited to its brand, last four digits, expiry month and year, issuing country and type, a one-way hash of its fingerprint, and Stripe's reference to it (Privacy Policy, Sections 2.5 and 2.9).

9.3 Privacy Policy. Our handling of personal data is described in the Privacy Policy, which is incorporated into these Terms by reference. We address GDPR (EU) and CCPA (California) rights, including access, deletion, and export, the lawful basis for processing, and our commitment not to sell your personal data.

9.4 Data processing agreement (DPA). Where lavela processes personal data on your behalf (so that you are the controller and lavela is your processor), lavela will provide a data processing agreement on request — contact legal@lavela.dev. It will contain the terms GDPR Article 28 requires. If a data processing agreement signed with you conflicts with these Terms with respect to processing of personal data on your behalf, the signed agreement controls.

9.5 Subprocessor authorization and objection. You authorize lavela to use the subprocessors listed in Section 8.1. If you are an EU/UK controller, lavela will give you advance notice of an intended addition or replacement of a subprocessor by email to your account address, and you may object on reasonable data-protection grounds within the window stated in the data processing agreement we provide on request (Section 9.4); that agreement governs what happens if you object.

9.6 Security-incident / breach notification. If lavela becomes aware of a personal-data breach affecting personal data it processes on your behalf, lavela will notify you without undue delay after becoming aware, with the information reasonably available, consistent with applicable law (GDPR/CCPA) and as further specified in any data processing agreement signed with you, so that you can meet your own notification obligations.

9.7 Audit log. The actions lavela carries out at your or your connected agent's request are recorded in an audit log available to you in the console, for transparency and your records. An automatic rollback of a web-hosting site (Section 2.1A) is not recorded there; other automatic actions lavela takes on its own (such as, where lavela offers it, an automatic rollback of a server), and a connection you complete on another provider's page (such as connecting GitHub), may not appear there either. Some requests lavela refuses before acting on them (for example over a rate limit, or before you have accepted the current Terms) are not recorded, and a project's entries are deleted when the project is deleted (Privacy Policy, Section 8).

---

10. Service Availability (No SLA at this stage)

10.1 No uptime SLA or service credits. The Service is currently provided without a contractual uptime commitment (SLA) and without service credits. While lavela's low-balance sequence (Section 7) is deliberately designed to keep your app running, lavela does not guarantee any particular level of availability, and a failure to meet any availability target does not entitle you to service credits. This does not affect your right to a refund of unused paid balance under Section 6.7, or our correction of billing errors. If lavela later offers a formal SLA, it will be published separately and identified as such.

---

11. Disclaimers

11.1 The Service is provided "as is." To the maximum extent permitted by law, the Service is provided "as is" and "as available," without warranties of any kind, whether express, implied, or statutory, including any implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement.

11.2 No guarantee of uptime or results. lavela depends on third-party providers and the internet. We do not warrant that the Service or your app will be uninterrupted, error-free, secure, or free from data loss, or that security scans, monitoring, recovery, compliance documents, or AI summaries will detect or resolve every issue. Compliance documents and AI-generated content are not legal, tax, or professional advice.

11.3 Your app's outcomes are yours. lavela does not warrant any particular business result, revenue, ad performance, or compliance outcome for your app.

---

12. Limitation of Liability

12.1 No indirect damages. To the maximum extent permitted by law, neither party will be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost goodwill, or lost or corrupted data, arising out of or relating to these Terms or the Service, even if advised of the possibility.

12.2 Liability cap. To the maximum extent permitted by law, lavela's total aggregate liability arising out of or relating to these Terms or the Service will not exceed the greater of (a) the total fees you paid to lavela in the three (3) months immediately before the event giving rise to the claim, or (b) USD $100.

12.3 Pass-through and connected-account costs are excluded from the cap basis. For the purpose of 12.2(a), "fees you paid to lavela" means amounts lavela charged you for its services (compute usage deducted from your paid balance, and ad commissions) — it does not include promotional credit, pass-through infrastructure costs or amounts settled through your own connected accounts (which never belong to lavela).

12.4 Carve-outs. Nothing in these Terms limits liability that cannot be limited by law (for example, fraud, willful misconduct, or, where applicable, death or personal injury caused by negligence). Your obligation to pay fees you have incurred, the refund of unused paid balance under Section 6.7, and the indemnity in Section 13 are not subject to the cap in 12.2.

12.5 Allocation of risk. You acknowledge that the fees reflect this allocation of risk and that these limits are a fundamental basis of the agreement between us.

---

13. Indemnification

13.1 By you. You will defend, indemnify, and hold harmless lavela and its personnel from and against any third-party claims, losses, liabilities, damages, and reasonable costs (including reasonable legal fees) arising out of or relating to: (a) your app, Your Materials, or your use of the Service; (b) your violation of these Terms or of any law or third-party right (including a provider's terms for a connected account); (c) instructions you or your connected AI agent gave lavela; or (d) your products, services, sales, or relationship with your own customers.

13.2 By lavela (platform IP). lavela will defend you against a third-party claim alleging that the lavela platform software itself (the console, MCP server, and APIs as provided by lavela, excluding Your Materials, your configuration, and third-party or connected-account services) infringes that third party's intellectual property rights, and will pay damages finally awarded against you (or amounts in a settlement lavela approves) for that claim. This obligation does not apply to the extent a claim arises from Your Materials, your instructions, your combination of the Service with anything not provided by lavela, or your use of the Service in violation of these Terms. lavela's obligations under this Section 13.2 are subject to the limitation of liability in Section 12 (and count toward, rather than sit outside, the cap).

13.3 Procedure. The party seeking indemnification will notify the other of the claim, give the indemnifying party control of the defense (with the other party's right to participate with its own counsel), and reasonably cooperate. The indemnifying party will not settle any claim in a way that imposes obligations on the other party without that party's consent.

---

14. Changes to These Terms and the Versioned Clickwrap

14.1 We may update these Terms. As lavela evolves, we may revise these Terms. When we do, we update the "Last updated" date and the version.

14.2 Versioned consent and re-acceptance. Because lavela acts on your behalf, material changes to these Terms or to the delegation Consent are versioned. When the version changes, we will ask you to re-accept the new version before lavela provisions, deploys or starts anything billed, adds funds (other than by an automatic top-up you already turned on, Section 14.3), or starts or raises ad spend at your request, and we record that acceptance (version, time, IP) as described in Section 1.2. Every change in a new version applies to you from the time you accept it. For price changes, the notice in Section 6.12 applies. For EU/UK controllers, subprocessor additions follow the advance-notice and objection process in Sections 8.4 and 9.5.

14.3 Your choice. If you do not accept a new required version, you may stop using the Service and close your account. Without accepting it, you can still stop or delete your servers, delete a disk, delete a managed resource (a database, cache, storage bucket or error-monitoring project) through your agent, delete a preview environment, turn daily snapshots off on a plain disk or release a public-port or static-egress IP (where those features and resources are available), turn always-on off on a public app server or change a server back to 512 MB (a stopped or paused server must be started first, and a running build of its service must finish first), pause or delete scheduled jobs, pause ads, turn off automatic top-up and request a refund of your unused paid balance (Section 6.7); provisioning, deploying or starting anything billed, adding funds yourself, and starting or raising ad spend at your request wait until you accept it. Always-on cannot be turned off for database or cache servers; you can stop or delete those servers instead. Scheduled jobs you set up keep running until you pause them, and servers lavela paused during a metering fault may be started again when metering recovers. An account that has not accepted the current version of these Terms is billed under the version it accepted. An automatic top-up you have already turned on keeps working under Section 6.6 until you turn it off or Section 6.6 turns it off; it does not wait for you to accept a newer version, and you can turn it off at any time in the console (Section 6.6) without accepting it. Turning it on again waits until you accept. A change in a new version applies to you from the time you accept it; you can ask support@lavela.dev for the text of the version you accepted.

---

15. Term, Termination, and Data Export

15.1 Term. These Terms apply for as long as you have an account or use the Service.

15.2 Termination by you. You may stop using the Service and close your account at any time. Closing your account does not forfeit your paid balance: after outstanding usage and obligations are settled, your unused paid balance is refundable under Section 6.7. Unused promotional credit (the welcome credit, a card bonus included) ends when the account closes.

15.3 Termination or suspension by lavela. We may suspend or terminate your access (a) when your balance runs out, following Section 7; (b) for a material breach of these Terms, including the acceptable-use rules in Section 4; (c) where required to protect lavela's pooled provider accounts or other customers from imminent harm; or (d) if required by law or by a provider. Where practical and lawful, we will give you notice and an opportunity to cure.

15.4 Effect of termination. On termination, your right to use the Service ends. Subject to Section 7, lavela will, on request, tear down what it provisioned and hand back the accounts you connected. Sections that by their nature should survive (including fees already incurred, refunds of unused paid balance, IP, Disclaimers, Limitation of Liability, Indemnification, the DPA, and Governing Law) survive termination.

15.5 Data export and portability. lavela is built for no lock-in. You may request an export of your data at any reasonable time, including during the grace period in Section 7 and while your servers are stopped, by emailing legal@lavela.dev (see Section 9 of the Privacy Policy) — self-serve export tooling in the console or MCP server is planned but not yet available. On account closure, lavela keeps your exportable data available for 30 days before it may be deleted, except where we must delete or retain it to comply with law. Servers stopped for insufficient balance are kept until you delete them (Section 7.1), except as Section 7.1(4) says for an account that has only the welcome credit.

---

16. General

16.1 Governing law and disputes. These Terms are governed by the laws of the Province of British Columbia and the federal laws of Canada that apply there, without regard to conflict-of-laws rules. The parties submit to the courts of British Columbia, Canada for any dispute, except that either party may seek injunctive relief to protect its intellectual property or confidential information in any court of competent jurisdiction. If you are a consumer, nothing in these Terms removes the protection of mandatory consumer laws of the place where you live, or your right to bring a claim there where that law gives you one.

16.2 Entire agreement. These Terms, together with the Credits & Refunds Policy, the Privacy Policy, any data processing agreement signed with you, and any consents you accept, are the entire agreement between you and lavela about the Service and supersede prior agreements on that subject.

16.3 Severability. If any provision is held unenforceable, the rest remains in effect, and the unenforceable provision is enforced to the maximum extent permitted.

16.4 No waiver. Our failure to enforce a provision is not a waiver of it.

16.5 Assignment. You may not assign these Terms without our consent. We may assign them to an affiliate or in connection with a merger, acquisition, or sale of assets.

16.6 Force majeure. Neither party is liable for delays or failures caused by events beyond its reasonable control (including provider outages, internet failures, or acts of government).

16.7 Relationship. lavela acts as your agent only to the limited extent described in Section 3. Nothing else in these Terms creates a partnership, joint venture, or employment relationship.

16.8 Language. These Terms are written in English. We may provide translations or summaries for convenience — such as the Korean summary at the top of this page and the Korean version of the signup consent. If a translation or summary differs from the English text, the English text controls to the extent the law allows.

---

17. Contact

Questions about these Terms? Contact lavela at legal@lavela.dev, British Columbia, Canada (mailing address available on request at legal@lavela.dev). For refunds and billing questions, use support@lavela.dev or console.lavela.dev/support.

---

lavela — launch and operations for the app you built. These Terms are provided for your reference and are not legal advice; have them reviewed by a qualified lawyer before relying on them.