lavela — Terms of Service

Last updated: June 21, 2026 Version: 2026-06-2

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 we charge you (Section 6), what happens if you don't pay (Section 7), limits on our liability (Section 11), and — in some places — how disputes are resolved (Section 15). 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 date and time, and your IP address 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 takes further delegated action for you (see Section 14).

1.3 Eligibility. You must be at least 18 years old (or the age of legal majority in your jurisdiction) and able to form a binding contract. 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 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.

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, security scans, compliance document generation, automated recovery, and daily AI summaries.

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. Each delegated action is recorded in an audit log that you can review. Some action types may run automatically (auto-mode) and others may ask for your confirmation first, according to the settings and consents in effect for your account.

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, and 11).

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 Sections 6 and 7). 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 13).

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.3 Why some limits exist. Because lavela runs your compute inside pooled, shared provider accounts, abuse by one customer can harm everyone. We therefore enforce safety guardrails (limits on how large a resource a newer/less-verified account can spin up, abuse detection, and rate limits). These are safety controls, not spending caps — your spending is governed by the fees in Section 6.

4.4 Identity and anti-fraud. To run meaningful compute, advertising, or payments, you may be required to add a payment card (with a small verification hold) and to complete identity verification (such as Stripe KYC). The threshold at which identity verification becomes mandatory (for example a level of monthly compute or a number of machines) is shown in the console at the point it applies; below that threshold a card-only account may run smaller workloads. We may decline, limit, suspend, or unwind any action 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.

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 and lavela own 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

This Section states exactly how lavela makes money from you. We aim to be precise.

6.1 Monthly compute service charge (billed in advance, with a non-refundable floor + overage-only true-up). For the pooled compute and container infrastructure lavela runs for you, you pay a monthly service charge. This charge is priced at lavela's cost plus a margin and is presented as a single monthly figure (we do not separately itemize the margin, and we do not claim this charge is "at cost"). It works like this:

• Billed in advance. At the start of each monthly cycle (calendar-month cycles), lavela charges a monthly amount based on the machine specification you have provisioned. When you first provision partway through a month, the first charge is prorated for the remainder of that month.
• This advance amount is a non-refundable monthly floor. It is your minimum commitment for that cycle for the compute you provisioned. If your actual usage for the cycle turns out to be less than the floor, the difference is not refunded and never produces a negative invoice (the floor is the commitment). The one exception is cancellation, which is covered in Section 6.7.
• Overage-only true-up. If your actual metered usage (for example runtime above the estimate, or bandwidth/egress) exceeds the floor for a cycle, the excess only is billed in arrears on the next cycle's invoice. A single invoice therefore carries next month's floor (in advance) plus last month's overage, if any (in arrears). The true-up never runs in your favor below the floor.
• Mid-cycle changes. If you scale up mid-cycle, the larger specification is charged for the new exposure. If you scale down mid-cycle, the change is reflected as a credit toward your next invoice rather than an immediate refund.

6.2 Advertising commission (~10%). If you run advertising through lavela, lavela charges a commission of approximately 10% on the advertising spend you run through the Service, subject to any spend limits you set. The current commission rate is shown in the console before you launch a campaign.

6.3 What's inside the compute charge vs. passed through at cost.

• Inside the monthly compute service charge (Section 6.1): the pooled infrastructure lavela operates to run your app — compute and containers, plus the caching, object storage, and logging/error-monitoring resources lavela provisions to support that compute. These are bundled into the single monthly figure, not billed separately.
• Passed through at provider cost (no lavela markup): transactional email and domains. Domains are connect-only where applicable (you own the domain).
• Web analytics (visitor/pageview counts for your app) is provided as part of the operations layer at no separate charge unless the console states otherwise.

6.4 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 Sections 6.1–6.3 — for the infrastructure and services lavela itself runs for you. (Separately, lavela is the merchant of record for its own charges to you under this Section 6; that does not make lavela a party to your sales to your customers.)

6.5 Taxes. Fees are exclusive of taxes. You are responsible for any taxes on your purchases from lavela (other than taxes on lavela's net income). You are solely responsible for the taxes arising from your business and your sales to your customers.

6.6 Payment method and authorization. You authorize lavela (and its payment processor) to charge your payment method on file for all fees as they come due, including the monthly advance charge, overage true-ups, and ad commissions. If you do not have a valid payment method on file, lavela cannot run compute for you.

6.7 Cancellation and prorated refund. You may cancel a paid resource or your account at any time. If you cancel partway through a billing cycle, lavela will issue a prorated refund of the unused remainder of the prepaid monthly floor for that cycle, calculated from the effective date of cancellation and net of usage already incurred (including any metered overage). This prorated refund applies only to cancellation — it does not apply to ordinary under-use within a cycle, which is governed by the non-refundable floor in Section 6.1. Ad commissions and pass-through infrastructure costs already incurred are non-refundable.

6.8 Changes to fees. We may change fees or the commission rate prospectively. We will give you reasonable advance notice through the console or by email, and changes take effect at your next billing cycle. Continuing to use a paid resource after the change takes effect means you accept the new fee.

7. Non-Payment: Suspension and Teardown Ladder

If a payment fails, lavela does not kill your services immediately — because your app going down means your customers see downtime. Instead we follow a graceful, staged ladder. Within this ladder, your data is preserved until the final step, and your app is brought back up as soon as payment succeeds.

7.1 The ladder.

1. Warn + retry. When a charge fails, we notify you and begin automatic retries. Your app keeps running. Most issues resolve here.
2. Stop (data preserved). If the failure isn't resolved within the grace window, lavela stops your compute — the machines power off (compute billing goes to zero), but your data, volumes, and databases are kept. Pay during this period and your app comes right back up (typically within about a minute, on the same volumes/databases).
3. Teardown (deletion). If payment is still not made after a further destroy-grace window, lavela permanently tears down the provisioned resources, including the preserved data. After this step the data is not recoverable.

7.2 Grace windows depend on your trust level. How long you have at each step depends on your account's standing, because during a grace period lavela is fronting real provider costs it has not yet collected:

• Newer / card-only accounts (Tier A): stop around day 5 after the failed charge; teardown around day 12.
• Verified / established accounts (Tier B) — identity-verified (e.g. Stripe KYC) or a seasoned, paying account: stop around day 14; teardown around day 28.

These windows are defaults and may be tuned over time; the current windows are reflected in the console and in our notifications.

7.3 We will warn you before each step, including the irreversible one. lavela commits to sending you notice (by email and/or in the console) before moving to the stop step and again before the irreversible teardown step, so you have a real opportunity to resolve the payment or export your data before deletion. These warnings track the grace windows in Section 7.2.

7.4 Disputes / chargebacks. If a charge is disputed or flagged as fraudulent (for example a chargeback or a fraud flag), lavela may stop your compute immediately, skipping retries, because a dispute on a running server means lavela bears both the cost and the reversed payment. Data is preserved at the stop step as in 7.1(2).

7.5 Export before teardown. Your data is exportable throughout (Section 13.5). We encourage you to export promptly if you do not intend to resolve a payment failure.

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:

• Vercel — web hosting and CDN
• Fly.io — compute and containers
• Neon — Postgres databases
• Supabase — your app's authentication and lavela's application database
• Resend — transactional email
• Stripe / Stripe Connect — payments, your connected accounts, and lavela's own billing
• Upstash — Redis cache and rate limiting
• Inngest — workflow orchestration
• Axiom and Sentry — logging and error monitoring
• Cloudflare R2 — object storage
• Plausible — privacy-friendly web analytics for your app (visitor and pageview counts)
• DeepSeek — server-side background AI for summaries and suggestions

This list is the authoritative subprocessor list and is kept identical to the list in the Privacy Policy and the Data Processing Agreement (Section 9). (Founder: re-audit the codebase for any live data-touching provider before launch and keep all three lists exactly in sync.)

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. Where you are an EU/UK controller of personal data, the advance-notice and objection rights in the Data Processing Agreement (Section 9.5) apply to new subprocessors — additions of subprocessors are not treated as silent changes for you. 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.

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), the Data Processing Agreement (available on request — contact legal@lavela.dev) is incorporated into these Terms and applies automatically to that processing. The DPA contains the terms required by GDPR Article 28, including: the subject matter, duration, nature, and purpose of processing; processing only on your documented instructions; confidentiality obligations on personnel; technical and organizational security measures; the use of and flow-down to subprocessors; assistance with data-subject requests and with your security, breach, and impact-assessment obligations; deletion or return of personal data on termination; and audit/information rights. For transfers of personal data out of the EU/UK, the DPA incorporates the applicable transfer mechanism (EU Standard Contractual Clauses and the UK International Data Transfer Addendum). If there is any conflict between the DPA and these Terms with respect to processing of personal data on your behalf, the DPA 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 any intended addition or replacement of a subprocessor (by updating the list and notifying you via the console and/or email), and you may object on reasonable data-protection grounds within the window stated in the DPA; the DPA 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 the DPA, so that you can meet your own notification obligations.

9.7 Audit log. Every delegated action lavela takes for you is recorded in an audit log available to you, for transparency and your records.

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 non-payment ladder (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 credits or refunds, except as expressly stated in Section 6.7. 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. (Founder: confirm with counsel that this cap is enforceable against consumers in your chosen jurisdiction; consider a modestly higher floor or a carve-out for security-incident liability.)

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 lavela's compute service charge and ad commission — it does not include 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 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, 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). (Founder: confirm scope of this lavela-side IP indemnity with counsel before launch.)

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 materially, we will ask you to re-accept the new version before lavela takes further delegated action for you, and we record that acceptance (version, time, IP) as described in Section 1.2. Non-material changes (such as clarifications) take effect on posting. Subprocessor additions are not silent for EU/UK controllers — they 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; we will not continue taking delegated actions for you under the old version once a new acceptance is required.

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. Outstanding fees through the effective date of cancellation remain due; prorated refunds apply as described in Section 6.7.

15.3 Termination or suspension by lavela. We may suspend or terminate your access (a) for non-payment, following the ladder in 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 non-payment teardown (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, 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 export your data yourself, on a self-serve basis, through the console or the MCP server, at any reasonable time before and during the teardown grace windows. On account closure (or before the irreversible teardown step), lavela will keep your exportable data available for at least 30 days days before deletion, except where we must delete or retain it to comply with law. We will give you the notice described in Section 7.3 before any irreversible deletion.

16. General

16.1 Governing law and disputes. These Terms are governed by the laws of Canada, without regard to its conflict-of-laws rules. The parties submit to the courts of 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.

[FOUNDER DECISION REQUIRED BEFORE LAUNCH — arbitration vs. courts.] Decide whether disputes go to the courts named above or to binding individual arbitration with a class-action waiver. This is a material, must-decide item for a US-facing platform, and consumer-protection law (including CCPA contexts) affects how venue, jurisdiction, arbitration, and class-waiver clauses are enforced against consumers.

• If you choose courts, delete this note and keep the clause above.
• If you choose arbitration + class waiver, insert the arbitration clause here (selected administrator/rules, seat, individual-basis-only, and a 30-day opt-out window per US enforceability norms), after legal review.

16.2 Entire agreement. These Terms, together with the Privacy Policy, the DPA (where it applies), 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.

17. Contact

Questions about these Terms? Contact lavela at legal@lavela.dev (e.g. legal@lavela.dev), Canada (mailing address available on request at legal@lavela.dev).

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.

Questions? Contact us at the email in this document. · Terms · Privacy