Cloud Mac Rental & Service Terms

01

Acceptance and Applicability

By creating an order, completing payment, accessing the console, connecting to an instance, or otherwise using XcodeVM services, you confirm that you have read, understood, and agreed to these service terms, the related Privacy Policy and order confirmation rules. If you act for a company, team, or other organization, you confirm that you are authorized to accept these rules on its behalf.

These terms apply to purchasers, account holders, team members authorized to operate instances, and anyone using the service through automated tasks. Account holders must ensure that their authorized users know and follow these terms. Internal team permissions for devices, repositories, or build tasks do not change the account holder’s responsibility for orders and account activity.

Checks to complete before accepting

• Confirm that the selected model, memory, storage, region, and rental term meet your requirements.
• Confirm that your team can connect remotely and securely store login credentials and keys.
• Confirm that your use case complies with the acceptable-use rules on this page.
• Confirm that you understand your responsibilities for data migration, application-level backups, and handling data after the rental term ends.

If you do not agree to these terms, do not submit an order, make a payment, or use the service. For an unpaid order, you may simply stop the process. The handling of a confirmed order is governed by its status and these terms.

02

Service Description

XcodeVM provides Cloud Macs for remote development, automated builds, iOS/macOS packaging, and MLX experiments. Each order is assigned a dedicated physical machine running on a physical node, not a virtual machine. You may use the macOS graphical interface and command line, and configure development tools, code repositories, build caches, and automated workflows for your tasks.

This catalog currently includes two Mac Mini M4 configurations: XVM M4 Core with M4, 16GB RAM, and 256GB SSD; and XVM M4 Plus with M4, 24GB RAM, and 512GB SSD. Available regions are Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. Both models support all four regions; actual availability is returned in real time by the console.

The model, region, term, storage expansion, and Thunderbolt 5 parallel-connection options are governed by the confirmation shown before payment. Orders are independent. Configurations, remaining time, or add-ons purchased in one order do not transfer automatically to another order.

Service boundaries

Device resources

The processor, memory, and base storage assigned to an order are dedicated to that order and are not shared with another user as the same running instance.

Region selection

The region identifies where the device is located. Connection quality also depends on your location, carrier routing, cross-border links, and local network.

Software environment

You may configure the development environment within the scope of your authorization, but you are responsible for verifying tool versions, dependencies, signing materials, and project compatibility.

Service term

Services run for the day, week, month, or quarter specified in the order confirmation. The order record determines the start and end times.

All regions operate normally 365 days a year. XcodeVM may take necessary action for security isolation, incident response, or infrastructure risks and will provide notice through the console or account contact details where reasonably feasible.

03

Account and Credential Responsibilities

You must provide accurate, complete account information that can be used for service notices and update it promptly when it changes. Do not impersonate another person, bypass account verification, transfer disputed orders, or use multiple accounts to evade payment, security, or usage controls.

Login credentials, instance connection details, repository keys, signing materials, and automation tokens must be treated as sensitive information. Use strong credentials, restrict sharing, review authorization regularly, and immediately replace credentials if you suspect exposure. Do not share them through public repositories, public logs, screenshots, or unencrypted messages.

Attribution of authorized actions

Actions performed through a valid account session, valid instance credentials, or user-configured automation tokens are generally treated as authorized account actions. Account holders must manage permissions for team members, contractors, and automated tasks and are responsible for order changes, instance configuration, data deletion, and ticket submissions under the account.

If you discover an unusual login, unknown order, exposed credential, or unauthorized instance operation, immediately update the relevant credentials and submit a ticket through the console. Include the order ID, region, discovery time, observed issue, and steps taken, but do not attach passwords, private keys, complete payment credentials, or unredacted business data.

04

Orders and Billing

XcodeVM supports daily, weekly, monthly, and quarterly plans. All prices and order totals are displayed and settled in US dollars (USD). Before paying, verify the model, region, term, storage expansion, number of Thunderbolt 5 parallel connections, and total due. After confirmation, the order runs according to the selected term and configuration.

The pricing page presents the standard catalog; the order confirmation records a specific transaction. If you use multiple browser windows, submit repeatedly, or create multiple orders at once, verify each order ID and status in the console. Do not rely solely on a payment screenshot or local records to determine whether service is confirmed.

Order status and service term

• Pending payment: The order has not completed valid settlement and does not constitute activated service.
• Processing: Payment details are being verified or the order is being configured. Avoid creating the same order again.
• Active: The service term has started. The console order record determines the exact start and end times.
• Ended: The service term has expired or the order has ended under the applicable rules. Complete data migration beforehand.

If you want to continue using the service, verify the renewal configuration, amount, and payment status before the current term ends. A renewal is effective only when confirmed by the console; creating a renewal order, initiating an on-chain transfer, or submitting a card payment request does not itself confirm renewal.

Any necessary taxes, bank charges, or on-chain transfer fees shown at checkout must be reviewed by the payer before confirmation. For issues caused by incorrect user information, selecting the wrong network, insufficient payment, or duplicate payment, submit the order ID and redacted transaction details through a console ticket for review.

05

Payment Methods

XcodeVM supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All orders are settled in US dollars (USD). The payment gateway actually available is determined by the backend response at checkout. You must ensure that your payment instrument is authorized for lawful use and that the payment details match the order requirements.

USDT-TRC20 payments

Verify the network, receiving address, transfer amount, and order ID. Transfers sent over another network, to an incorrect address, for an insufficient amount, or without following the order requirements may prevent automatic confirmation. Once broadcast, an on-chain transaction generally cannot be recalled by XcodeVM. Check every field again before submitting.

Card payments

Visa, Mastercard, and Amex payments are processed by Stripe. Your card issuer may require additional verification. If a payment request is declined, verification is incomplete, or a payment is later reversed, the order may remain unconfirmed and active services may be restricted based on risk and outstanding balances.

Refunds, renewals, and failed payments

Refund eligibility depends on the order status, whether service has started, the results of incident review, and applicable mandatory rules. Where XcodeVM is responsible and the conditions for an availability credit on this page are met, the service-credit rules apply first. If you select the wrong model, region, term, or add-on, submit a ticket promptly; however, an active order may not be changeable or cancellable.

A renewal becomes effective only after payment is completed and confirmed in the console. If payment fails, is reversed, is disputed, or remains overdue, XcodeVM may restrict new orders, suspend affected services, or terminate the relevant order and retain records necessary for billing review.

06

Acceptable Use

You may use the service only for lawful and authorized development, build, testing, research, and business activities. Automation does not change your responsibility. Set reasonable permission, concurrency, and resource limits for scripts, runners, agents, and remote operations.

Prohibited activities

• Conducting unlawful activities or storing, processing, or distributing clearly unlawful content.
• Accessing, scanning, probing, controlling, or interfering with any account, device, service, or network without authorization.
• Distributing malware, ransomware, or credential-theft tools, or building infrastructure for attacks, fraud, or bypassing security controls.
• Using an instance to send spam, perform credential stuffing, bulk account attacks, traffic amplification, or other abusive activity.
• Intentionally exhausting network, storage, power, or management resources and affecting infrastructure or other users.
• Evading billing, verification, access controls, risk detection, service limits, or suspension measures.
• Deleting, altering, or falsifying records related to security incidents, orders, or authorized actions.
• Reselling, subdividing, or providing an instance to third parties not managed by the account holder.

When activity may create a real and imminent security risk, XcodeVM may first restrict the relevant connection, isolate the affected instance, or suspend service, then ask you for further information. Provide the purpose, relevant processes, time range, and redacted logs within the time stated in the notice. Service may be terminated if authorization cannot be demonstrated or you refuse to stop the risky activity.

Security research, load testing, and network scanning may target only systems you own or are expressly authorized to test, and must be limited in frequency and scope. Do not use XcodeVM nodes as an exit point for broad public-network scanning, attack validation, or bypassing access restrictions.

07

Data and Backup Responsibilities

You are responsible for workloads, source code, build artifacts, keys, signing materials, dependency caches, model files, and business data on the instance. XcodeVM provides the runtime environment but does not replace your version control, key management, release archiving, or application-level backup processes.

Minimum data-management requirements

• Keep source code in a controlled repository rather than only on one instance.
• Restrict access to keys and signing materials, store them separately, and avoid writing them to build logs or repository history.
• Copy important build artifacts to a user-controlled destination after creation and verify file integrity.
• Before using an expanded SSD, confirm its mount point, permissions, and available capacity; verify files by sampling after migration.
• Redact logs and ticket attachments first, removing tokens, personal information, complete request payloads, and business secrets.
• Complete data export, credential rotation, and deactivation of automated tasks before the rental term ends.

Before running a reinstall, disk format, directory cleanup, key replacement, or automated deletion script, verify the target path and backup status. The account holder is responsible for data changes caused by user commands, scripts, permission settings, or team-member actions.

After an order ends, an unpaid balance triggers termination, or a violation causes termination, the instance may no longer allow connections. Do not treat access after the term ends as a data-retention solution. To verify the end time, rely on the console record and allow enough time for migration before the term ends.

08

Availability and Service Credits

XcodeVM targets 99.9% availability. Availability is calculated separately for each active instance and each calendar month; different instances or months are not combined. Time before service starts, after it ends, or while it is suspended for nonpayment or violations is excluded from the valid measurement window.

Unavailable means that an instance cannot establish a remote connection from the XcodeVM node side for at least 5 continuous minutes, and service records confirm that the device or node is unreachable. A failed application build, code error, dependency issue, user configuration problem, or slow graphical interface does not by itself constitute service unavailability.

Events excluded from unavailable time

• Impact caused by the user shutting down, restarting, or reinstalling the instance, changing network settings, or adjusting access controls.
• Connection issues caused by the user’s network, carrier routing, endpoint device, client software, or third-party dependencies.
• Isolation, restriction, or suspension caused by malicious traffic, prohibited use, security risks, or unpaid balances.
• Natural disasters, public-infrastructure failures, government action, war, major network incidents, and other events beyond reasonable control.
• Reports that cannot be verified because they lack the order ID, region, incident time, or necessary diagnostic information.

Service credit schedule

The service-credit cap for one instance and one measurement window is 25% of that instance’s applicable term fee. Credits cannot be exchanged for cash, transferred to another account, or applied to add-on fees, taxes, on-chain fees, or payment-provider fees.

You must submit a ticket through the console within 7 calendar days after the incident, including the order ID, region, start and recovery times, carrier, reproduction steps, and redacted logs. XcodeVM will review node records, device status, and ticket materials. Repeated reports of the same incident do not generate duplicate credits.

09

Suspension, Termination, and Liability Boundaries

If an order is overdue, a payment is reversed, the account presents a significant security risk, the user violates the acceptable-use rules, or continued operation could affect infrastructure or other users, XcodeVM may restrict connections, suspend the instance, isolate related data, or terminate the affected order. The action should be limited as far as reasonably possible to the relevant account, instance, or task.

Notice and restoration

When there is no urgent risk, XcodeVM will explain the reason and required action through a console notice, ticket, or account contact information. After you complete payment verification, stop prohibited activity, update credentials, or provide required materials, XcodeVM may decide whether to restore service based on its risk assessment. For urgent security incidents, restrictions may be applied first, followed by notice and review.

You may choose not to renew and should stop tasks, export data, revoke automation tokens, and rotate relevant keys before the current term ends. Ending use does not waive obligations relating to confirmed orders, incurred charges, violations, or other obligations arising before termination.

Liability boundaries

To the extent permitted by applicable rules, each party is responsible for conduct within its reasonable control. XcodeVM handles verified service unavailability under the service-credit rules in these terms. You are responsible for your code, data, keys, signing materials, software licenses, automated tasks, account authorization, and application-level backups.

Losses caused by force majeure, the user’s own actions, the user’s network, third-party dependencies, or unauthorized activity will be assessed according to the cause, scope of control, and applicable rules. When either party discovers an event that could increase the impact, it must take reasonable steps to limit losses and retain necessary records for review.

Changes to these terms

XcodeVM may update these terms due to changes in service offerings, risk controls, payment processes, or applicable obligations. Material changes affecting existing users will be notified through the website, console, or account contact information. Updated terms apply to subsequent access, use, and new orders from the stated effective time; the specific configuration and term of a confirmed order remain governed by its order record.

Governing law 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 located, without affecting mandatory rights that cannot lawfully be excluded. In a dispute, the parties should first submit the order ID, facts, relevant records, and desired resolution through a ticket or to support@xcodevm.com and negotiate in good faith.

Disputes not resolved through negotiation must be submitted to a court with jurisdiction in that jurisdiction. If any provision is found invalid or unenforceable, the remaining provisions remain effective; the invalid provision will be interpreted within the lawful scope that most closely reflects its original intent.