Cloud Mac Rental and Usage Terms

When a user places an order, completes checkout, signs in to the console, connects to a device, or otherwise uses NUMACS services, they confirm that they have read, understood, and accepted these terms. Users acting for an organization also confirm that they are authorized to accept these terms, manage orders, and use devices on the organization’s behalf.

Users must have the legal capacity required to enter into an agreement and provide accurate, verifiable, and up-to-date account and order information. Impersonating another person, placing an order for an organization without authorization, or using false information to bypass security checks or usage limits is prohibited.

If a user does not agree to these terms, they must stop placing orders or using the service. Existing orders must still be handled according to their confirmed periods, charges, and data export requirements.

NUMACS provides dedicated physical Apple Silicon Cloud Mac workstations. Each device is dedicated physical hardware, not a virtual machine, and users access the device assigned to their order through remote desktop or SSH during the rental period. The public catalog includes only two tiers: NUMACS M4 Core and NUMACS M4 Plus.

Both tiers are available across nodes in Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. Catalog configurations can be ordered normally; actual availability is determined by the console in real time. After confirmation, the model, node, rental period, storage expansion, and Thunderbolt 5 parallel-device option are governed by the order record.

The service includes device access and necessary management capabilities. It does not replace the user’s own code repository, continuous integration platform, certificate management, build and release process, or project backup plan. Users must ensure that their software, plugins, licenses, and project materials meet all applicable rights and authorization requirements.

The service is available for daily, weekly, monthly, and quarterly rental. Before placing an order, users must check the model, node, period, additional storage, number of parallel devices, and total amount due. Once an order is confirmed, its billing period will not be shortened automatically based on actual connection time, task volume, or resource usage.

All amounts are displayed and settled in US dollars (USD). For changes caused by selecting the wrong model, node, period, or add-on, submit the order number and reason for the change through a console ticket first. Whether a change can be made depends on the device delivery status, current order record, and actual processing outcome.

NUMACS supports only two payment methods: USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All orders are settled in US dollars (USD). Available gateways, payment confirmation, and order status are shown in real time in the console.

Before paying, users must verify the network, recipient details, amount, and order number. Once an on-chain transfer is sent, users are responsible for confirming that the selected network matches the order requirements. Card payments are handled through the applicable payment processor; NUMACS does not store complete card credentials on its content site.

An order enters device allocation or renewal processing only after the settlement result has been confirmed and the order has reached the relevant processing status. Confirmation delays caused by banks, payment processors, blockchain networks, or the user’s own actions do not change the final order status recorded in the console.

Users may use the device for lawful software development, automated testing, continuous integration, data processing, AI experiments, audio and video production, and other workloads consistent with the order configuration. Users must ensure that their code, materials, data, dependencies, models, and software licenses come from lawful sources and have the necessary authorization.

• Do not engage in illegal activities.This includes using the device to create, store, distribute, or assist with illegal content or transactions.
• Do not access systems without authorization.Scanning, intrusion, bypassing authentication, stealing credentials, or interfering with systems, accounts, or networks that do not belong to the user is prohibited.
• Do not distribute malware.Running programs or scripts intended for disruption, extortion, covert control, credential theft, or large-scale abuse is prohibited.
• Do not abuse resources.Bypassing technical limits, affecting the stability of other devices or infrastructure, or generating abnormal network or storage loads is prohibited.
• Do not infringe third-party rights.Using protected software, code, materials, data, trademarks, works, or trade secrets without permission is prohibited.

If conduct may affect the security of the platform, devices, network, or third parties, NUMACS may require the user to stop the relevant tasks, provide necessary information, or complete risk mitigation. Users must cooperate by verifying timestamps, processes, network targets, and redacted logs.

Users are responsible for protecting console credentials, device login credentials, SSH keys, certificates, recovery materials, and project data. Access should be assigned according to actual responsibilities. The same credentials should not be shared indefinitely among unrelated members, and private keys or passwords must not be stored in public repositories, build logs, or publicly accessible scripts.

After first connecting to a device, users should change the initial credentials, configure their own SSH keys, verify remote desktop access, and check that administrator privileges match project requirements. After team changes, key exposure, unusual logins, or automated credential exposure, users must immediately rotate the relevant credentials and stop affected tasks.

After detecting an account or device anomaly, users should submit a console ticket or email support@numacs.com. To help us investigate, describe the affected order, node, and isolation measures already taken.

Users are responsible for continuously backing up code, build artifacts, project configuration, certificate materials, cache inventories, and other important data. A Cloud Mac should not be the sole copy of project materials. We recommend keeping source code in a repository with version control and access auditing, and copying critical artifacts to separate storage managed by the user.

Backup effectiveness should be assessed through restore tests, not merely by whether copying appears complete. Users should record toolchain versions, dependency lockfiles, environment variable sources, and build commands so workflows remain recoverable after device replacement, project migration, or cache cleanup.

1. A
   Back Up Throughout the Rental Period

   Save code, configuration, signing materials, and critical artifacts according to the project’s change frequency.

2. B
   Complete the Migration Out Before the End

   Export necessary data, revoke temporary access, and confirm that the destination can read it normally.

3. C
   Verify After Migration

   Spot-check repositories, archives, logs, and recovery scripts to confirm that copies are complete and permissions are correct.

Before the rental ends, an order terminates, or a device is reclaimed, users should allow sufficient time to complete migration out. After a device is released, its original working directory should no longer be treated as an available backup source.

Nodes in Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong operate normally 365 days a year. Device access still depends on the user’s local network, cross-region links, remote connection software, DNS resolution, payment confirmation, and other systems required to deliver the service.

Hardware failures, security incidents, upstream network issues, power or communications outages, and other events beyond reasonable control may require urgent technical action. NUMACS will take isolation, routing adjustments, device checks, or recovery measures appropriate to the scope of the incident and provide affected users with necessary information through available service interfaces.

When reporting a connection problem, users should record the time, node, destination address, remote connection method, error message, and diagnostic results. Without this information, it takes longer to distinguish issues involving the local network, target service, device status, and tool configuration.

If a user violates the acceptable use rules, accesses systems without authorization, causes a security risk to spread, reaches the order expiration, fails to complete settlement, or circumstances require action under applicable rules, NUMACS may restrict, suspend, or terminate the relevant account, order, connection, or device. The scope of action will correspond to the identified risk and necessary response.

Without increasing security risks, users may submit explanations, remediation evidence, and restoration requests through a console ticket. For malicious conduct, ongoing abuse, repeated violations, or clear risks to the platform or third parties, prior notice is not required before protective measures are taken.

Users are responsible for activity under their accounts, uploaded content, automated tasks, member permissions, and third-party tool configurations. Losses caused by a party’s breach of these terms, intentional conduct, gross negligence, or infringement of third-party rights will be borne by the responsible party to the extent permitted by applicable law.

For disputes, the parties should first communicate based on order records, ticket content, payment records, and verifiable technical evidence. If the dispute cannot be resolved through discussion, it will be governed by the laws of the jurisdiction where the platform operator is based and handled by a court with jurisdiction in that jurisdiction.

NUMACS may update these terms in response to changes in the service scope, payment processes, security requirements, or applicable rules. The effective date will be shown on this page. Updates that materially affect user rights, responsibilities, or services in use will be explained through available account or service notifications.

Continuing to place new orders or use the service after an update takes effect means that the user accepts the revised terms. Users with questions should review the new version before placing another order and submit the specific clause number, relevant order, and use case requiring clarification.

For questions about the terms, orders, payments, security, or data migration, visit theContact pageto review submission requirements, or email support@numacs.com. Users with existing orders should sign in to the console and submit a ticket first so it can be linked to the relevant device, node, and order records.