Cloud Mac Rental Order and Usage Rules

Service Definition

MacWorker provides Cloud Mac services that can be accessed remotely over the internet. Each valid order covers use of a dedicated physical Mac node during the rental period; its compute, memory, and base storage resources are not shared with other rental users. The node is a dedicated physical machine, not a virtual machine.

The service includes the node-ordering portal, order-status display, connection-information delivery, browser-based remote desktop and SSH access, billing records, and technical support. Available connection methods, operating-system version, and preinstalled tools are determined by the order information and portal display at delivery.

Service Scope

• Nodes may be used for remote development, builds, automation, testing, compatible AI inference experiments, and other lawful computing tasks.
• You receive the right to use the node for the agreed period. You do not acquire ownership of the node hardware, data-center facilities, network equipment, or portal software.
• All nodes operate continuously 365 days a year. Regional network events, single-node hardware failures, force majeure, and user actions may still affect particular connections or tasks.
• Actual performance depends on the selected chip, memory, SSD, workload, node region, and the user's local network conditions.

Account and Eligibility

You must have the legal capacity required to enter into and perform these terms. If you use the service for a company, team, or other organization, you confirm that you are authorized to place orders, configure nodes, and handle related billing on its behalf.

Registration and order details must be accurate, complete, and kept current. The email associated with your account is used for verification codes, order updates, connection information, security notices, and terms updates. Update your details promptly in the console, or request assistance through a console ticket.

Account Security Responsibilities

• Keep account credentials, node login details, SSH keys, and other access materials secure, and do not share them with unauthorized people.
• Model selection, region selection, rental-period confirmation, add-on configuration, node operations, and ticket submissions made through the account are generally treated as actions by the account user or an authorized member.
• If you discover exposed credentials, unusual login activity, or unauthorized node operations, change the relevant credentials immediately and submit a console ticket.
• When a team member leaves, a project ends, or responsibilities change, the account owner must promptly revoke that person's node access.

MacWorker may require reasonable verification of identity, order details, or payment status to handle account recovery, security incidents, billing disputes, or data requests. Do not obtain service by submitting false information, impersonating another person, or bypassing verification procedures.

Orders and Delivery

The order is determined by the selected model, node region, rental period, add-ons, real-time inventory, and the confirmation shown in the portal. Adding an option to the configuration flow does not reserve a node; the order enters node preparation only after the payment and portal order statuses meet the confirmation requirements.

Order Confirmation Steps

1. Choose your configuration Confirm the model, memory, base SSD, region, rental period from daily to quarterly, and any required storage expansion or Thunderbolt 5 linking.
2. Check inventory Nodes are offered subject to real-time inventory in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the U.S. East Coast.
3. Complete payment The portal records the payment method, USD amount, order ID, and payment status. A node is not considered delivered while payment is still being confirmed.
4. Receive connection details Once the node is ready, the portal provides its status, address, and login materials. Verify the destination address and host details when connecting for the first time.

Under normal conditions, choosing a model, region, and rental period, paying in USD, and receiving connection details takes about 4 minutes, with roughly 1 minute per step. This is a reference for the standard workflow; actual delivery depends on inventory, payment confirmation, and node status.

Configuration and Delivery Verification

After connecting for the first time, verify the chip, memory, disk capacity, system status, and network connectivity. If the delivered configuration does not match the order confirmed in the portal, stop any action that could further modify data and submit a console ticket with the order ID, node ID, discovery time, and configuration screenshots.

Differences caused by software installed by the user, system-setting changes, data deletion, or network-configuration changes do not constitute a delivery mismatch. Before resetting a node, confirm that data migration and backups are complete.

Pricing and Payment

The service uses the USD prices shown on the website and in the portal. All orders, bills, and payment records are settled in USD, with no conversion to other currencies. The order amount is calculated from the selected model, rental period, and add-ons and is governed by the confirmation recorded in the portal when the order is submitted.

The payment gateway actually available is determined by the result returned by the backend at payment time. Verify the receiving network, payment amount, and order ID. For USDT-TRC20 payments, selecting the wrong network, entering the wrong address, or sending an unmatched amount may prevent the payment from being automatically linked to the order.

Card transactions are processed by Stripe. MacWorker updates the order status based on the payment result and retains the transaction status and records needed to complete orders, reconcile bills, and conduct security reviews.

Payment Status and Billing Reconciliation

• If payment succeeds but the order status does not update, avoid paying again and submit a console ticket with the order ID, payment time, and a verifiable transaction summary.
• If payment fails, is declined, or remains pending, node preparation may be delayed until the portal shows a valid payment result.
• The model, rental period, and add-ons in the bill correspond to the order selections. Do not independently convert prices for different periods into an unlisted package price.
• You are responsible for confirming that your payment instrument supports USD transactions and that your payment complies with the rules applicable to you.

Rental Periods and Add-ons

Service periods are available by day, week, month, or quarter. The rental starts when the order is confirmed as complete and the node is marked as delivered, and ends according to the date shown in the portal. Before placing an order, make sure the selected period covers the time needed for builds, testing, data migration, and exporting results.

Period Selection Guidelines

• Daily rentals suit temporary builds, short-term validation, or focused testing with a defined end time.
• Weekly rentals suit release sprints, short-term expansion of CI/CD runners, or stage-based collaboration.
• Monthly or quarterly rentals suit tasks that require ongoing retention of dependencies, caches, model files, and development environments.
• Renewals, changes, and additional nodes are subject to the inventory, pricing, and confirmation shown in the portal at that time; resources from an expired order are not carried forward automatically.

Storage Expansion and Thunderbolt 5 Linking

Storage expansion and Thunderbolt 5 linking are optional order add-ons and must be selected clearly during configuration. An add-on is billed according to the applicable period shown in the order; reduced actual usage does not change that period.

Thunderbolt 5 linking is calculated per node. Before scheduling parallel tasks, confirm each device, connection relationship, and applicable period covered by the order. Additional storage expands the node's available capacity but does not replace independent backups of critical project data.

Acceptable Use

You may run lawful development, build, automation, testing, file-processing, and inference tasks that match the selected configuration on a dedicated physical Mac node. When using the service, you must comply with the laws, contractual obligations, software licenses, and third-party rights applicable to your activities.

Prohibited Conduct

• Conducting unlawful activities, or storing, processing, or distributing data and tools clearly intended for unlawful activities.
• Accessing, scanning, probing, interfering with, or controlling another account, device, network, system, or data without authorization.
• Creating, deploying, or distributing malicious code, including programs used to steal credentials, damage data, maintain covert control, or evade security measures.
• Abusing computing, storage, or network resources, generating sustained abnormal traffic, or disrupting normal use by the node's region, the portal, or other users.
• Infringing another person's copyright, trademark, privacy, trade secrets, or other lawful rights.
• Bypassing account verification, payment confirmation, access controls, resource limits, or technical measures used to protect service security.
• Reselling, subleasing, or making node access available to unspecified third parties without authorization.

Security Incident Response

When system records indicate that a node may be involved in high-risk or prohibited conduct, MacWorker may take proportionate measures, including restricting specific connections, asking the user to verify activity, suspending node access, or preserving necessary security logs. Measures will account for the urgency, scope, available evidence, and the user's response.

After receiving a security-verification request, provide enough information to explain the task, timing, relevant processes, and remediation steps. Do not send passwords, private keys, payment credentials, or complete project source code in ordinary email.

Data and Backup Responsibilities

A dedicated physical node provides a continuously retained working environment, but retention is not a backup. You are responsible for managing projects, source files, build artifacts, dependency caches, models, access credentials, databases, logs, and other content stored on the node, and should maintain independent copies according to the importance of the data.

Minimum Recommended Data Workflow

1. Before starting a task

   Confirm that recoverable copies of source data exist, and record versions of key tools, dependencies, and system configuration.

2. During the rental

   Regularly sync data that cannot be recreated to a secure location you control; do not keep it only on the node's local disk.

3. Before changing configuration

   Save necessary recovery points and change records before reinstalling tools, adjusting disks, changing permissions, or running batch scripts.

4. Before releasing the node

   Export projects, artifacts, key materials, and logs required for auditing. Verify that copies can be read before clearing node data.

Credentials and Support Materials

Use separate credentials to manage your code repositories, build systems, and other business resources. When requesting technical support, submit only the minimum diagnostic information needed to locate the issue, such as the node ID, time of occurrence, connection method, error summary, reproduction steps, and sanitized log excerpts.

Do not paste private keys, passwords, payment credentials, or complete project source code into ordinary support emails or tickets. If diagnostic material may contain personal information, business data, or access tokens, delete, redact, or replace those fields first.

Suspension, Termination, and Liability Boundaries

MacWorker may restrict, suspend, or terminate an account or node in response to a clear violation, security risk, abnormal payment status, signs of unauthorized access, or a technical incident that could increase the impact. Measures will be proportionate to the risk, and where conditions permit, the reason and next steps will be provided through the portal, the email linked to the account, or a ticket.

Suspension and Restoration

• If payment is incomplete, the transaction status is abnormal, or the order cannot be verified, node delivery or continued use may be delayed.
• If exposed credentials, malicious processes, unusual network activity, or unauthorized access are detected, related connections may be restricted first to prevent further impact.
• After the user completes identity verification, payment reconciliation, risk remediation, or corrective action, MacWorker will assess restoration of access based on the node status and incident outcome.
• Suspension does not change the user's responsibility to back up and migrate critical data. If a controlled export path can be provided, the specific steps will be described in the ticket.

End of Rental and Early Termination

When the rental ends, the user's right to use the node ends with the order period. The service may end early if the user releases the node, seriously violates acceptable-use rules, repeatedly refuses security verification, or fails to meet the order's payment conditions. Whether time for data export can be provided before termination depends on the urgency of the risk, node status, and applicable requirements.

If a security incident requires immediate connection blocking, access may be restricted first, followed by an incident explanation through the account email or a console ticket. If you have questions about the outcome, submit a console ticket with the order ID, node ID, incident time, and relevant evidence.

Network Events and Hardware Failures

Regional network disruptions, local carrier routing changes, force majeure, or single-node hardware failures may affect connection quality or task continuity. MacWorker will determine the appropriate response using verifiable node status, network observations, and hardware diagnostics, which may include restoring the connection, migrating to an available node, replacing failed hardware, or providing another response proportionate to the affected scope.

Issues caused by the user's local network, client settings, incorrect credentials, user-installed software conflicts, scripts, permission changes, or data deletion are the user's responsibility to investigate and fix. MacWorker may provide diagnostic steps within the available support scope. Both parties should determine responsibility using order records, node logs, payment status, and reproducible evidence rather than relying on a single error message.

Changes to These Terms, Governing Law, and Dispute Resolution

MacWorker may update these terms due to changes in service features, order processes, security requirements, or applicable rules. Updates that materially affect user rights or obligations will be reasonably notified through the website, portal, or account email. Updated terms apply to new orders submitted after they take effect and to services the user continues to use.

These terms and service-related disputes are governed by the laws of the jurisdiction where the platform operator is based. In a dispute, the parties should first communicate in good faith using order records, payment status, node logs, and support tickets. If the matter cannot be resolved through communication, it may be submitted to a court with jurisdiction in that jurisdiction.

Contact and Evidence Submission

For order, node, security, or billing issues, first sign in to the console and submit a ticket so it can be linked to your account and node records. If you cannot access the console or need to submit a written request regarding these terms, email support@macworker.com. Include the order ID, issue type, time of occurrence, and requested action in your request. Do not include passwords, private keys, payment credentials, or complete project source code.