Service definition
VMDebug provides the dedicated physical cloud Mac, node connectivity, and related management capabilities specified in the confirmed order. Each device’s compute, memory, and local storage resources are dedicated to that order. Delivery is on a physical node, not a virtual machine.
The order defines the actual delivery scope
The order confirmation determines the exact model, chip, memory, internal storage, additional storage, Thunderbolt 5 pairing option, node, rental term, and amount due. The current public catalog includes VMDebug M4 and VMDebug M4 Pro; real-time availability returned by the console determines whether the order can be created.
Nodes are available in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the western United States. Node selection identifies the service region where the device is located; it does not guarantee fixed latency, routing, or third-party network quality between you and the node.
The physical device resources in the order do not share the processor, memory, or local system disk with other customer orders.
The console includes order status, connection details, renewal access, billing records, and support tickets.
You may use macOS graphical and command-line capabilities. Actual permissions, ports, and additional configuration are determined by the order.
Delivery acceptance
After receiving the connection details, verify the device identifier, host fingerprint, system version, disk capacity, and network connectivity. If the configuration differs from the order confirmation, stop writing important data and submit a console ticket with the order number, device identifier, verification results, and necessary screenshots.
Accounts and authorization
The account holder is responsible for controlling access, protecting credentials, and ensuring that all authorized users understand these terms. Orders, configuration changes, tickets, and device operations initiated under the account are considered actions authorized by the account holder.
Credentials and access control
- Provide console, SSH, or graphical-session credentials only to people with a genuine business need, and assign access according to least privilege.
- Change temporary credentials promptly after the first connection. Never store plaintext passwords or private keys in code repositories, public build logs, public tickets, or chat records.
- When someone leaves the team, changes responsibilities, or credentials may have been exposed, immediately revoke access, rotate keys, and review recent activity.
- Do not resell accounts, share uncontrolled public login entry points, or allow unidentified third parties to operate the device directly.
First isolate the affected credentials and preserve necessary logs, then submit a console ticket. Include the order number, device identifier, approximate incident window, source-address clues, and actions already taken. Do not submit complete passwords, wallet private keys, or full card numbers.
User-submitted content
You must ensure that uploaded code, assets, keys, certificates, models, datasets, and build inputs have lawful sources and the necessary authorization. VMDebug processes this content to fulfill the order but acquires no intellectual property rights in it; you remain responsible for the content, instructions, and resulting output.
Orders and billing
Service terms are available by day, week, month, or quarter. The base model, term, node, and optional add-ons together form the order, and all amounts are priced and settled in USD.
| Term | Best suited for | Confirm before ordering |
|---|---|---|
| Day | Short-term troubleshooting, one-time archiving, environment validation | Start and end times, node, and data-export plan |
| Week | Iteration sprints, concentrated testing, temporary runners | Task duration, cache capacity, and renewal point |
| Month | Continuous builds, fixed development environments, stable experiments | Long-term keys, available disk space, and renewal rules |
| Quarter | Stable pipelines, ongoing projects, long-term device use | Toolchain lifecycle, upgrade plan, and person responsible for data export |
Payment methods
We support only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The payment gateway actually available is determined by the console. Before paying, verify the currency, recipient details, network type, and order amount. You are responsible for processing costs caused by selecting the wrong network, entering an incorrect address, or submitting a payment more than once.
Card transactions are processed by Stripe. VMDebug will never ask you to provide a full card number, security code, account password, or wallet private key in support emails or tickets. For transaction verification, submit only the order number, transaction time, amount, and transaction identifiers that can be safely disclosed.
Charges and records
Before creating an order, the console displays the selected model, rental term, node, add-ons, and USD total. After you confirm and complete payment, the order record becomes the billing basis. Banks, card issuers, blockchain networks, or payment processors may charge their own fees; these are not part of the VMDebug order amount.
If you find a duplicate order, an abnormal amount, or a payment status that does not match the actual transaction, retain the order number and transaction record and submit a ticket. Do not pay the same order again before verification is complete.
Renewals and expiration
Renewals must be completed in the console and are governed by the term, amount, and availability shown at the time of renewal. Support communications, verbal intent, or an incomplete payment step do not constitute a successful renewal.
Before renewing
- Confirm the current order’s end time, target renewal term, and USD total.
- Confirm that the device, node, additional storage, and pairing topology still meet the requirements of your upcoming work.
- Check available disk space, build queues, and expected completion times for long-running tasks to avoid crossing the order end time.
- Prepare independent backups for critical code, keys, certificates, build artifacts, logs, and configuration.
Export code, keys, assets, non-rebuildable cache data, and final artifacts, then verify that they are readable at the destination.
Stop new builds, uploads, and long-running computations; confirm that the queue is empty and record the last successful task and log location.
Access to the device may stop after the order ends. Content that has not been exported must not be treated as continuously accessible or as a long-term backup.
You are responsible for exporting data and verifying backups while the order is active. VMDebug does not treat local device storage as a substitute for your repository, artifact store, key-management system, or backup plan. If you need help determining export steps, submit a console ticket before the order ends.
Acceptable use
You may use the device for lawful software development, automated testing, CI/CD, AI experiments, and remote media toolchains. Your use must not harm the platform, node network, other users, third-party systems, or the public interest.
Do not use the device to conduct, assist with, or conceal activities that violate applicable rules, or process content you know you have no right to possess or distribute.
Do not scan, probe, log in to, or control systems, accounts, networks, interfaces, or data without authorization.
Do not create, host, distribute, or run code intended to cause damage, steal, extort, maintain covert control, or evade detection.
Do not launch denial-of-service attacks, send spam, generate deceptive traffic, conduct malicious scraping, or make connection attempts clearly beyond normal development use.
Do not bypass access restrictions, isolation measures, billing logic, rate limits, auditing capabilities, or other security controls.
Do not infringe copyrights, trademarks, trade secrets, privacy rights, software licenses, or other legally protected rights.
Investigation and response
Upon receiving a credible abuse report, identifying a significant security risk, or when processing is legally required, VMDebug may ask you to explain the use, stop related tasks, remove risky content, or provide authorization materials. To limit ongoing harm, VMDebug may temporarily restrict related connections or device access and retain necessary audit records.
You must cooperate with reasonable investigations and must not delete key evidence, falsify logs, or continue expanding the impact. If serious unlawful activity, malicious attacks, repeated abuse, or refusal to remediate is verified, VMDebug may terminate the related order or account access.
Service level
VMDebug targets 99.9% availability. Nodes are designed to run continuously 365 days a year, with no preset downtime periods as part of normal operations. Actual availability is calculated separately for the affected order, device, and applicable service term.
Calculated from the time during the applicable order term when you can connect and perform basic device operations.
The specific affected order, physical device, and node connection—not another order that is operating normally.
Calculated for the affected order’s applicable service term; if an order spans multiple terms, each term is assessed separately.
Availability = (total minutes in the applicable term − confirmed unavailable minutes) ÷ total minutes in the applicable term.
Confirming unavailable time
Unavailability generally means that, with valid credentials, an active order, and a normal local network, you cannot connect to the specified device, or the device cannot perform basic operations because of hardware, power, node-network, or management-system issues within VMDebug’s control. For intermittent issues, the applicable period is the duration jointly confirmed by logs, monitoring records, and the ticket timeline.
Excluded circumstances
- Interruptions caused by your shutdown, restart, system upgrade, firewall changes, deleted connection configuration, or other actions.
- Unavailability caused by your network, carrier routing, endpoint device, code, dependencies, build scripts, software licenses, or third-party services.
- Invalid account credentials, an expired order, incomplete payment, access restrictions resulting from a breach of these terms, or refusal to provide necessary troubleshooting information.
- Force majeure, widespread public-network failures, government action, or other events beyond VMDebug’s reasonable control.
Claims and service credits
Submit a console ticket with the order number, device identifier, outage start and recovery times, connection source, error messages, redacted logs, troubleshooting steps completed, and the minimum information needed to reproduce the issue. Only events within VMDebug’s service scope, confirmed by records, that reduce availability below 99.9% for the applicable service term qualify for service-credit calculation.
When eligible, service credits are calculated for the affected service term and based on the order’s actual impact. Credits do not automatically extend to unaffected devices, expected user revenue, third-party fees, or periods that records cannot verify. If a claim is incomplete, VMDebug may request additional materials before continuing its review.
Third-party services
Cloud Mac workflows commonly connect to Apple, code hosting, software licensing, package management, network carriers, payment processing, and app review services. Those services are controlled by their respective providers; VMDebug does not guarantee their availability, rules, or review outcomes.
Determining responsibility
VMDebug is responsible for the physical device, node connectivity, and management capabilities covered by the order. Whether a project compiles, certificates pass, dependencies download, third-party accounts can be accessed, software licenses remain valid, an app passes review, or public routing meets your expectations depends on your configuration and the relevant third-party rules.
Device power, hardware status, order configuration, node-side connectivity, console records, and reproducible basic system issues.
Project code, certificate chains, Keychain permissions, dependency versions, build scripts, software licenses, and repository permissions.
External platform policies, account status, content review, network routing, interface limits, and third-party service availability.
First distinguish among “the device cannot connect,” “the system connects but the tool fails,” and “a third-party platform rejected the request.” Providing the redacted original error, timestamp, and minimal reproduction steps can reduce back-and-forth between different areas of responsibility.
Liability, changes, and dispute resolution
This section defines the scope of service commitments, liability caps, force majeure, terms updates, notices, termination conditions, and dispute-resolution principles.
Service commitments and user judgment
VMDebug provides services according to the order confirmation, these terms, and applicable documentation, using reasonable engineering measures to keep the device and management capabilities available. You should choose the rental term, node, backup plan, and toolchain according to project risk, and should not treat a single device, local disk, or network path as an irreplaceable sole copy.
Except for the service level and service credits expressly stated in these terms, project delivery dates, build results, commercial returns, third-party review outcomes, and continued compatibility with specific software are not guaranteed order results.
Liability cap
To the extent permitted by applicable rules, VMDebug’s aggregate liability for a single event or related events is limited to the fees you actually paid VMDebug for the affected order’s service term. This cap does not limit liability that cannot legally be excluded or limited.
Losses increased because you failed to maintain backups, protect credentials, export data, or take reasonable steps to mitigate harm are outside VMDebug’s responsibility. Both parties should retain relevant orders, logs, tickets, and payment records and take reasonable measures to prevent further impact.
Force majeure
If natural disasters, war, major public-network failures, government action, public-infrastructure outages, or other events beyond a party’s reasonable control prevent performance, the affected party should notify the other party promptly where feasible, explain the impact, and take reasonable mitigation measures. After the event ends, each party should resume the portions it can perform.
Terms updates and notices
VMDebug may update these terms in response to changes in service capabilities, payment processes, security requirements, or applicable rules. Material changes to user rights or obligations will be indicated through the website, console notices, or the support channel associated with the account. Updated terms apply to orders created or renewed after they take effect; content requiring separate legal consent applies after you confirm it.
You can contact support@vmdebug.com or submit a ticket through the console to ask about the terms version, rules applicable to an order, or notice content. This is the only external contact email.
Suspension and termination
If you materially breach acceptable-use rules, endanger platform or third-party security, refuse to cooperate with a necessary investigation, fail to pay amounts due, or continue high-risk conduct after being told to stop, VMDebug may restrict access to the related device, order, or account. Measures will be determined based on the urgency of the risk, scope of impact, and recoverability.
Termination does not affect payment obligations incurred before termination, data-export responsibilities, confidentiality requirements, intellectual-property ownership, liability limitations, or dispute-resolution terms. Before closing the account, you must complete necessary data export while access remains available.
Governing rules and dispute resolution
The formation, interpretation, performance, and dispute resolution of these terms are governed by the laws of the jurisdiction where the platform operator is based. The parties should first submit the facts, order records, and requested resolution through a support ticket or support@vmdebug.com and seek a reasonable negotiated resolution.
If negotiation fails, either party may bring proceedings before a court with jurisdiction in that jurisdiction. If any part of these terms is held invalid or unenforceable, the remaining provisions remain effective to the extent permitted by applicable rules.