1. Service scope
ArmShell provides dedicated Apple Silicon physical nodes for rent. You rent a physical cloud Mac node, not a virtual machine. For the duration of your rental, its CPU, GPU and unified memory are not shared with other customers. Dedicated resources do not give you ownership of the hardware or administrative access to its network or infrastructure.
Three configurations are available: M4 / 16GB / 256GB, M4 / 24GB / 512GB, and M4 Pro / 64GB / 2TB, named Shell M4, Shell M4 Plus and Shell M4 Pro, respectively. The order record determines the configuration, node, billing period and any confirmed add-ons supplied. Availability is based on the live status shown in the account portal.
You can use the macOS graphical interface and command line for development, builds and compute workloads. You are responsible for obtaining and maintaining valid project code, third-party software licences, signing certificates and any other required permissions. Third-party service charges not listed in your order are not included in the node rental fee.
2. Account and security responsibilities
When registering and using an account, provide a valid email address that can receive service notifications, and keep your required details up to date. If you place an order on behalf of a team, you must be authorised to do so and are responsible for coordinating team access, payment approval and data handover.
Keep your account password, node credentials, SSH private keys, access tokens and build credentials secure. Do not share complete passwords or private keys in public repositories, support tickets or email. Before sending terminal output to our support team, remove tokens, certificate contents and other sensitive information.
If you notice a suspicious login, exposed credentials or unauthorised activity, replace the affected credentials immediately and report the issue through an account support ticket or by email. We’ll help investigate using account verification and activity records. Requests involving account ownership or changes to sensitive settings require the necessary identity checks first.
3. Billing periods, renewals and expiry
Nodes are available with four billing periods: daily, weekly, monthly and quarterly. All charges are billed and settled in US dollars (USD). Your selected period starts when the node is provisioned. The account portal’s order and billing records show the exact start and end times, amount due and order status. Use the expiry time shown on your bill rather than estimating it from calendar days, months or your local time zone.
Before placing an order, check the model, node, billing period, storage expansion and any add-ons, such as Thunderbolt 5 daisy-chaining. Make sure you can distinguish the base rental fee from add-on charges, and pay only after confirming the final breakdown. Confirm in advance whether a resource change, billing-period adjustment or upgrade is possible, along with any price difference and when the change will take effect.
If you want to keep using the node, review and pay the renewal bill before it expires. Creating a renewal request, sending proof of payment or submitting a support ticket does not complete the renewal. The renewal is complete only when the bill is confirmed and your service period is updated. Do not assume that payment will be charged automatically at expiry, or that stopping use cancels an active order.
After expiry, access to the node may stop, and the node may enter the recycling and data-erasure process. We do not guarantee a fixed data-retention period; any specific retention arrangement stated in your order will apply. Back up your data and retrieve your work before expiry. Do not rely on an expired node as a recoverable copy of your data.
4. Payment methods and settlement
We accept only USDT-TRC20 and Visa / Mastercard / Amex card payments processed by Stripe. The payment gateways actually available are determined by the response from our backend. Orders and bills are priced and settled in US dollars (USD), regardless of the payment method.
When paying with USDT-TRC20, carefully check the network, recipient address and amount shown on the payment page. Do not send funds to an address from an earlier transaction. If we need to verify a transaction, provide the order number and transaction hash. Sending a transaction does not mean your bill has been confirmed; the status shown in the account portal is final.
Card payments are processed by Stripe, and ArmShell does not store full card numbers. Your card issuer may require identity verification, conduct risk checks or charge its own fees. If the charge status does not match the bill status, save your order number and payment reference, then request a review through a support ticket. Do not pay again until the discrepancy has been checked.
5. Refunds and disputes
If you’ve been charged twice, the amount is incorrect, a service hasn’t been delivered or you have another service-related dispute, request a review through an account support ticket or email support@armshell.com. Include the order number, the item in dispute, payment reference and the resolution you’re seeking. Do not include full card numbers, passwords or private keys in your supporting material.
We’ll review your request against the order configuration, payment records, provisioning time, actual delivery and applicable law. Stopping use, deleting a project or ending a task early does not automatically entitle you to a refund. Whether a refund is due, its scope and any follow-up service arrangements will be confirmed after the facts have been reviewed. Estimates or verbal assumptions do not replace a confirmed outcome.
If a refund is approved, we’ll arrange it using the original payment method and an available processing route, and let you know what information is required. Processing times can vary between banks, payment processors and on-chain transactions, so we do not guarantee a standard time for funds to arrive. If you have questions about the outcome, add information to the same support ticket so the review remains in one continuous record.
6. Acceptable use
You may use the node only within the scope of the permissions you hold. You must not use the service to send spam, carry out network attacks, distribute malware, steal credentials, perform unauthorised scans or access, mine cryptocurrency, or store, process or distribute unlawful content. Do not use a node to disrupt other users, platform infrastructure or third-party systems.
Repositories, build dependencies, models, datasets and test targets must come from lawful sources and be covered by the necessary permissions. Automated and security testing must be limited to systems you are authorised to test. When sharing a node with your team, use clear access controls and session handover procedures. Team sharing does not exempt you from these requirements.
If we detect prohibited activity or have specific evidence of a security risk, we may restrict the relevant access, suspend the service or terminate the order, depending on the level of risk. Where permitted by law and safe to do so, we’ll explain the reason. To restore service, you must cooperate with verification, stop the relevant activity and complete any necessary remediation. Fee disputes are handled under Section 5.
7. Service availability and incident handling
All nodes are provided for normal operation 365 days a year. If a network, hardware or other infrastructure issue occurs, we’ll investigate and work to restore service based on the circumstances. A node operating normally and being reachable from your location are separate matters: public internet routing, your network provider’s links and your local network can all affect connectivity.
When reporting an issue, include your order number, node, the time and time zone when the problem occurred, your connection method and redacted error details. If you can still access the node, save any necessary logs and work files first. Do not repeatedly change firewall settings, delete system directories or reset critical services unless you understand the consequences.
Any service-level commitment for a specific order must be set out in a document confirmed by both parties. These terms do not create unagreed compensation rates or restoration deadlines. Issues involving force majeure, your own actions or third-party network links will be reviewed according to their causes and actual impact, rather than treated as though all incidents have the same cause or outcome.
8. Data responsibilities and backups
You are responsible for managing source code, build outputs, project settings, certificates, models and other work data on the node, and for keeping backups independently of that node. We recommend making backups before important changes, after builds and before expiry, and verifying that you can restore them. Copying files to another directory on the same node is not an independent backup.
Your dedicated physical node does not expose your working directory to other customers. We will not access your user files or workloads without authorisation. If access is needed to respond to a support request you initiated, we’ll first confirm the scope of that authorisation. Account, order, billing and support-ticket information is handled under the Privacy Policy and should not be confused with project files on the node.
Expiry and recycling, redeployment, system reinstallation or a cleanup operation you have approved may make existing data inaccessible. The data-erasure process must be completed before a node is reassigned, but erasure is not a backup service and does not mean the original data can be recovered afterwards. Before carrying out any operation that could affect your data, check your exports and recovery plan.
9. Liability and limitations
ArmShell provides node rentals and related services as set out in the confirmed order, and is responsible for its obligations to deliver the service, handle accounts and review reported issues. You are responsible for the software you deploy, the permissions under which you use it, changes to node settings and your backup arrangements. If a loss occurs, responsibility will be assessed based on the evidence, cause and conduct of each party; a one-sided account is not a substitute for review.
We do not guarantee that a project will pass review, a model will produce the expected results, third-party software will be compatible or your business will achieve a particular outcome. These results depend on the project, toolchain, external requirements and specific workload. If you have particular compatibility requirements, raise them before ordering and rely on the service scope confirmed in writing.
Any limitation of liability applies only to the extent permitted by applicable law. Nothing in these terms excludes or limits liability that cannot legally be excluded or limited, or affects any rights you may have under applicable law. If a dispute arises, both parties should take reasonable steps to limit further loss, preserve relevant records and first use the review process in Section 5.
10. Changes, applicable law and contact
This version takes effect on its publication date. We’ll announce material changes to the service scope, billing or users’ rights and responsibilities on the website or through account-related notices. Existing orders will be handled in light of the terms confirmed when they were placed and applicable law. Updated terms should not be taken to change existing orders retroactively without notice.
These terms are governed by the laws of the jurisdiction in which the platform operator is based. The parties should first discuss any dispute and review the relevant facts. If they cannot reach an agreement, the dispute will be submitted to a court with jurisdiction in that jurisdiction, unless mandatory law provides otherwise.
For account, order, billing, compliance or security issues, contact us at support@armshell.com or sign in to the account portal to submit a support ticket. Where possible, include the order number, a description of the issue and relevant redacted records in the same request so we can review the full context.