1. Acceptance & Account Responsibilities
By accessing or using the ArmCLI website, creating an account, placing an order, paying fees, or using a delivered Cloud Mac, you confirm that you have read, understood, and agreed to these terms. Users acting for an organization also confirm that they have the necessary authority to accept these terms on its behalf.
You must provide accurate, complete, and verifiable account and order information, and promptly update any changed contact details. Accounts are limited to authorized users and may not be sold, transferred, rented, or otherwise placed under the control of an unauthorized third party.
You are responsible for securely storing login credentials, SSH keys, temporary passwords, and recovery information, and should apply least-privilege access based on the task scope. If credentials are exposed or you detect an unknown session or unusual activity, immediately rotate the relevant credentials, terminate suspicious sessions, and notify the service team through a console ticket or at support@armcli.com.
2. Service Definition
ArmCLI provides Cloud Macs for daily, weekly, monthly, or quarterly rental. Each valid order corresponds to one dedicated Apple Silicon physical machine. Operating system instances are not shared between tenants, and this service is not a virtual machine resource pool.
The available range includes only the three machine tiers listed on the plans page and five data centers: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the US East. The exact chip, memory, storage, rental period, and add-ons are determined by the catalog shown on the order confirmation page.
+1TB SSD, +2TB SSD, and Thunderbolt 5 interconnect are optional upgrades and are not included in the base configuration by default. Choose a configuration based on build concurrency, dependency caches, project size, and data growth. ArmCLI provides configuration details and general guidance but does not guarantee that any configuration will achieve a specific business outcome.
3. Orders & Delivery
Before placing an order, verify the machine model, data center, rental period, storage upgrade, interconnect option, and amount due. Once an order enters the payment process, the final configuration is the one recorded on the order confirmation page. Configuration changes may require reconfirming the amount and delivery arrangements.
Machine and data center combinations in the catalog are generally available to order, but actual availability at submission is determined by the real-time status returned in the console. After payment is confirmed, the system prepares the node, applies the base configuration, and issues credentials. The standard process takes about 4 minutes; complex orders or required security checks may take longer.
After delivery, verify the node ID, configuration, connection details, rental start and end times, and basic connectivity, then complete the first-login check promptly. If the delivery record does not match the order, retain the order number and redacted verification results and submit a console ticket.
4. Fees & Payment
ArmCLI accepts USDT-TRC20 and card payments by Visa, Mastercard, and Amex processed through Stripe. All orders are billed in US dollars (USD). The gateways actually available are shown in real time on the checkout page.
The applicable amount is the one shown on the order confirmation page before you submit payment. The order total is determined by the selected machine, rental period, data center, and add-ons. Before paying, check the network, currency, amount, recipient details, and order status to avoid duplicate submissions.
Blockchain transfers generally cannot be reversed once broadcast. You are responsible for the consequences of choosing the wrong network, entering an incorrect address, underpaying, paying twice, or incurring fees charged by the sender. Card payment verification, disputes, and risk checks follow the applicable payment processor's procedures.
5. Renewals, Expiration & Resource Recovery
You are responsible for monitoring the rental end time shown in the console and should allow sufficient time for payment confirmation, internal approval, and data export. Submitting a renewal request does not mean the renewal is complete; success is determined by the console order status and updated expiration time.
When the rental period ends without a valid completed renewal, node access will be stopped according to the process and the related physical resources will enter recovery. An old session, cached credentials, or local connection record that still works must not be treated as proof that the rental has been extended.
Before the rental ends, export and verify your code, build artifacts, certificates, keys, logs, and business data. Once resources enter recovery, ArmCLI does not guarantee that content you failed to export can be restored, and temporary access extensions do not replace your backup responsibilities.
6. Acceptable Use
You may not use ArmCLI services for unauthorized system access, credential probing, malware distribution, denial-of-service attacks, resource abuse, bypassing access controls, intellectual property infringement, or any other activity that harms the platform, nodes, networks, or third parties.
You may not use automated tasks to continuously generate abnormal network traffic, conceal an attack source, scan unauthorized targets, or run workloads that affect physical node stability or infrastructure security. Legitimate security testing must be limited to targets you clearly own or are authorized to test in writing.
ArmCLI may apply rate limits, isolate sessions, suspend access, or request additional information based on verifiable risk signals. You must cooperate by providing the task purpose, impact scope, time of occurrence, and redacted logs. Refusal to cooperate or continued violations may result in termination of service.
7. Data & Backup Responsibilities
You are responsible for the legality, security configuration, and backups of your code, certificates, signing materials, SSH keys, access tokens, build caches, databases, logs, and business data. Important data should have at least one verifiable copy stored independently of the rented node.
Limit sensitive information in build logs, command history, and temporary directories, and disable credential saving on shared work devices. Before sending troubleshooting materials to the service team, remove keys, tokens, full personal information, and other sensitive fields that are not needed to reproduce the issue.
Before the rental ends, export your data, verify backups, revoke keys, sign out of sessions, and remove sensitive files you no longer need. ArmCLI is responsible for physical node delivery and basic connectivity within the agreed scope; it does not replace your own version control, key management, or business continuity measures.
8. Availability & Service Interruptions
ArmCLI nodes operate normally 365 days a year. Service may still be interrupted or experience performance changes due to events beyond reasonable control, security incidents, hardware failures, user actions, the user's local network, or necessary emergency risk response.
The 99.9% availability calculation is based on server connection records, node status records, and confirmed incidents. Effects caused by the user's local network, misconfiguration, unauthorized software changes, third-party dependency failures, or events beyond reasonable control are outside the platform's controllable scope.
Requests to review availability or provide compensation must be submitted through a console ticket with the order number, affected time period, node ID, and redacted evidence. Eligibility for compensation and the handling method are determined by the commitment applicable to the order, these terms, and the review outcome.
9. Liability Limits, Suspension & Termination
If an account presents a clear security risk, payment irregularity, unlawful use, serious breach of these terms, or conduct that may harm the platform or third parties, ArmCLI may take proportionate measures, including limiting features, isolating the node, suspending access, or terminating the service.
To the extent permitted by law, ArmCLI is not liable beyond the scope agreed in the applicable order for indirect losses, business interruption, lost profits, or data loss arising from user configuration, the user's network, third-party tools, external dependencies, unauthorized access, or failure to maintain backups.
Suspension or termination does not release you from payment obligations incurred before the measure took effect, nor does it affect the continuing validity of provisions concerning account security, fees, intellectual property, data responsibilities, liability limits, or dispute resolution.
10. Changes, Governing Rules & Contact
ArmCLI may update these terms due to changes in service processes, risk controls, legal requirements, or product scope. The updated version, effective date, and key changes will be provided on the website or in the console. Continuing to use the service after the effective date means you accept the updated terms.
These terms are governed by the laws of the jurisdiction where the platform operator is based. For disputes arising from these terms or the service, the parties should first seek a resolution through written communication. If no resolution is reached, the dispute will be submitted to a court with jurisdiction in that jurisdiction.
For questions about the terms, orders, billing, or formal notices, email support@armcli.com; users with an existing order should sign in to the console first to submit a ticket, including the order number, issue type, and necessary redacted materials.