1. Service overview
PushMac Cloud Mac provides dedicated physical Mac mini rentals. Each machine is assigned to one customer for the duration of the rental; it is not a virtual machine, and its computing resources are not shared with other customers. The service is suited to Xcode cloud builds, macOS CI, remote development, and legitimate testing. The macOS graphical interface and command line are both fully available.
The data center provides the power, network, and cooling required to host the machine. Customers are responsible for their projects, dependencies, build scripts, signing materials, and application configuration. A dedicated machine does not guarantee a fixed build time: duration depends on project size, concurrent tasks, dependency downloads, and the selected configuration.
The machine type, region, billing period, and add-ons in your order define the service provided. Available combinations can be ordered from the catalog; current availability is shown in the console. Check your order before payment. To change the configuration or region of a provisioned machine, first submit a support ticket in the console to confirm how the change will be handled. Changes are not automatic.
2. Billing & payment
Choose daily, weekly, monthly, or quarterly billing. All prices and invoices are in US dollars (USD). Machine charges and add-ons, such as storage expansion and Thunderbolt 5 daisy chaining, are listed separately. The amount due is shown in the order summary before payment. Each billing period is priced independently; do not calculate one period’s price by multiplying another period’s price.
We accept USDT-TRC20 and Visa, Mastercard, or Amex cards. Card payments are processed by Stripe; available payment gateways are shown by the checkout system. For USDT-TRC20, check the network, address, and amount displayed on the payment page. Using the wrong network or address, or sending mismatched payment details, may delay confirmation. Keep the transaction hash for verification.
Submitting a payment does not mean it has been confirmed. Bank processing and on-chain confirmation can take time. Check payment and order status in the console, and do not submit another payment if the status is unclear. Card transactions are handled by the payment processor; we do not store card numbers. USDT-TRC20 payments are verified against on-chain records.
Manage renewals, billing-period changes, and order adjustments in the console. Before making a change, confirm the new period, applicable amount, and effective date. For refund requests or billing corrections, submit the relevant order number and reason. The parties will review the request in light of service delivery and applicable law. Unused time is not automatically refundable on a prorated basis.
3. Provisioning & renewals
Once payment is confirmed, the system assigns a machine based on your order and displays its delivery status and SSH / VNC connection details in the console. Our target is to provision orders on the same day they are placed. Payment confirmation, information checks, and allocation can affect when the machine becomes available. Your order record in the console shows the exact service start and end times.
After receiving the connection details, promptly check that you can log in and that the hardware matches your order, then set your own access credentials. If the details are incorrect or you cannot connect, open a support ticket in the console with your order number, region, the time the issue occurred, and the error. Do not share passwords, private keys, or signing materials publicly.
You are responsible for tracking the expiry date and renewing before your rental ends. A renewal payment that has not been confirmed does not extend the rental. If you do not renew by the expiry date, access may be suspended and the machine may enter the recovery process. Builds and remote sessions may be interrupted during suspension. Do not rely on the machine as the only copy of production work.
There is no default data-retention grace period under these terms. If you have trouble renewing, submit a support ticket before expiry to confirm what options are available. Do not assume the machine will be retained unless we explicitly confirm this. Once the machine has been reclaimed and erased, renewing cannot restore its files or environment.
4. Acceptable use
Use the machine lawfully and ensure you have the necessary rights to use your code, data, software, and signing materials. Do not use the service for unauthorized access, malicious scanning, denial-of-service attacks, malware distribution, fraud, spam, or infringement of another party’s intellectual property, privacy, or other legal rights.
Do not use the machine to disrupt data center networks, bypass access controls, access other customers’ information, or share credentials with unauthorized people. Teams should clearly define administrators, users, and task ownership, and promptly revoke access when a team member leaves, a key is exposed, or an unusual login occurs. You are responsible for how people you authorize use the service.
If activity may put the platform, other customers, or third parties at risk, PushMac may restrict connections, suspend affected services, or stop the prohibited use. Where practicable, we will explain the reason and any steps required. An urgent security risk may require immediate action. You can provide further information, request a review, and cooperate with remediation through a support ticket in the console.
Dedicated resources do not authorize every use. You must still comply with applicable laws, software licenses, and third-party service rules. Do not carry out unauthorized activities under the guise of building, testing, or research. When reporting a dispute, include only information that is necessary; do not submit unrelated sensitive data in a support ticket.
5. Uptime
All regions are designed to run 365 days a year, with no scheduled downtime. Data centers provide power, network connectivity, and cooling so machines can support development across time zones and overnight CI workloads. This describes the service’s operating schedule; it does not guarantee that every remote session, external dependency request, or customer build will be error-free.
If you experience a connection or runtime issue, note when it occurred, the region used, the error message, and the impact. Report it through a support ticket in the console. Investigate whether the issue lies with the machine, your local network, a third-party code repository, a dependency service, or your build scripts rather than assuming every failed build means the machine was unavailable.
Shutdowns initiated by the customer, network setting changes, deleted system files, misconfigured access permissions, and failures caused by the customer’s own software are not equivalent to an interruption in the platform’s normal uptime. Keep configurations and scripts that you can roll back, and make necessary backups before major changes.
Natural disasters, war, measures taken by government authorities under applicable law, and other events that could not reasonably be foreseen, avoided, or overcome may affect service delivery. The affected party should promptly explain the impact and take reasonable steps to limit it. Responsibility and next steps will be determined based on the actual impact and applicable law; these terms do not promise a fixed compensation multiple.
6. Data & offboarding
Code, files, build artifacts, and other project data stored on your dedicated machine belong to you or their respective rights holders. PushMac does not proactively access project content as part of routine operations. If your help is needed to investigate an issue, provide redacted logs and only the necessary information. Do not send complete private keys, certificate passwords, or other access secrets.
You are responsible for backing up your data, verifying that it can be restored, and migrating it before your rental ends. DerivedData, dependency caches, and local build artifacts stored on the machine are not a substitute for independent backups. We recommend managing source code, release artifacts, configuration documentation, and signing materials through your team’s own data management processes.
After cancellation or expiry, the machine is reclaimed and erased before it is assigned to another customer. Erasure includes existing files and environments, which cannot be guaranteed recoverable afterward. Before the service ends, export your data, deregister any self-hosted runners, revoke access keys, and remove the machine’s authorization from your team’s automation systems.
Erasing the machine and deleting account records are separate processes. Order, payment, and support ticket records may be retained to provide the service, reconcile accounts, or meet legal obligations. To make a data-related request, contact support@pushmac.comfrom the email address associated with your account, or sign in to the console and submit a support ticket. Specify which data you want us to address.
7. Liability & dispute resolution
Each party is responsible for matters within its control. PushMac provides machine rental and data center hosting as specified in the order. Customers are responsible for their software configuration, access permissions, data backups, and use of the machine. If a fault or loss occurs, both parties should preserve relevant records, notify each other promptly, and take reasonable steps to prevent further impact.
Responsibility for a service dispute will be determined based on actual performance, the cause attributable to each party, evidence of loss, and applicable law. Any loss that could have been avoided or contained through reasonable backups or timely mitigation will be considered in light of the circumstances. These terms do not exclude or limit liability that cannot be excluded or limited under applicable law, or affect any rights customers have under that law.
These terms are governed by the laws of the jurisdiction where the platform operator is based, and that jurisdiction’s laws apply to their formation, performance, and interpretation. If a dispute arises, the parties should first communicate through a support ticket in the console or support@pushmac.com and provide the order number, the issue in dispute, and the resolution sought.
If the dispute cannot be resolved through discussion, it will be submitted to a court with jurisdiction in that same jurisdiction. While discussions are ongoing, both parties should continue to perform any obligations unaffected by the dispute that they are able to perform, and protect the other party’s information and the information of relevant individuals.
8. Changes to these terms
PushMac may update these terms when the service scope, business processes, or applicable requirements change. Updates and their effective dates will be published on this page. We will make reasonable efforts to notify customers of changes affecting important rights or obligations. If your confirmation is required, the relevant confirmation process will apply.
New terms apply according to the published effective date and the terms of your order. Updating this page does not automatically change completed transactions retroactively. If you have questions about a change, contact us before placing a new order or renewing, and keep the terms and billing records relevant to your order.
For questions about these terms, contact support@pushmac.com or submit a support ticket in the console. Current customers should use support tickets where possible, keeping the order, region, and issue together in one record so we can verify the service scope and track progress.