NOTICE: FREQUENT UPDATES & ACTIVE DEVELOPMENT

Please Note: The Service is currently undergoing a period of rapid development and expansion (specifically late 2025 through end of 2026). Because we are frequently adding new features and improvements, these Terms of Service may also change frequently to keep pace.

By continuing to use the Service, you agree to be bound by the most recent published version of these Terms. We appreciate your flexibility and encourage you to review this document regularly during this active phase.

1. NATURE OF SERVICE AND "AS-IS" WARRANTY

The Service provides proprietary wrapper solutions—utilizing Flutter (webview_flutter or flutter_inappwebview) or Capacitor—to package JavaScript-based applications into native binaries for mobile platforms.

BETA / PREVIEW STATUS: The Service is currently in a "Beta" or "Public Preview" stage. It may contain bugs, errors, or incomplete features. We make no warranties that the Service will be stable or suitable for production use.

• "As-Is" Provision: The Service, including the proprietary bridges, custom Plugin APIs, and compilation environments, is provided on an "AS-IS" and "AS-AVAILABLE" basis. We do not warrant that the Service will be uninterrupted, timely, secure, or error-free. To the maximum extent permitted by law, we expressly disclaim all warranties, whether express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and non-infringement.
• Technical Limitations: We do not warrant that all web-standard features, CSS properties, or JavaScript APIs will function within the custom bridge environments (Flutter or Capacitor). Performance is strictly dependent on the User's code optimization; we disclaim all liability for latency or performance degradation resulting from the User's software.
• Solo Operation & Availability: User acknowledges that the Service is operated by a solo developer and relies on a mix of third-party cloud providers and self-hosted infrastructure. Consequently, the Service may experience extended periods of unavailability (potentially lasting days) if technical failures occur while the developer is unavailable (e.g., due to vacation, illness, or time zone differences). We do not guarantee 24/7 uptime, continuous monitoring, or immediate restoration of service.
• Best-Effort Support: Support requests are handled on a "best-effort" basis. We do not guarantee a response to every inquiry. We reserve the right not to reply depending on service demand and the communication channel used. Priority is given to official channels (e.g., GitHub Discussions); inquiries via unsupported platforms (e.g., Reddit, Discord) may be ignored.

2. TARGET AUDIENCE & INTENDED USE

This Service is designed and intended for use by individuals and small teams (defined as groups of 10 members or fewer). It is not designed or intended for use by large-scale enterprises or organizations requiring enterprise-level service agreements, custom security audits, dedicated support infrastructure, or guaranteed uptime SLAs.

This is a consumer-grade service. While larger organizations are not prohibited from using the Service, html2app.dev does not provide the warranties, indemnifications, uptime guarantees, or support commitments typically required by enterprise-scale businesses. Use of the Service by organizations exceeding the intended audience definition is permitted solely under the terms stated herein, with no additional obligations on the part of html2app.dev.

3. SUBSCRIPTION TERMS & ACCESS RIGHTS

Current Status: The Service is currently provided free of charge. We reserve the right to introduce paid subscription plans in the future.

• Free Access: During the current free period, the Service is provided "AS-IS" without warranty or support obligations. We reserve the right to limit features, usage quotas, or terminate free access at any time without notice.
• Future Paid Subscriptions: A "Subscription" refers to a paid plan that grants access to specific features, such as the compilation service. If paid plans are introduced:
  • Post-Termination Rights: Upon expiration or termination of a subscription, the User retains the right to use, distribute, and maintain applications already compiled and downloaded during the active subscription period.
  • Compilation Access: However, the User will lose access to the compilation service and cannot generate new binaries or updates until the subscription is renewed.
• Automatic Renewal: Paid subscriptions will automatically renew at the end of each billing period unless cancelled by the User.
  • Renewal Pricing: If you subscribed at an introductory or promotional rate (e.g., first-year discount), your renewal price may differ from your initial subscription price. Upon renewal, you will be charged the then-current standard price for your subscription tier, unless you have an active promotional code or extended discount agreement. We will notify you of any price change at least 30 days before your renewal date. Continued use of the Service after the renewal date constitutes acceptance of the new price.
  • Cancellation: You may cancel your subscription at any time through your account settings or by contacting support. Cancellation takes effect at the end of your current billing period; no refunds are issued for partial periods.
• Rate Limits (Build Quotas): User acknowledges that usage is subject to rate limits, including but not limited to: (1) a daily build limit, defined as the maximum number of builds (compilations) allowed per calendar day, resetting at 00:00 server time; and (2) a monthly build limit, defined as 10 times the applicable daily limit for free accounts, or 20 times the applicable daily limit for paid accounts (e.g., a paid tier with a daily limit of 5 builds is capped at 100 builds per calendar month), resetting on the 1st of each calendar month at 00:00 server time, each as specified on the Pricing Page. If any limit is reached, access to the affected functionality will be suspended until the respective limit resets. The Service reserves the right to modify these limits to ensure service stability for all users.
• Platform Restrictions: Access to specific build platforms (e.g., iOS) is restricted to specific subscription tiers. Users on lower tiers (e.g., Free or Starter) may be restricted to Android-only builds. We reserve the right to modify these platform restrictions at any time. For existing paid subscribers, we will provide at least 30 days' notice before restricting access to previously available platforms. If a platform is restricted, existing subscribers may request a pro-rata refund for the affected portion of their subscription.
• Support (Best-Effort / No SLA): Support is provided on a "best effort" basis. While we strive to resolve issues, a response or resolution time is not guaranteed. As a solo-operated project, support availability may vary. Priority is given to paid subscribers. We do not offer any service-level agreement (SLA), guaranteed response times, or guaranteed fix/update timelines, regardless of whether the service is free or paid.
• Regional Pricing & Eligibility: To make our services accessible globally, we may offer discounted pricing in specific regions (e.g., India) in the future. These discounts are only available to residents of the specified region. To qualify, you must provide a payment method (credit/debit card) issued by a financial institution within that region. We reserve the right to verify your location via IP address and payment metadata. If a mismatch is detected, html2app.dev reserves the right to charge the standard global rate or terminate the subscription. Attempting to bypass regional pricing via VPN or fraudulent billing addresses may result in account termination without a refund.
• Payment Terms & Merchant of Record:
  • Merchant of Record: Our order process is conducted by our online reseller Paddle.com. Paddle.com is the Merchant of Record for all our orders. Paddle provides all customer service inquiries and handles returns.
  • Taxes & Currency: As the Merchant of Record, Paddle is responsible for collecting and remitting applicable sales tax, VAT, or GST where required by law. The default currency is presented based on your IP address, but you may choose your preferred currency.
    • USD Pricing: Prices in USD are displayed exclusive of taxes. Applicable taxes will be added at checkout.
    • EUR Pricing: Prices in EUR are displayed inclusive of VAT (where applicable).
  • Price Changes: We reserve the right to change pricing. We will provide at least 30 days' notice for any price increase. No notice is required for price reductions. Continued use after the price change constitutes acceptance.
  • No Set-off: You must pay all fees in full without any set-off, counterclaim, deduction, or withholding.
  • Pricing Page: Current pricing, subscription tiers, and available features are listed on our home page, which is incorporated by reference into these Terms. In the event of a conflict between the pricing information and these Terms, these Terms shall prevail.

4. APP STORE ACCEPTANCE & DISCLAIMER

The Service currently supports one distribution channel: the Google Play Console (standard Android store distribution). Support for the Android Developer Console (ADC) (sideloading and non-Play distribution on certified Android devices) and the Apple App Store (iOS distribution) is planned but not yet integrated. User acknowledges that all three platforms maintain strict and evolving guidelines, and that support for each channel may vary in maturity.

• No Affiliation: html2app.dev is an independent service and is not affiliated with, endorsed by, or associated with Apple Inc., Google LLC, The Flutter Team, or the Capacitor Team. "Android", "Google Play", "iPhone", and "App Store" are trademarks of their respective owners.
• Rejection Risk: We do not guarantee that your application will be approved by Apple or Google. Rejection based on "Guideline 4.2" (Minimum Functionality) or similar policies is a known risk of wrapper solutions.
• Rejection Liability: We are not liable for any financial loss or damages resulting from the rejection of an application by third-party reviewers.
• Evolving Platform Policies: Google Play and the Apple App Store periodically introduce new requirements, including but not limited to changes to the Google Play Developer Console, new submission workflows, updated review policies, and new mandatory compliance declarations. We do not guarantee that the Service will be updated to reflect these changes before any enforcement deadline. User is solely responsible for monitoring platform policy announcements and ensuring their applications remain compliant.
• Phased & Regional Enforcement: Platform policy enforcement is sometimes rolled out gradually, with certain countries or developer accounts subject to enforcement earlier than others. We are not liable for a User's inability to publish, update, or distribute their application in any region due to enforcement timing mismatches between platform rollout schedules and our implementation timeline.

5. REFUND POLICY & WITHDRAWAL RIGHTS

Merchant of Record: Our order process is conducted by our online reseller Paddle.com. Paddle.com is the Merchant of Record for all our orders. All refund requests are handled by Paddle in accordance with their refund policy. To request a refund, please contact Paddle directly at paddle.net. For full details on refund handling, see Paddle's Consumer Terms.

Try Before You Subscribe: We encourage you to use our Free Tier to test the Service's functionality and compatibility with your project before subscribing. This allows you to evaluate the Service at no cost and ensure it meets your needs.

5.1. Right of Withdrawal (EU/UK/EEA Consumers)

If you are a consumer based in the EU, EEA, or UK, you have a statutory right to withdraw from a contract for digital services within 14 days. By subscribing to the Service, you acknowledge the following:

• Immediate Performance: By subscribing, you request that we begin providing the Service immediately. You acknowledge that once the digital service has begun (e.g., access to the compilation service is granted), your statutory right of withdrawal may be affected in accordance with applicable consumer protection laws.
• Pro-Rata Refund: If you are an EU, UK, or EEA consumer and wish to cancel your subscription within 14 days of your initial purchase, you may request a pro-rata refund for the unused portion of your subscription period by contacting Paddle at paddle.net. Refunds are processed by Paddle on a case-by-case basis.

5.2. Subscription Cancellation

You may cancel your subscription at any time. Upon cancellation, you will retain access to the Service until the end of your current billing period. Refund requests for subscription cancellations are handled by Paddle on a case-by-case basis in accordance with their policies.

5.3. Chargebacks & Disputes

If you have a concern about a charge, we encourage you to contact Paddle directly to resolve the issue. Initiating a chargeback or payment dispute without first attempting to resolve the matter with Paddle may result in suspension of your account and revocation of access to the Service.

6. AUTONOMOUS AGENTS & AI-ASSISTED PURCHASES

If you use any automated bot, artificial intelligence, browser extension, or autonomous software agent (collectively, "Autonomous Agents")—such as procurement tools, AI assistants, or similar automation software—to interact with the Service or execute financial transactions, the following terms apply:

• Mandatory Disclosure & Explicit Consent: For any purchase, subscription, or renewal initiated by an Autonomous Agent to be considered valid and authorized, the Agent must:
  • Explicitly present the total purchase price to the human account holder, including all applicable taxes, fees, currency conversions, and any other charges;
  • Obtain affirmative, explicit human consent (e.g., a manual click, verbal confirmation, or explicit "confirm" command) before finalizing the transaction; and
  • Provide a clear summary of what is being purchased and the subscription tier or service level being activated.
• User Responsibility for Bot Configuration: You are solely responsible for the configuration, behavior, and errors of any Autonomous Agent you deploy or authorize. This includes:
  • Ensuring the Agent is properly configured to request human approval before purchases;
  • Monitoring the Agent's activity and preventing unauthorized or unintended transactions;
  • Maintaining secure access credentials and preventing the Agent from accessing payment methods without proper safeguards.
  We are not liable for unintended purchases, duplicate charges, or financial losses caused by bot malfunctions, coding errors, misconfiguration, or AI "hallucinations."
• Irrevocability of Authorized Transactions: Any transaction completed where the Autonomous Agent has followed the disclosure and consent steps outlined above is deemed an authorized purchase by you. We will not honor refund requests, chargeback claims, or disputes based on "unauthorized use" or "I didn't authorize this" if the Agent successfully completed these verification steps. The burden of proof lies with you to demonstrate that the Agent did not obtain proper consent.
• Security & Technical Compliance: We reserve the right to:
  • Restrict, rate-limit, or block any Autonomous Agent that attempts to circumvent these transparency requirements;
  • Suspend or terminate accounts that engage in patterns suggesting bot-driven abuse, such as rapid successive purchases, purchases at unusual times, or purchases from multiple geographic locations;
  • Require additional verification (e.g., CAPTCHA, email confirmation, or manual approval) for transactions initiated by Autonomous Agents.
• No Liability for Bot Errors: We disclaim all liability for:
  • Duplicate charges resulting from bot retry logic or network errors;
  • Incorrect subscription tier selection due to bot misconfiguration;
  • Unintended renewals or upgrades triggered by the Agent;
  • Any financial loss or inconvenience resulting from the Agent's actions.

7. BRIDGE IMPLEMENTATION & NATIVE HARDWARE

All communication between the JavaScript layer and the Native layer is handled via a bridge. The Flutter implementation uses a proprietary bridge, while the Capacitor implementation uses the standard Capacitor bridge.

• Custom Plugin API: Liability for data loss, hardware malfunction, or incorrect sensor readings (GPS, Camera, Biometrics, etc.) resulting from the use of our custom Plugin API or Capacitor-integrated plugins is strictly excluded.
• Third-Party Dependencies: The Service may rely on third-party services and dependencies (including Apple/Google services, certificate authorities, hosting providers, and payment providers). We do not control these third parties and are not responsible for outages, policy changes, breaking changes, service degradation, or interruptions caused by them.
• Framework & OS Compatibility: We do not guarantee the continued compatibility of our bridges with future updates to Android (SDK), iOS (Swift/CocoaPods), or the underlying Capacitor/Flutter frameworks.

8. DEVICE FRAGMENTATION, COMPATIBILITY & FUTURE UPDATES

Due to the highly fragmented nature of the Android and iOS ecosystems, User acknowledges that:

• Hardware Variance: The application may behave differently across various OEMs, screen densities, and processor architectures.
• UI/UX Anomalies: We are not liable for "edge-case" bugs, including but not limited to: app icons failing to display, status bar overlapping, system gestures interfering with the WebView, or crashes occurring on specific hardware models.
• No Universal Guarantee: We do not guarantee that the compiled application will function correctly on every device manufacturer, model, or OS version.
• Breaking Changes: Mobile operating systems evolve rapidly. An application that functions correctly today may cease to function on future OS versions due to "breaking changes" introduced by Apple or Google. html2app.dev does not guarantee perpetual compatibility with future OS updates.
• SDK Target Version Mandates: Google and Apple periodically require developers to raise the minimum SDK target version of their applications (e.g., Android targetSdkVersion, iOS minimum deployment target). Updating the Service's build environment to comply with these mandates requires changes to the underlying frameworks (Flutter, Capacitor), toolchains, and third-party plugins. We do not guarantee that such updates will be completed before any platform-imposed deadline. During any update window, the Service may produce binaries that do not satisfy the latest platform requirements. User is solely responsible for monitoring these deadlines and planning their release schedule accordingly.
• Plugin & Dependency Lag: The Service relies on third-party plugins and packages (Flutter pub.dev packages, Capacitor community plugins, native SDKs, etc.). These dependencies are maintained by independent third parties and may not support new SDK versions or OS requirements immediately upon release. We are not liable for compilation failures, runtime errors, feature regressions, or store rejections caused by third-party plugin incompatibilities with new platform requirements, regardless of whether such incompatibilities are temporary or permanent.

9. PLATFORM POLICY COMPLIANCE & SDK MAINTENANCE

The Service currently integrates with the Google Play Console only. Support for the Android Developer Console (ADC) and the Apple App Store is planned for future releases. Each platform continuously evolves its technical requirements, developer console workflows, and compliance obligations. User acknowledges the following limitations of the Service in relation to these changes:

• Android Developer Console (ADC) — Early Development Status: The ADC is a new platform introduced by Google to govern sideloading and non-Play distribution on certified Android devices. Support for the ADC within the Service is currently under development and is not yet stable or feature-complete. The ADC's first enforcement deadline begins September 2026 in select countries (Brazil, Indonesia, Singapore, Thailand), with global rollout planned for 2027. We cannot guarantee that ADC support in the Service will be ready, stable, or fully compliant before these enforcement dates. User acknowledges this risk and is solely responsible for completing their own ADC registration (including identity verification, package name registration, and signing key submission) directly in their ADC account. The $25 Full Distribution account fee and any identity verification requirements are the User's sole responsibility. We are not liable for any inability to distribute apps via sideloading resulting from incomplete ADC support in the Service or from the User's failure to complete their own ADC registration before enforcement deadlines.
• No Compliance Guarantee: We do not guarantee that the Service, or applications built with the Service, will comply with current or future Google Play Console, ADC, or Apple App Store policies, technical requirements, or developer console mandates at any given point in time. Compliance is a shared responsibility between the User and the platform; html2app.dev is a technical tool, not a compliance advisor.
• Implementation Delays: As a solo-operated service, implementing support for new platform requirements (including new SDK targets, new console declarations, new permission models, or new binary format requirements) takes time. We do not commit to any specific implementation timeline. We are not liable for any loss, missed deadline, or inability to publish caused by a delay in our implementation of new platform requirements.
• Annual SDK Upgrade Cycle: Google mandates an annual increase to the required targetSdkVersion for new app submissions and updates. Apple similarly enforces minimum SDK and Xcode version requirements. Updating the Service to support each new annual requirement involves upgrading the Flutter or Capacitor framework, updating native dependencies, and validating the full build pipeline. This process may not be completed before the enforcement deadline. We are not liable for any consequences arising from this update window, including but not limited to: inability to submit new apps, inability to push updates to existing apps, or removal of apps from the store.
• Phased & Regional Enforcement: Platform policy enforcement is sometimes rolled out gradually, with certain regions, developer account types, or app categories subject to enforcement earlier than others. We are not liable for a User's inability to publish, update, or distribute their application in any specific region or account context due to a mismatch between the platform's enforcement schedule and our implementation timeline.
• New Console Requirements: Changes to the Google Play Developer Console or Apple App Store Connect (including new mandatory declarations, data safety forms, age rating requirements, or submission workflows) may require updates to the Service or to the User's own developer account configuration. We are not responsible for requirements that must be fulfilled directly by the User in their developer account, and we are not liable for rejections or enforcement actions resulting from incomplete or incorrect console configurations.
• User Monitoring Responsibility: User is solely responsible for monitoring official platform communications (Google Play Policy Center, Apple Developer News, etc.) and for understanding how upcoming changes affect their applications and release timelines. We recommend maintaining adequate lead time before any platform-imposed deadline when relying on the Service for production releases.
• No Liability for Store Actions: We are not liable for any app removal, suspension, demotion, or rejection by Google or Apple resulting from SDK non-compliance, policy violations, or failure to meet platform requirements — including ADC registration or verification failures — regardless of whether such non-compliance is attributable to a delay in our Service updates, third-party plugin lag, or platform enforcement timing.

10. ASSET ENCRYPTION AND SECURITY DISCLAIMER

The Service may offer an optional asset-encryption feature (for HTML, CSS, JS, and media). This feature is provided on an "as-available" basis and may be introduced, modified, or removed at our discretion.

• Default Plaintext Storage (Industry Standard): Unless the User subscribes to a specific tier that explicitly includes asset encryption, all application assets (HTML, CSS, JavaScript, images, etc.) are stored in the application binary in plaintext (unencrypted) format. User acknowledges that this is the standard behavior for WebView-based frameworks (e.g., Capacitor, Cordova) and is not a deficiency of the Service. While standard wrappers leave code exposed, html2app.dev distinguishes itself by offering proprietary asset encryption on supported tiers to mitigate this risk. Without this upgrade, assets can be extracted by anyone with access to the application binary (APK/IPA).
• Nature of Protection: While encryption adds a layer of protection against casual inspection, we do not guarantee that assets are "unhackable" or immune to reverse engineering. Security is provided on a best-effort basis, and we do not warrant absolute protection against determined third parties.
• Technical Implementation & Key Risk: To enable runtime decryption on the end-user's device, a decryption key must be embedded within the application binary. While this key is not stored in plain text (e.g., via obfuscation or similar methods), the User acknowledges that any key stored within a client-side binary can potentially be extracted by a sophisticated actor. Because the distributed binary must contain both the decryption routine and the key material to function, a determined attacker can use static reverse engineering, dynamic instrumentation (e.g., Frida), or memory inspection to recover the key. While techniques like obfuscation raise the cost of extraction, they cannot provide an absolute guarantee on devices we do not control. Consequently, client-side asset encryption is a deterrent, not an impenetrable barrier, and we cannot guarantee 100% protection against reverse engineering or data extraction.
• User Verification Responsibility: It is the User's sole responsibility to verify the integrity and encryption status of the final binary before submission to any app store. html2app.dev is not liable if the Service fails to encrypt assets during the build process, resulting in the publication of unencrypted files.
• Runtime Performance & Failure: We are not liable for application crashes, "white screens," or failure to boot caused by decryption errors on an end-user's device, whether due to hardware incompatibility, OS interference, memory constraints, or errors in the Service's proprietary logic.
• Export Control Compliance: User is solely responsible for ensuring their application complies with all applicable export control laws and regulations regarding the encryption in their territory of residence and operation.

11. CREDENTIAL STORAGE & KEY MANAGEMENT

The Service allows Users to store sensitive signing credentials (including but not limited to Android Keystores, iOS Distribution Certificates, and Provisioning Profiles) on our servers for the purpose of automated signing.

• Account Security: You are responsible for maintaining the confidentiality of your account login credentials and are fully responsible for all activities that occur under your account. You agree to immediately notify Us of any unauthorized use or suspected breach of security. We cannot and will not be liable for any loss or damage arising from your failure to comply with this requirement.
• Encrypted Storage: Credentials are stored in encrypted form within our Object Storage Service. Once uploaded, credentials are managed exclusively by the Service and cannot be retrieved by the User. The User may delete stored credentials at any time via the Service interface.
• Backup Responsibility: User is solely responsible for maintaining local backups of their keystores and certificates. Since the Service does not provide a way to retrieve uploaded credentials, the User must ensure their local copy is kept secure. We are not responsible for permanent data loss resulting from server failures or account termination.
• Storage Risk: User acknowledges that storing cryptographic keys on a remote server inherently carries risk. While we employ reasonable security measures, we do not guarantee the absolute security of stored credentials.
• Liability: Any liability arising from the loss, theft, leak, or compromise of User credentials is subject to the limitations set forth in Section 16.
• Data Retention & Deletion: We reserve the right to delete any stored credentials that have not been used for 12 months. Furthermore, we reserve the right to delete stored credentials periodically or at any time at our sole discretion (e.g., for security hygiene). The User acknowledges that they must maintain a local copy of their credentials at all times and keep it secure, as the Service does not provide a way to retrieve uploaded credentials.

12. INTELLECTUAL PROPERTY & CONFIDENTIALITY

• Split-IP Model: User retains full ownership of their web assets (HTML/JS/CSS). html2app.dev retains ownership of the server-side compilation scripts and infrastructure. For Flutter builds, html2app.dev additionally retains ownership of the proprietary native wrapper code and bridge implementation. For Capacitor builds, html2app.dev claims no ownership over the standard Capacitor runtime code.
• Confidentiality: html2app.dev agrees to treat all User-uploaded assets (including JavaScript logic, HTML, CSS, images, audio, and video) as confidential. We will not misappropriate, sell, or use User's proprietary assets for any purpose other than providing the compilation service.
• Limited License to Host: You hereby grant html2app.dev a worldwide, non-exclusive, royalty-free, limited license to host, copy, transmit, and display your User Content solely as necessary to provide the Service (e.g., to compile the application binary). This license terminates automatically when your content is deleted from our systems.
• Third-Party Licenses: The generated application may include third-party open-source components (e.g., Flutter or Capacitor plugins). The User is responsible for maintaining any required license notices (such as MIT, Apache 2.0, BSD-3-Clause, or others) within their distributed application.
• Feedback: If You provide Us with any feedback, suggestions, bug reports, or proposed modifications regarding the Service ("Feedback"), You hereby grant Us a perpetual, irrevocable, non-exclusive, royalty-free, worldwide license to use, modify, and incorporate such Feedback into the Service without any obligation to compensate or credit You.

13. COMPLIANCE WITH LAWS & ACCEPTABLE USE

• User Responsibility: User is solely responsible for ensuring their application complies with all applicable local and international laws, including but not limited to data privacy regulations (GDPR, CCPA), consumer protection laws, and intellectual property rights.
• Privacy Policy: Your use of the Service is also subject to our Privacy Policy, which describes how we collect, use, and share your personal data.
• Data Collection: User acknowledges that they are the "Data Controller" for any end-user data collected via the application, and html2app.dev acts solely as a technical service provider.
• Acceptable Use / Prohibited Content: User agrees not to use the Service to upload, compile, distribute, or facilitate (including through apps built with the Service) any content or activity that is unlawful, harmful, infringing, deceptive, or abusive. Prohibited use includes, but is not limited to:
  (a) malware, spyware, credential theft, phishing, or any malicious code;
  (b) infringing content (copyright/trademark) or unlawful use of third-party intellectual property;
  (c) content or functionality that violates applicable laws, regulations, or third-party platform policies;
  (d) attempts to conceal malicious functionality or bypass platform/security restrictions.
• Sanctions & Export Compliance: You represent and warrant that you are not located in, under the control of, or a national or resident of any country subject to a U.S. Government or Swiss embargo, or designated on any U.S. Government or Swiss list of prohibited or restricted parties. You agree not to use the Service to export or re-export any software or technical data in violation of applicable export control laws.

14. TERMINATION & SUSPENSION

We reserve the right to suspend or permanently terminate a User's account and access to the Service. Termination may occur without prior notice or refund for severe violations (including but not limited to prohibited activities). For non-material breaches, we may, at our sole discretion, provide an opportunity to cure the breach, though we are under no obligation to do so.

• Security Violations & Abuse: Such activities include, but are not limited to:
  (a) Attempting to hack, penetrate, scan, or compromise the security of the Service or its infrastructure;
  (b) Bypassing or attempting to bypass payment mechanisms, usage quotas, or access controls;
  (c) Reverse engineering, decompiling, or disassembling any proprietary components (bridges, plugins, wrappers);
  (d) Uploading malicious code, malware, or content that violates applicable laws;
  (e) Initiating fraudulent chargebacks or payment disputes.
• Consequences: In such events, all rights granted to the User herein shall immediately cease, and we reserve the right to pursue appropriate legal action.
• At-Will Termination: We reserve the right to terminate any User account or the Service as a whole at any time, for any reason or no reason ("At-Will"), provided that such termination does not violate the terms of any active paid subscription contract. If we terminate a paid account without cause, we will refund the pro-rated portion of any prepaid fees for the remainder of the subscription term.

15. MODIFICATIONS TO TERMS AND SERVICE

• Right to Modify Terms: We reserve the right to modify these Terms of Service at any time.
• Right to Modify Service: We reserve the right to modify, suspend, or discontinue any aspect of the Service, including features, functionality, supported platforms, or technical specifications, at any time without prior notice.
• Acceptance: Continued use of the Service after any such changes (to the Terms or the Service) constitutes your acceptance of the modified Terms and the most recent version of the Service. It is the User's responsibility to review these Terms periodically.
• User Responsibility: Users are responsible for evaluating changes before relying on features in production builds.

16. LIMITATION OF LIABILITY

To the maximum extent permitted by applicable law, in no event shall html2app.dev, its directors, or employees be liable for any indirect, incidental, special, or consequential damages, including loss of profits, data, or use.

• Liability Cap: In no event shall our total liability to you for all damages exceed the greater of: (a) the amount of fees paid by you to the Service during the 12-month period immediately preceding the event giving rise to the claim, or (b) $100 USD. For users of the free tier, liability is capped at $100 USD. This liability cap applies to all claims in aggregate, to the maximum extent permitted by law.
• Force Majeure: We shall not be liable for any failure to perform our obligations where such failure results from any cause beyond our reasonable control, including, without limitation, mechanical, electronic, or communications failure or degradation (including "line-noise" interference), natural disasters, pandemics, government actions, war, terrorism, or acts of God. In the event of a force majeure event, we will notify users of the suspension of service and provide updates on restoration efforts to the extent reasonably practicable.
• No High-Risk Use: The Service is not designed or intended for use in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, life support machines, or weapons systems, in which the failure of the Service could lead directly to death, personal injury, or severe physical or environmental damage.
• Unforeseen Risks: All other risks, including those not explicitly mentioned in this section, fall under the disclaimers and limitations described in Section 19, and are subject to the same liability cap and exclusions.

17. INDEMNIFICATION

User agrees to defend, indemnify, and hold harmless html2app.dev from and against any claims, damages, or expenses (including reasonable legal fees and attorney costs) arising from:

• The content of the User's application.
• Any violation of third-party intellectual property by the User.
• End-user claims regarding the functionality of the User's published application.
• Any violation of these Terms or applicable laws by the User.

18. MISCELLANEOUS

• Severability: If any provision of these Terms is held to be invalid, illegal, or unenforceable, the remaining provisions shall remain in full force and effect.
• Entire Agreement: These Terms constitute the entire agreement between the User and html2app.dev regarding the Service and supersede any prior or contemporaneous communications or agreements.
• Assignment: User may not assign or transfer these Terms without our prior written consent. We may assign these Terms in connection with a merger, acquisition, reorganization, or sale of assets, or by operation of law.
• No Waiver: The failure of html2app.dev to enforce any right or provision of these Terms will not be considered a waiver of those rights.
• Survival: All provisions of these Terms which by their nature should survive termination shall survive termination, including, without limitation, ownership provisions, warranty disclaimers, indemnity, and limitations of liability.

19. UNFORESEEN RISKS & CATCH-ALL DISCLAIMER

The technology landscape evolves rapidly, and we cannot foresee every technical issue, platform policy change, or usage scenario.

• Comprehensive Coverage: All risks, damages, or losses not explicitly mentioned in these Terms—including those arising from third-party dependencies, platform updates, or novel technologies—are subject to the same liability caps, disclaimers, and limitations described herein.
• Broad Interpretation: These Terms shall be interpreted broadly to protect the Service provider against liability for such unanticipated events to the maximum extent permitted by law. The absence of a specific reference to a particular scenario does not imply assumed liability.

20. GOVERNING LAW & DISPUTE RESOLUTION

• Governing Law: This Agreement shall be governed by and construed in accordance with the substantive laws of Switzerland.
• Informal Resolution: Before initiating litigation, the parties agree to attempt to resolve any dispute informally and in good faith.
• Class Action Waiver & Individual Capacity: To the fullest extent permitted by applicable law, You agree that any dispute arising out of or related to these Terms or the Service will be resolved solely on an individual basis. You explicitly waive any right to participate in a class action lawsuit, class-wide arbitration, private attorney general action, or any other representative proceeding.
• Jurisdiction: Any disputes arising out of or related to this Agreement that cannot be resolved informally shall be subject to the exclusive jurisdiction of the competent courts of Bern, Switzerland.

21. CONTACT INFORMATION

For any questions regarding these Terms of Service, please contact us via:

• Public Discussions: GitHub Discussions
• Email: You can find the contact email on the developer's profile page: https://yandeu.github.io/