Cloud Mac Rental Terms of Service

Scope and Acceptance

These terms apply to individuals and organizations that access the Oakmini website, create or use a portal account, place a Cloud Mac order, or manage a dedicated Mac mini physical machine through the portal. Website usage rules and applicable privacy information apply when you browse public pages; account security and authorization rules also apply once you create a portal account; after you place an order, the model, node, term, and add-ons shown on the order confirmation page become part of the service relationship.

Anyone acting on behalf of an organization must ensure they have the necessary authority to select configurations, place orders, manage authorized users, and handle related support requests for that organization. Configuration confirmations, term selections, ticket submissions, and instance-management actions completed in the portal are considered actions taken by the account holder.

If the order confirmation page, product page, and these terms describe a specific configuration at different levels of detail, the model, chip, memory, storage, node, billing term, and add-ons are governed by the final order record confirmed by the user. Account security, acceptable use, data responsibilities, and dispute handling remain governed by these terms.

Service Description

Oakmini provides remotely accessible dedicated Mac mini physical machines and related management access. Each valid order corresponds to the physical node recorded in the order and is not shared with other users as the same virtual machine instance. Based on the delivery details, users may access the macOS command line and graphical interface through SSH or VNC, and connect the node to their development environment, build scripts, or self-hosted runner.

Currently available nodes include Singapore, Tokyo, Seoul, Hong Kong, and the U.S. West Coast. Available models are Oak Core and Oak Forge; the order page determines the regions and configurations available at the time of purchase. All nodes operate continuously 365 days a year. Actual connection quality may still be affected by the user’s local network, interregional routing, endpoint configuration, and workload.

Oakmini provides the physical node rental and management access associated with each order. Users are responsible for assessing their requirements for the macOS version, Apple Silicon architecture, dependencies, software licenses, network access, and storage capacity, and for determining before ordering whether the selected option suits their workflow.

Accounts and Authorization

Users must set unique, sufficiently strong credentials for their portal account and securely protect SSH keys, VNC credentials, automation tokens, and other connection information. Do not share access credentials publicly or place long-lived keys directly in public repositories, build logs, images, script templates, or configuration files readable by unauthorized people.

Organization users should manage members according to the principle of least privilege. When an authorized person changes, a project ends, or an external collaborator leaves, promptly revoke the relevant node access, rotate related keys, and check CI runners, Git credentials, environment variables, and scheduled tasks for retained access methods.

The account holder is responsible for connections, commands, tasks, network requests, file changes, and actions by authorized users under the account. If credentials are exposed or you detect an unusual connection, unknown process, or unauthorized configuration change, first stop the relevant automation, rotate affected credentials, and save sanitized logs, then submit a ticket through the portal.

• Use a unique password and avoid sharing one login credential among multiple people
• Assign the minimum necessary permissions separately for development, builds, and temporary collaboration
• Rotate credentials immediately when a member leaves, a project is transferred, or a key is exposed
• Remove passwords, private keys, signing materials, and payment credentials before submitting support logs

Orders and Billing

Cloud Mac orders support daily, weekly, monthly, and quarterly terms. Confirm the term unit before placing an order: each term has its own price and daily, weekly, or quarterly pricing should not be treated as a simple conversion of the monthly price. The term, model, node, and add-ons shown on the order page together determine the billing basis.

Orders support only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe), with all charges settled in USD. The payment gateway available at checkout is determined by the result returned in the portal. Before paying, verify the order ID, amount, network type, and recipient details. Do not pay to an old address or to information not shown on the order page.

Renewals, term selection, order status, and host management are all handled through the portal. If the payment status does not match the order status, retain the order ID, payment time, and information that can be used to verify the transaction, then request a review through a portal ticket or support@oakmini.com but do not send complete payment credentials.

Configuration and Add-ons

Before placing an order, confirm the chip, memory, base storage, node region, billing term, and add-ons item by item. Oak Core includes an M4, 16GB RAM, and 256GB SSD; Oak Forge includes an M4 Pro, 64GB RAM, and 2TB SSD. Configurations support different levels of concurrency, data volume, and toolchain workload, and later migration cannot replace capacity planning before purchase.

Thunderbolt 5 pairing is priced per machine and becomes an order item only when the user explicitly selects and confirms the quantity. Evaluate storage expansion against peak usage from repositories, dependency caches, build artifacts, model files, and temporary working directories—not only the initial project size.

Acceptable Use

Users may use Cloud Mac for lawful software development, automated builds, testing, remote experiments, audio and video processing, and other workflows consistent with the ordered configuration. Users must not infringe intellectual property, privacy, trade secrets, or other lawful rights, or bypass authorization limits imposed by a project, software, or data.

Do not upload, run, distribute, or help spread malware. Do not scan, probe, access, or control systems, accounts, ports, devices, or data without authorization. Do not disrupt networks, nodes, or other services through excessive requests, abnormal traffic, resource exhaustion, or other means. Do not use a node for fraud, unlawful transactions, evading security controls, or other unlawful activity.

If system activity indicates a clear security risk, infringement of third-party rights, or a violation of these terms, Oakmini may ask the user to explain the purpose, stop the relevant tasks, remove prohibited content, or correct the configuration. If the risk is urgent and may continue to escalate, Oakmini may first restrict the relevant connections or tasks and then investigate using available records. Users must cooperate by providing the order ID, time of occurrence, process information, reproduction steps, and sanitized logs.

Software and Third-Party Accounts

Users are responsible for the authorization status of their developer accounts, code repositories, packages, models, media assets, dependencies, and third-party services. Copying a tool or content to a Cloud Mac does not change its existing license scope or automatically grant team seats, commercial-use, redistribution, or remote-execution rights.

Users must manage versions of Xcode, Homebrew, Git, Fastlane, language runtimes, CI runners, and other tools according to project requirements, and review applicable licenses and third-party service terms. Workflows requiring signing materials must keep certificates, keys, and configuration files in access-controlled locations and must not place them in public repositories or publicly readable build artifacts.

Software upgrades, dependency changes, and script modifications may change build results. Users should retain version lists, lockfiles, installation commands, and descriptions of critical environment variables, and validate the toolchain with a test project before important tasks. Users must handle third-party service outages, API changes, license restrictions, and account permission changes under the applicable service rules.

Oakmini’s Scope

The physical node associated with the order, remote connection information, and portal management access.

User’s Scope

Project permissions, developer accounts, code authorization, software licenses, signing materials, and compliance with third-party services.

Data and Backups

Users must maintain recoverable copies of code, build artifacts, project configuration, dependency lists, model files, credentials, and other business data. The Cloud Mac working directory should not be treated as the only copy. For ongoing development or automated pipelines, we recommend separately retaining the repository source, environment rebuild checklist, required artifacts, and credential recovery path.

The backup plan should match the rate of data change and recovery objectives. Frequently changing repositories and configurations can be managed through version control and scheduled exports; large caches can usually be rebuilt, but their generation methods should be documented. Irreplaceable build artifacts, experiment results, and original media files should be stored separately and regularly tested for readability and recovery.

Before migrating configuration, ending a term, changing project ownership, or stopping use of a node, users must complete necessary exports, confirm that repositories have been pushed, build artifacts have been copied, the environment inventory has been saved, runners have been unregistered from pipelines, and unneeded keys and access tokens have been removed. Seeing that files exist does not mean a recoverable backup is complete.

1. 01
   Identify Data

   Distinguish code, configuration, caches, artifacts, models, and credentials.

2. 02
   Create Copies

   Store irreplaceable content in a separate, access-controlled location.

3. 03
   Verify Recovery

   Spot-check that repositories, configurations, and artifacts can be read in a new environment.

4. 04
   Securely Wrap Up

   Revoke runners, rotate keys, and delete leftover sensitive information.

Changes, Termination, and Liability

Oakmini may update service descriptions or these terms based on product configuration, infrastructure, security requirements, payment processing, and legal obligations. Material changes affecting a user’s current order will be communicated through the website, portal, or contact details associated with the account in an identifiable update. Updated terms apply to access, account activity, or orders occurring after the stated effective time.

If a user violates acceptable-use rules, endangers node or network security, infringes third-party rights, provides invalid authorization, or fails to pay the amount due under an order, Oakmini may require correction, restrict relevant tasks, suspend access, or terminate the applicable service. Measures will account for the urgency of the risk, scope of impact, available logs, and the user’s cooperation. Users must still complete necessary data exports within a practicable period and stop using affected access methods.

For impacts caused by events beyond reasonable control, public network disruptions, upstream infrastructure failures, government action, natural events, or the user’s own actions, software configuration, credential exposure, unauthorized personnel, or changes to third-party services, the parties will allocate responsibility based on the cause, controllable scope, actual loss, and applicable mandatory legal rules. No limitation of liability excludes liability that applicable law does not permit to be limited.

These terms and the related service relationship are governed by the laws of the jurisdiction where the platform operator is established. For disputes arising from these terms, a portal account, or a Cloud Mac order, the parties should first communicate in writing to verify order records, timelines, and relevant logs. If negotiation does not resolve the matter, it may be submitted to a court with jurisdiction in that jurisdiction.

If any part of these terms is held unenforceable, the remaining parts remain effective and should be interpreted, to the extent permitted by law, in the manner closest to the original purpose. Failure to immediately enforce a right does not waive the ability to exercise it later based on the facts and applicable rules.