Scope and definitions
These terms apply when customers access the OnceMac website, create or manage a service account, place a Cloud Mac order, use a physical node, or handle order-related matters through support channels. The order confirmation page, specific configuration details, and these terms together form the agreement for the service. If an explicit configuration in the order differs from general information, the final order record confirmed by both parties controls.
- OnceMac
- The platform and its operating entity providing Cloud Mac rental, order management, node delivery, and support services.
- Customer
- The individual or organization that creates an account, places an order, makes a payment, or actually uses the service. Anyone acting for an organization must have appropriate authorization.
- Cloud Mac
- A macOS computing environment accessed by the customer over the internet for building, testing, development, or experimentation. This term describes the delivery model and does not change the fact that the device is a physical node.
- Physical node
- An independent Mac mini device and the necessary network connection hosting the customer's workload. Each valid order corresponds to a separate node; its compute, memory, and local storage are not shared with other customers.
- Dedicated physical machine
- A physical device used exclusively by one customer during the applicable rental term, rather than a shared computing instance divided through virtual machines.
- Order
- The complete record of the customer-confirmed model, node, rental term, price, add-ons, payment status, and delivery information.
- Rental term
- The service period confirmed in an order—daily, weekly, monthly, or quarterly—starting when delivery information becomes available and according to the order rules.
- Add-ons
- Items selected beyond the base configuration, such as +1TB SSD, +2TB SSD, or Thunderbolt 5 interconnect. Availability is subject to the specific order.
- Console
- The service portal described in these terms, used to view orders, payment status, node information, connection details, renewal options, and support tickets.
Services and orders
OnceMac offers three dedicated physical Mac configurations: OnceMac M4 16, OnceMac M4 24, and OnceMac M4 Pro 64. Before submitting an order, customers must check the model, memory, base storage, target node, rental term, and add-ons. Actual availability at the six nodes—Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, and US West—is based on the real-time results returned by the console when the order is submitted.
When is an order formed?
Selecting a configuration or generating payment details does not mean that an order has been confirmed. An order is formed only after the payment status is confirmed by the system, the selected configuration passes validation, and a valid order record is created. Customers should retain the order number and immediately stop further action and contact support through a ticket if the model, node, term, or add-ons do not match their expectations.
What does an order record include?
- The selected model and its chip, memory, and base storage;
- The selected service node and the basis for the rental term dates;
- The base service price, add-ons, and USD settlement amount;
- The payment method, payment confirmation status, and transaction identifiers;
- Node delivery status, connection details, and subsequent change records.
Customer-submitted notes become part of the service scope only when explicitly accepted in the order record. Requirements for specific software versions, network policies, batches of nodes, or special hardware connections must be confirmed through the support email before payment; they cannot be treated as commitments based solely on free-text notes.
Pricing and payment
All prices are listed and settled in US dollars (USD). OnceMac supports only USDT-TRC20 and Visa / Mastercard / Amex through Stripe. The payment gateway available at a given time, payment status, and order confirmation result are determined by the record returned by the console.
Check before paying
Customers must confirm the order number, USD amount due, payment network, recipient details, and validity period. When using USDT-TRC20, customers must select the correct network and cover any on-chain fees charged on the payment side. Card verification is handled by the applicable payment gateway.
Payment confirmation
A payment page showing that a submission was made does not mean that the funds have been confirmed. Card authorization, on-chain confirmation, or a payment gateway response may take time to process. The system updates the order only after receiving a verifiable successful status. Customers may not substitute screenshots, pending records, or self-generated transaction information for the final status shown in the console.
Price changes and existing orders
OnceMac may change catalog prices for future new orders, but a confirmed current rental term continues to follow its order record. A renewal is a new term confirmation, so customers must review the configuration, price, and add-ons shown on the renewal page again. Any taxes, payment-side fees, or costs arising from the customer's own financial services are borne by the party responsible under applicable law or the relevant payment rules.
Payment discrepancies
If the amount, network, transaction identifier, or order association does not match, customers must submit a console ticket with the order number, redacted payment proof, and verifiable transaction information. Do not send complete card details, keys, or other sensitive information that could be used directly for payment in a ticket or email.
Delivery, renewals, and changes
A node is delivered when usable node information and connection details appear in the console. After receiving delivery information, customers should promptly check the model, node, system reachability, and connection method. If they find an issue, they should retain timestamps, command output, and redacted logs so the support team can investigate.
Term start and renewal
The rental term starts according to the period confirmed in the order and the delivery record. Customers are responsible for monitoring the term information and renewal entry in the console. A renewal takes effect only after the new payment status is confirmed; an unconfirmed action does not automatically extend the service term. To prevent interruptions, customers should back up code, build artifacts, and necessary data before the current term ends.
Configuration and node changes
The model, memory, and base storage are physical node configurations and cannot be guaranteed to switch in place while running. Customers needing an upgrade, downgrade, or node replacement will generally need to create a new order or have the support team confirm a migration path. Customers participate in file copying, dependency rebuilding, permission checks, and toolchain validation during migration.
Storage expansion and device interconnection
+1TB SSD, +2TB SSD, and Thunderbolt 5 interconnection are add-ons. Whether they can be added to an existing order depends on node conditions, the current configuration, and operational arrangements. Thunderbolt 5 interconnection is charged per device and must not be understood as a default part of the base plan. An add-on takes effect only after explicit confirmation in the console or a written support record.
Protecting delivery information
Connection addresses, usernames, keys, and other access details are for authorized personnel only. Customers should share them internally through secure channels and avoid placing them in public code repositories, build logs, chat screenshots, or documents without access controls.
Acceptable use
Customers may use Cloud Mac for lawful software development, automated builds, testing, remote development, and computing experiments, but may not use the service to infringe the rights of the platform, other customers, or third parties. Customers are responsible for the conduct of their users, scripts, runners, and automated tasks on the node.
Prohibited activities
- Illegal activity: Using a node to conduct, assist with, or conceal activity that violates applicable law.
- Unauthorized access: Scanning, probing, bypassing authentication, or attempting to access accounts, devices, networks, or data without authorization.
- Malware distribution: Creating, hosting, or distributing programs intended to damage, steal, control, or evade security mechanisms.
- Network abuse: Launching denial-of-service attacks, malicious scraping, traffic amplification, credential stuffing, or other activity that harms network stability.
- Infringing content: Storing, processing, or distributing content protected by intellectual property rights, privacy rights, or other lawful interests without authorization.
- Service disruption: Evading resource limits, interfering with node management, tampering with platform components, or endangering platform or third-party infrastructure.
OnceMac may investigate based on abnormal traffic, credible reports, system alerts, or legal requirements. Investigations will be limited to what is necessary. Customers must explain the purpose of their workloads, mitigate risks, and stop clearly prohibited activity. Failure to cooperate or an ongoing risk may result in access restrictions, suspension, or termination.
Customer responsibilities
A dedicated physical machine provides resource isolation but does not replace the customer's own engineering management, security configuration, or data protection processes. Customers should establish access control, backup, and audit mechanisms appropriate to code sensitivity, team size, and release requirements.
Code and data
Confirm that you have the right to upload and process the relevant code, models, assets, and data, and maintain independent backups with a verifiable recovery path.
Accounts and keys
Use unique credentials, limit key permissions, rotate access details promptly, and revoke access immediately when a team member leaves or responsibilities change.
Signing certificates
Protect code-signing materials, private keys, and configuration files yourself. Do not keep them in public repositories, ordinary logs, or caches without access isolation.
Software and licenses
Confirm that installed software, dependencies, fonts, assets, and development tools have appropriate licenses, and comply with their applicable usage limits.
Access permissions
Assign administrator and automation-runner permissions according to least privilege, and regularly review source addresses, authorized members, and unusual logins.
Workload compliance
Ensure that builds, tests, network requests, data processing, and automated workflows comply with applicable law and commitments made to third parties.
Customers should also plan disk space, dependency caches, build artifacts, and log retention appropriately. Node restarts, toolchain upgrades, or workload errors may affect unsaved state, so critical workflows should be reproducible rather than relying on a single copy stored on the node.
Service operations, suspension, and termination
OnceMac nodes are designed to operate continuously 365 days a year without scheduled downtime periods. In the event of an unexpected hardware failure, network incident, security risk, or infrastructure issue requiring immediate action, OnceMac may take necessary measures such as diagnosis, isolation, migration, restart, or access restriction, and will provide updates through console tickets or account contact information based on the impact of the incident.
Possible reasons for suspension
- The order has expired and renewal payment has not been confirmed;
- Payment has been reversed or declined, or the order status shows an anomaly requiring verification;
- The account, keys, or node show clear signs of unauthorized access risk;
- The customer violates acceptable-use rules, or the workload continues to affect platform or third-party stability;
- Legal requirements, valid regulatory requirements, or urgent security response require service restrictions.
Where the risk permits, OnceMac will explain the reason for suspension and the corrective steps available to the customer. If the risk is escalating, there are signs of unauthorized access, or continued operation could cause harm, OnceMac may restrict access first and complete notification and investigation afterward.
Restoration and termination
After the customer completes identity verification, risk remediation, order confirmation, or other necessary steps, OnceMac will assess whether to restore service. OnceMac may terminate the relevant order or account in cases of serious or repeated violations, refusal to cooperate with risk response, or legal restrictions on continuing to provide the service.
Before the rental term ends, the customer voluntarily terminates, or the service is terminated, the customer must export code, build artifacts, logs, and other required data. After termination, the node enters the recovery and redeployment process. Customers must not treat local node storage as long-term archiving or as their only backup medium.
Availability, liability, and disputes
Availability is assessed using the applicable order, verifiable service records, and the agreed measurement method. Impacts caused by the customer's actions or network, third-party software, misconfiguration, unauthorized activity, or force majeure are excluded from service interruptions within OnceMac's control.
Service credit
If the availability condition specified in the applicable order is not met, the customer must submit a console ticket within a reasonable period with the order number, affected node, time range, connection tests, and redacted logs. OnceMac will verify the matter against its service records. If confirmed, a service credit will be provided under the applicable rules. Credits apply to eligible future orders and do not directly replace remediation of the incident's cause.
Responsibilities and liability
OnceMac is responsible for providing, within reasonable limits, the confirmed dedicated physical machine configuration, node connectivity, order management, and support process. Customers are responsible for their code, data, accounts, keys, software licenses, workloads, and business continuity arrangements. Each party must take reasonable steps to reduce known losses and must not allow avoidable impacts to worsen.
To the extent permitted by applicable law, OnceMac's aggregate liability for an order is limited to the service fees actually paid by the customer for the order giving rise to the claim, except for intentional misconduct, gross negligence, or liability that applicable law expressly prohibits from being limited. Indirect losses, anticipated profits, business opportunities, or losses arising solely from unbacked-up data will be handled to the extent permitted by applicable law.
Updates to these terms
OnceMac may update these terms in response to changes in service processes, risk controls, payment methods, or legal requirements. Updates that materially affect customer rights or obligations will be reasonably notified through the website, console, or account contact information. Updated terms apply to orders submitted or renewed after they take effect, unless applicable law requires otherwise.
Governing law and dispute resolution
These terms are governed by the laws of the jurisdiction where the platform's operating entity is located. The parties should first resolve disputes through support records, order materials, and good-faith negotiation. If negotiation fails, either party may bring proceedings before a court with jurisdiction in that jurisdiction. Any other mandatory process required by applicable law will be followed.
Notices and contact
Notices concerning orders, suspension, termination, or disputes may be sent through console tickets, account contact information, or the support email. Customers must keep their contact details accurate and regularly check their order and ticket status. Questions about these terms may be sent to support@oncemac.com; matters concerning existing orders should be submitted first through theconsole ticket system, so they can be linked to the relevant order record.