Acceptance of the Terms and eligibility
By visiting this site, creating an account, placing an order, paying fees, receiving a machine, or actually using the service, you confirm that you have read, understood, and agreed to be bound by these Terms. If you act for a business, team, or other organization, you confirm that you are authorized to accept these Terms on its behalf and are responsible for communicating the applicable rules to approved machine users.
Account information must support delivery and verification
The name, work email, organization details, billing information, and order context provided during registration and ordering must be truthful, accurate, and kept current. Accounts may not impersonate others or use false information to evade security checks, usage limits, or billing obligations. Email is an important channel for verification codes, delivery notices, billing updates, and security information, so users must ensure they can receive messages reliably.
Account activity is treated as authorized activity
Orders, renewals, configuration selections, ticket submissions, and instance operations completed through a valid session, verification code, or console credentials are treated as instructions from the account holder or an authorized member. Users should apply appropriate internal approvals and least-privilege access for team members. If unusual access is detected, change the relevant credentials immediately and contact support through a console ticket or support@soarmac.com.
The purchaser must have the legal capacity required to enter into and perform these Terms. Organization accounts must also ensure that operators are authorized to purchase, use, and process data.
Cloud Mac is a dedicated physical server on an assigned node
SoarMac Cloud Mac means an Apple Silicon physical machine deployed on an assigned physical node and dedicated to a single order during the valid rental period. The service is not a virtual machine and does not substitute a shared compute instance for the hardware confirmed in the order. The actual model, chip, memory, system drive, additional storage, node, and rental period are determined by the order confirmation page and console records.
The order defines the deliverable
The catalog offers three tiers: SoarMac M4 Air, SoarMac M4 Plus, and SoarMac M4 Pro. Before confirming an order, users should check their workload requirements for memory, storage, continuous runtime, and node location. Tiers are not automatically interchangeable equivalent resources, and confirmed configurations will not be replaced without the user's confirmation.
What the service includes and excludes
- The physical machine listed in the order, the base system environment, delivery information required for remote access, and console management during the valid rental period.
- macOS graphical and command-line workflows are supported. Users may install and configure lawfully obtained software and dependencies as needed for their projects.
- Users are responsible for project source code, build scripts, certificates and provisioning profiles, third-party software licenses, task data, and team permissions.
- Third-party networks, code hosting, software licenses, external storage, and user-built pipelines are not service components directly controlled by SoarMac.
The catalog describes available model and node combinations. Actual availability, configuration results, and delivery progress when an order is placed are returned in real time by the console.
Orders, rental periods, renewals, and configuration changes
An order is submitted after the user selects the model, period, node, and add-ons and reviews the charges on the confirmation page. The rental period is based on the start and end times recorded in the delivery information, not on the user's first login, first task run, or first remote session.
| Period | Start time | End time | Renewal and switching |
|---|---|---|---|
| Daily | Starts at the activation time in the delivery record | Ends when the confirmed daily period expires | Renewal creates a new confirmation record; a period switch takes effect after confirmation |
| Weekly | Starts at the activation time in the delivery record | Ends when the confirmed weekly period expires | Renewal does not retroactively change pricing for a completed period |
| Monthly | Starts at the activation time in the delivery record | Ends when the confirmed monthly period expires | A period switch must be confirmed before the current period ends |
| Quarterly | Starts at the activation time in the delivery record | Ends when the confirmed quarterly period expires | Add-ons and concurrent quantities are reconfirmed with the renewal order |
Delivery confirmation
Delivery information typically includes the order number, model and configuration, node, rental-period start and end times, system account, access address, and initial session credentials. After receiving it, users should promptly verify the configuration and complete an initial connection check. If the model, memory, storage, node, or rental-period record differs from the order, open a ticket before running production workloads.
Renewals and configuration changes
A renewal does not rewrite the facts of the original order; it extends the usage period or creates a new service period. Changing the model or node, expanding storage, or adjusting the Thunderbolt 5 linked-device quantity may require task migration, process shutdown, or machine redelivery. Users should back up first and allow time for migration. The effective time is shown in the console confirmation.
Cancellations and incomplete payments
Unpaid or system-unconfirmed configuration selections do not constitute valid orders. Once an order is confirmed and enters delivery, cancellation, changes, and fee handling depend on the order status, resources already consumed, and the outcome confirmed in writing by the support team.
Pricing, add-ons, and payment methods
All machine fees, storage expansion fees, Thunderbolt 5 linking fees, and other applicable charges are priced and settled in USD. Before submission, the confirmation page shows the model, rental period, node, add-on quantities, total due, and, where applicable, taxes. Users should review each item before paying.
Two payment methods only
- USDT-TRC20:Complete the transfer using the payment details shown on the confirmation page. The network type and amount must match the order requirements.
- Card payments:Visa, Mastercard, and Amex are supported and processed by Stripe. The console's response determines the gateway available for the transaction.
SoarMac will not ask users through unofficial messages to send funds to an address other than the one on the confirmation page. If the payment status, amount, or order attribution is unclear, stop making duplicate payments and submit the order number, payment time, and redacted transaction details through a console ticket.
Billing confirmation and period changes
The price for an order period is locked in that order record when confirmed. Renewals, upgrades, downgrades, node changes, or add-on adjustments generate a new amount for confirmation and do not automatically change the price of a completed period retroactively. External fees charged by the payment network are governed by the relevant channel and are not included in catalog prices.
Before paying for any additional machine, rental extension, storage expansion, or quantity change, confirm that the console clearly shows the items and the USD total.
Acceptable use rules
Users may use Cloud Mac for lawful software development, continuous integration, automated testing, AI experiments, audio and video processing, and other authorized workloads. Using a dedicated physical server does not change the user's responsibility for task content, software licenses, access permissions, or network activity.
Prohibited activities
- Conducting unlawful activities or storing, processing, or distributing content that may not lawfully be handled.
- Unauthorized access to, scanning, testing, interference with, or control of third-party systems, accounts, devices, or networks.
- Developing, deploying, or distributing malicious code intended to cause damage, steal data, extort, or bypass security controls.
- Generating persistent abnormal network traffic, attack traffic, spam, or resource abuse clearly beyond normal engineering use.
- Infringing third-party intellectual property, privacy, trade secrets, or other lawful rights.
- Reselling, subleasing, or sharing access credentials, or allowing unauthorized parties to use ordered resources.
- Bypassing access controls, billing, security audits, or service limits, or interfering with other users or platform infrastructure.
Security response sequence
If the system detects conduct that may endanger the platform, physical node, or a third party, SoarMac may restrict networking, suspend related tasks, require verification of the activity's source, or suspend the instance in serious cases. Actions will be limited to what is reasonably necessary where possible, with a timeline retained in account records, email, or tickets.
After receiving a security notice, users must stop the relevant tasks, preserve necessary non-sensitive diagnostic information, revoke exposed credentials, and explain the purpose and remediation within the requested time. The service may be terminated for refusal to cooperate, repeated violations, or risks that cannot be isolated.
99.9% availability target and service-credit requests
SoarMac sets a 99.9% availability target for each applicable service period on physical nodes. Nodes operate continuously 365 days a year. Availability is assessed based on platform-controlled machine power, node networking, and remote-access capability, verified against service records, event timelines, and ticket evidence.
Determining downtime
If a machine cannot support reasonable connection and usage because of a node, power, platform-network, or remote-access failure within SoarMac's control, and the user provides the order number, node, occurrence time, and reproduction details through a ticket, the period may be reviewed for availability. Scattered client retries do not by themselves establish service unavailability; platform records and duration are considered together.
Situations excluded from platform downtime
- Interruptions caused by the user's intentional shutdown, restart, deletion of system components, or changes to network or security settings.
- Task failures caused by the user's software, build scripts, dependencies, resource contention, or misconfiguration.
- Connection problems caused by the user's network, a third-party network or service, or local remote-access tools.
- Force majeure, public-infrastructure failures, or other events beyond the platform's reasonable control.
- Necessary restrictions imposed to address user violations, security threats, or valid legal requirements.
Request and calculation standards
Within 7 calendar days after the affected rental period ends, users must submit a console ticket with the order number, node, occurrence and recovery times, impact description, and redacted logs. SoarMac will use platform records to confirm the affected duration, responsibility, and relevant order charges. Eligible compensation is issued as service credits and explained item by item in the ticket; expected task revenue and indirect losses are not used as the calculation basis.
Data, credentials, and the end of the rental period
Users are responsible for managing source code, assets, build artifacts, caches, logs, certificates, provisioning profiles, keys, and other business data uploaded to Cloud Mac, and should maintain independent backups appropriate to the importance of each project. A dedicated physical server does not replace version control, team storage, or disaster recovery.
Credential management
After the first connection, users must update the initial session credentials, give team members separate least-privilege accounts, and avoid putting keys in scripts, logs, or public repositories. When sending materials to support, remove passwords, private keys, access tokens, and unrelated personal data.
Migration responsibility before the rental period ends
Before the rental period ends, users should stop sensitive tasks still running, export necessary artifacts, confirm that data has synced to a location they control, revoke temporary credentials, and preserve change records needed for team handover. Access may no longer be available after the rental period ends, so migration should not be left until the last moment.
Handling after suspension or termination
When an order expires, the user terminates it, payment obligations remain overdue, or a serious violation occurs, SoarMac may stop access and begin resource recovery. If the risk and service status permit, we will explain required actions through account records or email; in an urgent security situation, access may be restricted before verification. Users remain responsible for retaining valid copies of their business data.
Liability, dispute handling, and Terms updates
The parties must perform their obligations in accordance with the order confirmation, these Terms, and established ticket records. SoarMac is responsible for the machine delivery, node operation, billing records, and support handling it directly controls. Users are responsible for workloads, software licenses, access authorization, data backups, credential management, and their choice of third-party services.
Liability
If a party breaches these Terms and directly causes demonstrable loss, liability will be determined by considering the breach, causation, foreseeability, and reasonable mitigation measures taken by both parties. Unless mandatory applicable rules require otherwise, aggregate liability related to an order is assessed by reference to the service fees already paid for that disputed order. Availability matters are handled first under the service-credit rules in these Terms.
Notices and dispute handling
If a user disputes billing, delivery, data processing, or service records, they must first submit a console ticket with the order number, factual timeline, desired resolution, and verifiable materials. If they do not have an account or cannot sign in, they may email support@soarmac.com. The parties should first verify the facts through written records and seek a resolution.
These Terms are governed by the laws of the jurisdiction where the platform operator is based. Disputes that cannot be resolved through discussion may be submitted to a competent court in that jurisdiction. Mandatory legal requirements prevail where applicable.
Terms updates
We may update these Terms in response to changes in service structure, billing processes, security requirements, or applicable rules. Material changes will be reasonably announced through the website, account notifications, or email, with the effective date of the new version. Prices locked in orders confirmed before an update and records of completed periods will not be rewritten retroactively; renewals and new orders after the update take effect under the then-current Terms.
This version takes effect on September 8, 2026. If you have questions about the version applicable to a specific order, submit the order number so the support team can verify it against the confirmation time.