Cloud Mac Rental Terms of Service

Acceptance and service definition

By creating an order, completing payment, beginning to use a device or authorizing team members to operate a device, you confirm that you have read and agree to these terms, the order confirmation and all related policies in effect at that time. Anyone ordering on behalf of an organization must have authority to accept these terms and arrange payment for that organization.

The service consists of a dedicated physical cloud Mac in the region selected in the order, together with management features for viewing orders, device information and billing status and for submitting support tickets. Each valid order corresponds to physical-node resources with the agreed configuration. The service is not a shared computing environment or a virtual machine instance.

The order confirmation records the model, region, rental term, add-ons and total amount due. The order confirmation and these terms together form the service agreement; where the order contains specific terms for a particular configuration, those terms prevail. Use-case examples on marketing pages explain applicable workflows and do not replace the specific configuration in the order.

Accounts and authorization

You must provide account and order information that is accurate, current and sufficient for ongoing contact, and update it promptly when it changes. Keep login credentials, device connection details, keys and other access materials secure. Do not publish them in public repositories, shared documents, public tickets or communications spaces without access controls.

Organization accounts may be used by authorized team members. The account holder is responsible for setting member access scopes, promptly removing people who no longer work on the project, and all orders, configuration changes, system changes and data operations performed under the account. Teams should assign repository, CI, signing-material and device-management permissions according to least-privilege principles.

If credentials may have been exposed or you detect an unusual login or unauthorized device activity, immediately stop sharing the affected information, rotate the credentials and submit a console ticket. To protect the service and other nodes, G-Mini may restrict the relevant access while the risk is verified, but will never ask you to submit passwords, private keys or unsanitized sensitive logs in a public area.

Available configurations and regions

The current catalog includes only the following two Mac Mini M4 configurations. Devices are delivered according to the configuration selected in the order, with memory and base storage governed by the order confirmation. Chip, memory or base-drive combinations outside this catalog are not standard configurations covered by these terms.

Both models are available in five regions: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong and the western United States. All regions operate normally 365 days a year. Choose a region based on your team’s location, repository and artifact transfer paths, remote desktop experience and internal compliance requirements.

Changing the region after an order is created is not a simple address change and may involve delivery of a new device, data migration and updated connection details. To request a region change, first submit a console ticket with the order number, current region, target region and preferred switchover time. Whether a direct change is possible depends on the actual device and order status.

Billing and payment

Base models are billed for the daily, weekly, monthly or quarterly term selected in the order. Each term has its own catalog price; other-term prices are not calculated by multiplying the daily rate, and the order price is not replaced with a rounded figure.

Payment is supported only by USDT-TRC20 or by Visa, Mastercard or Amex through Stripe. All quotes, orders and invoices are settled in USD. The payment gateway actually available is determined by the backend response at checkout.

Payment status, transaction identifiers and order activation status are governed by the console record. Before confirming payment, verify the currency, amount, network, recipient details and order contents. If a transaction is affected by selecting the wrong network, entering incorrect information or rejection by the card issuer, retain the transaction records and submit them for review through a console ticket.

The rental term is calculated from the service start status confirmed in the order. Renewals, term changes and configuration changes are governed by the new order confirmation and must not be inferred from the previous term’s amount. Any taxes or legally required fees, where applicable, will be shown separately before payment is confirmed.

Add-ons

Add-ons take effect with the corresponding primary order and are not sold as standalone services separate from the cloud Mac order. Storage options expand the storage capacity of the ordered device. Thunderbolt 5 linking is billed per participating device, and the quantity must match the order confirmation.

Add-ons use the same billing term as the primary order. The total consists of the base model, selected term, storage add-ons and number of Thunderbolt 5 linked devices. Use the itemized details and final total shown at checkout as the definitive amounts.

Storage or linking configurations that have already entered delivery may require device operations, data migration or changes to connection relationships. Before requesting a change, complete necessary backups and specify the data you want to retain. Whether the change can be performed on the existing device and how it takes effect will be confirmed through a console ticket.

Fair use and prohibited activities

You may use the cloud Mac for lawful software development, automated builds, testing, remote development, MLX experiments and other work consistent with the capacity of the ordered resources. Ensure that your code, dependencies, data, automation tasks and team activities comply with applicable rules, and avoid creating abnormal load on the node network or other services.

You must not use the service for unlawful activity, unauthorized access to third-party systems, network scanning or attacks, malware distribution, credential theft, bypassing access controls, concealing the source of abuse or operations that could compromise other nodes or network stability. You must not attempt to bypass device boundaries, alter controls used by the provider for delivery and security management, or interfere with incident-diagnosis records.

When running build queues, runners or long-running experiments, set reasonable concurrency, caching and log-retention policies. If you detect an abnormal process, sustained network spike or unknown task, first pause the relevant workload and save sanitized logs instead of repeatedly restarting or deleting evidence.

If the system detects a clear security risk, abusive behavior or an ongoing impact on network stability, G-Mini may take necessary measures such as restricting connections, pausing related tasks or temporarily isolating the device, and will explain the reason and verification requirements through the contact details on the account or console information.

Systems, data and backup responsibility

You are responsible for your development toolchain, software licenses, repository access authorization, CI credentials, code-signing materials, application data, build artifacts and business configuration. Record key tools and versions, maintain a reproducible installation manifest, and prepare backups for data that cannot be regenerated from a repository or artifact system.

G-Mini is responsible for delivering the dedicated physical machine with the agreed configuration and region and for providing device-management information and incident support within the order scope. Except for additional storage expressly included in the order, capacity will not expand automatically because of growing user directories, accumulated caches or uncleared build artifacts.

Do not treat the device’s local disk as your only backup. Before a system upgrade, major toolchain change, storage adjustment, bulk deletion or project migration, verify that backups can be read and retain repository commits, dependency manifests, signing materials and artifact indexes. Your team determines its own backup frequency, retention scope and recovery-acceptance criteria.

To help investigate an issue, you may submit sanitized command output, tool versions, reproduction steps and error logs. Remove passwords, private keys, access tokens, complete connection credentials and unnecessary personal information from logs. Support personnel will process this information only to the extent necessary for diagnosis.

Operation, incidents and support

All regions operate normally 365 days a year. If you experience a connection issue, hardware failure or inconsistent delivery information, submit a console ticket with the order number, region, macOS version, time of occurrence, scope of impact, reproduction steps and sanitized logs.

Diagnosis generally begins by distinguishing local network, remote connection configuration, system processes, development toolchain and physical hardware issues. Avoid repeatedly changing network settings, reinstalling tools or clearing logs during evidence collection; where business conditions allow, pause related automation and preserve the current state first.

Once an issue is confirmed to involve physical hardware, G-Mini will arrange inspection, component service or device replacement according to the fault type and will share the steps in the console ticket. If a device is replaced, connection details may change, so verify host information and team authorization again.

Support covers order-delivery checks, region and connection verification, physical hardware diagnosis and billing-status checks. Project-code debugging, third-party dependency compatibility, repository permission design, signing-flow configuration and user-built automation scripts remain your responsibility. The support team may identify troubleshooting directions from logs but does not take over day-to-day engineering work on your projects.

Suspension, termination and data handling

When the rental term ends without a further order, device access will change according to the order status. Before expiry, complete code commits, export build artifacts, back up necessary data, revoke credentials and remove team access. After termination, do not continue using the former connection details to access the device.

To terminate the service, first check the order status in the console and submit the relevant request. If termination involves multiple linked devices, additional storage or running build tasks, specify the order scope to be stopped so that other devices still in use are not affected.

In cases of serious violation, a clear security risk, unauthorized access or activity that persistently affects node or network stability, G-Mini may suspend or terminate the relevant service. Where feasible, the console record will state the reason, additional verification information required and available next steps.

Data handling is based on the order status, user requests and necessary security verification. Once access ends, do not assume that device data can still be recovered. G-Mini will handle related data as required for service delivery, security and necessary records. Order and support records will be retained as needed for billing review, dispute handling and other necessary obligations.

Updates and dispute handling

G-Mini will retain the terms version, effective date and a summary of material changes. Material changes involving billing, available configurations, user responsibilities or data handling will be presented clearly and will not replace existing records without notice.

The model, region, term, add-ons and amount applicable to a specific order are governed by the order confirmation and the valid terms version applicable to that order. Updated terms generally apply to service relationships created or reconfirmed after their effective date, except where otherwise required by law or expressly agreed by both parties.

If a dispute arises, the parties should first communicate in good faith through a console ticket or support@globemini.com and provide the order number, subject of the dispute, relevant records and desired resolution. Each party should retain necessary evidence relating to the order, payment, device status and support communications.

These terms are governed by the laws of the jurisdiction where the platform operator is based. If consultation does not resolve a dispute, it may be submitted to a court with jurisdiction in that jurisdiction. Rights and obligations that cannot be excluded by contract under applicable law remain in effect.