Acceptance of terms and service provider
By accessing this website, placing an order in the console, completing payment, connecting to a delivered device, or continuing to use the service, you confirm that you have read and agree to be bound by these terms. If you act for a company, team, or other organization, you confirm that you are authorized to accept these terms on its behalf and are responsible for ensuring that approved device users understand the applicable requirements.
VMOwn provides Apple Silicon cloud Mac rentals, remote access delivery, order management, and related technical support. Product descriptions on the website are intended to help you choose a configuration. The final order is determined by the model, region, rental period, add-ons, payment record, and service status confirmed in the console.
If you do not agree to these terms, stop creating orders or using the service. If you have questions about a rule, contact us before payment at support@vmown.com ; for existing order issues, submit a console support ticket first so we can associate the request with the order record and track its progress.
Service description
A “cloud Mac” is an Apple Silicon device deployed in a data center and accessed remotely over a network. A “physical node” is the actual device hosting an order’s workloads. A “dedicated physical machine” means that the computing, memory, and local storage resources assigned to your order are not shared with other customers’ runtime environments; this service is not a virtual machine.
The catalog includes three tiers: VMOwn M4 Core, VMOwn M4 Plus, and VMOwn M4 Pro Max. Each tier has its own chip, unified memory, and local storage configuration. Available regions are Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US West. The specific combinations and live availability are determined by the results returned in real time when you create an order in the console.
Services are delivered through a graphical remote desktop and, where applicable, command-line connection methods. The remote experience depends on your local network, cross-region routing, client settings, display resolution, and workload. When choosing a region, consider the developer’s location, code repository location, target test markets, and the primary destinations of continuous integration traffic.
Device delivery does not include software licenses purchased independently by the customer, third-party subscriptions, project code, certificates, provisioning profiles, or business data. You are responsible for confirming that your intended software complies with its license terms and for managing project dependencies and team access.
Orders, configurations, and delivery records
When creating an order, you must select the model, region, rental period, and applicable add-ons. Available add-ons include extra SSD capacity and Thunderbolt 5 multi-device configurations. Before submitting, verify the unified memory, storage, network location, and runtime period required by your workload. After an order is confirmed, changing the region or hardware tier will generally require a new order and a data migration plan.
The order number, configuration details, payment status, delivery stage, device identifier, rental start and end times, and renewal records in the console together form the service record. Check this information promptly. If the configuration differs from the confirmed order, submit a support ticket before deploying production workloads, including the order identifier and a verifiable description of the discrepancy.
Delivery may include order confirmation, payment verification, device configuration, and generation of access credentials. The actual time required depends on the live availability status and order verification results returned by the console. The console record, not a static status shown on the website, governs delivery status.
Access credentials may be used only by authorized personnel to connect to the corresponding device. After the first connection, complete the necessary security settings and ensure that team members receive connection information through controlled channels. Do not publicly share complete passwords, private keys, or other information that could directly provide control of the device.
Pricing, payments, and settlement
All orders are priced and settled in US dollars (USD). The only supported payment methods are USDT-TRC20 and Visa, Mastercard, and Amex processed by Stripe. The available payment gateways are determined by the options returned in the console at checkout.
The order price consists of the selected model, rental period, region, and add-ons. The order details shown before payment are the basis for confirming the transaction. Check the payment amount, blockchain network, recipient details, and card payment page carefully to avoid using an incompatible network or paying a destination other than the one shown for the order.
When using USDT-TRC20, complete the transfer for the amount and valid details shown in the order, and retain verifiable transaction records. VMOwn does not control blockchain confirmation times or network processing speeds. Card payments are processed by Stripe; VMOwn does not store complete card details.
Keep payment proof, the order identifier, and transaction records associated with the corresponding order. Do not assume that an order is active based only on a local screenshot while payment status remains unconfirmed. If the status has not updated for an extended period, submit the order identifier and necessary transaction details through a console support ticket. Do not send complete card details, passwords, or private keys.
Rental periods, renewals, and expiration handling
Services are available for daily, weekly, monthly, or quarterly rental periods. The actual start and end times, renewal status, and current cycle for each order are determined by the console record. Choose a rental period based on your build tasks, project timeline, and data migration needs; do not assume that the device will automatically continue after the current order expires.
If you need to continue using the device, complete the renewal before the order expires and confirm the status in the console. Cycle changes, add-on adjustments, and changes to order information are governed by the options available for submission in the console and the final confirmation. An action that has not been confirmed does not constitute a valid renewal.
Before the rental period ends, you are responsible for exporting source code, build artifacts, caches, logs, certificates, provisioning profiles, and other required data, and for verifying that backups can be restored. After expiration, do not rely on the device as your sole copy of any data. If a team handoff is required, arrange access revocation, data export, and workspace cleanup in advance.
Changing the region or hardware tier generally involves a new order and data migration. First confirm that the new device can be accessed, the toolchain runs correctly, and all project dependencies are available. Only then stop using the original order to avoid interrupting builds through an incorrect migration sequence.
Acceptable use
You may use a cloud Mac for lawful software development, testing, automated builds, continuous integration, model inference, audio and video production, and other tasks compatible with the device’s capabilities and software licenses. When using the service, you must comply with these terms, the laws of the jurisdiction where the platform operator is established, and lawful requirements applicable to your activities.
You must not use or assist others in using the service for illegal activity, unauthorized access, credential theft, malware distribution, cyberattacks, fraud, resource abuse, bypassing security controls, privacy violations, or infringement of third-party intellectual property. Do not intentionally interfere with data center networks, other customers’ services, or VMOwn order and support systems.
Configure reasonable concurrency, retry, caching, and logging policies for automated tasks. Do not intentionally damage devices, networks, or storage media through abnormal traffic, runaway processes, or sustained high-intensity writes. If a script behaves unexpectedly, stop the relevant task immediately and review the access credentials and execution records.
VMOwn may take necessary measures, including restricting access, suspending processing, or terminating service, in response to activity that clearly violates these terms, affects service security, or presents an urgent risk. Verification may rely on order records, system events, and information submitted by the customer. Where appropriate, VMOwn may ask you to explain the intended use or complete remediation.
User data and account security
You own or lawfully control the project data you upload, create, and process, and are responsible for its content, software licenses, and processing purposes. VMOwn does not replace your version control, artifact repository, or long-term backup strategy. Keep independent copies of important code, configurations, certificates, and build artifacts.
You are responsible for securely protecting console login details, device access credentials, SSH keys, signing materials, and team member permissions. Follow the principle of least privilege, grant access only to members who need it, and promptly revoke access and rotate credentials when a member leaves the project, the device’s purpose changes, or credentials may have been exposed.
Do not submit complete passwords, private keys, or remote-control verification codes in tickets, email, screenshots, or logs. Before submitting diagnostic material, remove access tokens, keys, personal information, and unrelated business data. The support team may request an order identifier, system version, time of occurrence, an excerpt of the error, and reproduction steps, but will never ask you to send a complete password or private key.
Recovery work resulting from unbacked-up data, accidental file deletion, incorrectly configured permissions, shared credentials, or uncontrolled scripts may be limited by the device’s current state and available records. Create a verifiable backup before performing system upgrades, disk cleanup, large-scale dependency changes, or migration operations.
Availability, emergency response, and support
Under normal service conditions, nodes operate 365 days a year with continuous availability. Uptime, delivery progress, and device status shown on the status page or in the console are dynamic information and should be assessed against monitoring results at the relevant time; historical data should not be understood as an absolute guarantee for every future moment.
In the event of a hardware failure, security risk, network anomaly, or other incident requiring immediate attention, VMOwn may take necessary emergency measures, including isolating abnormal connections, checking device status, adjusting access methods, or coordinating recovery. Priority is determined by the scope of impact, reproducibility, order status, and security risk.
For connection issues, first check your local network, client version, target region, credential validity, and firewall settings. For build issues, provide the system version, Xcode version, command, error excerpt, and reproduction steps. Submit order, renewal, and device-status issues through a console support ticket so support staff can associate them with the service record.
Availability assessments exclude outages in the customer’s own network, incorrect configurations, invalid credentials, operations beyond software license permissions, third-party service incidents, resource exhaustion caused by customer scripts, and impacts caused by events beyond reasonable control. Support responses are based on verifiable device, order, and log information.
Limitation of liability and indemnification
VMOwn is responsible for the cloud Mac rentals, order management, and support processes it directly provides, within the scope set out in these terms. For issues caused by the customer’s network or configuration, third-party software, code repositories, payment processing, software licenses, automation scripts, or other factors not directly controlled by VMOwn, each party is responsible according to its actual area of control and the verifiable records.
You are responsible for evaluating your workload’s requirements for continuous operation, data integrity, build deadlines, and business delivery, and for configuring version control, backups, retries, and alternative execution paths. To the extent permitted by applicable law, VMOwn is not liable beyond what the law requires for lost profits, lost business opportunities, indirect losses, or data loss resulting from your failure to retain an independent copy.
If you breach these terms, infringe third-party rights, use the service unlawfully, or trigger a third-party claim through your data or actions, you must cooperate with the investigation, stop the relevant conduct, and bear the liability legally attributable to you. VMOwn will handle order, support, and system records related to the dispute based on lawful requirements and the principle of necessity.
Nothing in any limitation of liability excludes liability that applicable law does not permit to be limited or excluded. Liability will be determined in light of the causal relationship among the order records, scope of the incident, customer actions, support communications, and actual losses.
Changes to terms, service termination, and contact
VMOwn may update these terms in response to changes in service capabilities, order processes, security requirements, or applicable obligations. The updated version will be published on this website and will apply from the stated effective date. For confirmed orders, matters involving the configuration, amounts already paid, and current rental period remain governed by the order record and applicable terms.
You may stop renewing after the current rental period ends and complete your data export. If you seriously violate the acceptable-use requirements, threaten system security, repeatedly interfere with the service, or refuse to address a clearly identified risk, VMOwn may take lawful measures to restrict or terminate the service. After stopping use, you remain responsible for settling amounts due, revoking access, and completing necessary data export.
For questions about orders, devices, or renewals, sign in to the console and submit a support ticket. For general questions about these terms, rights requests, or partnership matters, email support@vmown.com. To help us respond efficiently, provide the issue type, order identifier, time of occurrence, and necessary details. Do not send complete passwords, private keys, or unrelated sensitive data.
These terms are governed by the laws of the jurisdiction where the platform operator is established. After a dispute arises, the parties should first seek resolution through support records and written communications. If the dispute cannot be resolved, it may be submitted to a court of competent jurisdiction in that jurisdiction.