1. Acceptance and Applicable Parties
By visiting the LemonVM website, creating an account, using the console, or ordering Cloud Mac services, you confirm that you have read, understood, and agreed to be bound by these Terms. If you do not agree with any part of them, do not create an account, place an order, or continue using the services.
Individual users must have the legal capacity required to enter into a contract. Anyone acting for a company, team, or other organization confirms that they have the necessary authorization; the organization and all members who use the services must comply with these Terms.
These Terms, together with the model, node, rental period, add-ons, and amount shown in the order, form the service agreement. If the specific order configuration differs from a general description, the order details confirmed before submission and the console record prevail.
2. Service Definition
LemonVM provides Cloud Mac services rented by the day, week, month, or quarter. Resources are delivered on physical Mac mini nodes. During the active service period, users receive exclusive use of the physical machine they ordered; it is not shared with other tenants and is not a virtual machine instance.
The actual delivery scope is defined by the order and includes the selected model, chip, memory, base storage, node, rental period, and any confirmed SSD expansion or Thunderbolt 5 parallel-connection add-ons. Connection details, ports, account information, and essential security notices are provided through controlled channels after order processing.
The node catalog includes Singapore, Tokyo, Seoul, Hong Kong, and the western United States. Real-time availability for each model-and-node combination is returned by the console. Website service descriptions help with selection and do not replace the final confirmation shown when an order is submitted.
The service allows users to use the macOS graphical interface, command line, Xcode, automated build tools, and legally installed software. Users are responsible for confirming before ordering that software licenses, project dependencies, signing materials, and workloads suit the selected configuration.
3. Account and Credential Responsibilities
Users must provide accurate, complete, and reachable account information and update it promptly when it changes. Do not impersonate another person or organization, use their name or contact details, or evade normal account-management rules through bulk registration or automated abuse.
Users must protect login credentials, connection keys, one-time codes, host addresses, and access ports. Do not disclose them in public repositories, groups, ticket screenshots, or other channels without access controls. For team use, assign access by role and revoke it promptly when a member leaves the project.
Orders, configuration changes, tickets, and node operations initiated through a user account or valid credentials are generally treated as actions of that account. If you discover unusual sign-ins, exposed credentials, or unauthorized activity, immediately replace the affected credentials and contact support through a console ticket or support@lemonvm.com.
4. Orders and Configuration
Before submitting an order, verify the model, chip, memory, storage, node, rental period, add-ons, and total USD amount. The standard Lemon M4 configuration is M4, 16GB memory, and a 256GB SSD; the standard Lemon M4 Pro configuration is M4 Pro, 64GB memory, and a 2TB SSD.
Choose the node and rental period based on your access location, task duration, interaction method, and data volume. SSH builds, VNC graphical work, continuous integration, experiments, and audio/video workflows have different network, memory, and storage requirements, so base your choice on the actual workload.
After submission, the order ID, model, node, period, add-ons, amount due, and service status shown in the console are the basis for verification. If the page does not match your expectations, stop before payment or further action and contact support; do not rely on verbal promises or information outside the page.
Real-time availability for a specific node is returned by the console. For confirmed orders, whether a configuration change can be made and what fees it may incur are determined by the available console actions and the solution confirmed by the support team.
5. Billing and Payment
All orders are priced and settled in US dollars (USD). The amounts for the base model, rental period, and add-ons are listed separately before submission. Review the details, quantities, and final total before paying.
The only supported payment methods are USDT-TRC20 and Visa, Mastercard, and Amex processed by Stripe. Actual gateway availability is returned by the console in real time. Complete payment using the amount, network, and recipient information shown at checkout.
When choosing USDT-TRC20, confirm that the asset type, transfer network, address, and amount match exactly. You are responsible for losses caused by selecting the wrong network, address, or asset. Card payments may require necessary identity or risk verification.
Billing questions must include the order ID, payment method, payment time, and a redacted transaction receipt, submitted through a console ticket. Do not send full card details, private keys, recovery phrases, or complete access tokens in tickets or email.
6. Acceptable Use
Users must not use the service for activities that violate applicable laws, administrative requirements, or binding rules, or engage in fraud, infringement, harassment, bypassing security controls, or other conduct that harms the lawful rights of third parties.
Do not scan, probe, access, or control third-party systems without authorization. Do not distribute malware, steal credentials, launch denial-of-service attacks, disrupt network operations, or use a node as infrastructure for attacks, relaying, or concealing the source of activity.
Users must not affect the service platform, other nodes, or upstream networks through sustained abnormal use of network, storage, or computing resources. Do not bypass technical limits, create accounts in bulk, resell unauthorized access, or conceal the actual service user.
Users must ensure that uploaded code, materials, data, software, and build tasks have lawful sources and the required permissions. After receiving a credible infringement, security, or compliance report, the platform may request an explanation, require the related task to stop, or remove problematic content.
7. Data and Backup Responsibilities
Users are responsible for managing code, materials, configurations, keys, caches, and build artifacts uploaded to a physical node and should maintain independent backups based on project importance. A working copy on the node must not be treated as the only copy; critical repositories, certificate copies, and final artifacts should be stored securely under the user's control.
Users should follow the principle of minimization and upload only the data required to complete the task. Do not submit personal sensitive information, production secrets, complete access tokens, private keys, recovery phrases, or unredacted signing materials unless necessary.
For collaborative work, users should establish clear processes for account roles, key rotation, log retention, and handoffs. When a task is complete, a member changes, or the service ends, promptly revoke access that is no longer needed and confirm that required artifacts have been exported.
If support assistance is needed, provide reproducible steps, the error time, node, tool versions, and redacted logs whenever possible. The support process does not require users to send long-lived credentials that could directly log in to a node or access a third-party system.
8. Suspension and Termination
If the system detects a clear security risk, unauthorized access, malware distribution, resource abuse, unlawful activity, infringement of third-party rights, or another violation of these Terms, the platform may, depending on the risk, restrict connections, suspend the related service, or terminate the account and order.
An order may not proceed if payment fails, payment details cannot be verified, a transaction appears materially abnormal, or the user has not completed required payment confirmation. The specific status and next steps are determined by the console and information provided by the support team.
To fulfill applicable legal obligations, comply with a valid request from an authorized authority, or contain an urgent security incident, the platform may take necessary access restrictions or data-protection measures. Where conditions permit and doing so will not increase risk, the platform will explain the required action to affected users.
Suspension or termination does not affect payment obligations already incurred, account-security responsibilities, acceptable-use responsibilities, or provisions that must remain effective by law. Before the service ends, users must export necessary data and build artifacts and revoke associated credentials.
9. Service Changes and Liability
The platform may adjust service features, ordering processes, and available configurations due to security response, hardware supply, software compatibility, node resources, or legal requirements. Important changes affecting existing orders will be explained through the console, account contact details, or another reasonable channel.
All nodes operate normally 365 days a year with no scheduled downtime. Unexpected hardware failures, urgent security incidents, force majeure events, third-party network issues, or user actions may still affect connectivity, task execution, or data transfer. Users should keep recoverable task states and independent backups for critical work.
Cross-region access quality is affected by the user's local network, carrier routing, link congestion, selected node, VNC image quality, and background transfer tasks. The platform will help locate service-side issues within reason but cannot control the real-time state of user or third-party networks.
To the extent permitted by applicable law, liability will be determined in light of the actual loss, cause of the incident, each party's ability to control it, whether the user took reasonable steps to mitigate the loss, and the relevant order. These Terms do not exclude or limit liability that the law expressly prohibits excluding or limiting.
10. Updates and Contact
The platform may update these Terms as service capabilities, business processes, security requirements, or legal obligations change. New versions will state the version and effective date. Changes that materially affect user rights or obligations will be communicated through reasonable means.
Continuing to access the website, use the console, or use the services after an update takes effect means that the user accepts the updated Terms. If you do not agree, stop placing new orders before the new version takes effect and handle existing services and necessary data exports through the available process.
These Terms are governed by the laws of the jurisdiction where the platform operator is based. For disputes arising from these Terms or the services, the parties should first seek a resolution through good-faith communication. If negotiation fails, the dispute may be submitted to a court with jurisdiction in that jurisdiction.
For questions about the Terms, orders, or service use, sign in to the console to submit a ticket or email support@lemonvm.com. Include the order ID, issue type, and necessary redacted information. Do not send private keys, recovery phrases, or complete access tokens.