Terms of Service

1. Service scope

OSXHost provides cloud Macs built on Apple Silicon Mac mini hardware. For the duration of your rental, one physical machine is assigned exclusively to you. It is not a virtual machine, and its CPU, unified memory and local storage are not shared with other users. The service is intended for remote development, automated iOS builds, testing and other computing tasks permitted under these terms.

The machine lineup has three tiers: Host M4 Lite (M4 / 16GB / 256GB), Host M4 Plus (M4 / 24GB / 512GB) and Host M4 Pro (M4 Pro / 64GB / 2TB). Your order confirmation determines the machine, rental period, node and add-ons. Check the control panel for current availability.

Your service includes use of the machine with the agreed configuration and the connection details needed to access it. It does not include app development, code fixes, app distribution review or third-party software licences. You can use the macOS graphical interface and command line to configure a build environment; you are responsible for confirming project dependencies, software licences and pipeline requirements. If delivery fails or the configuration does not match your order, submit a support ticket in the control panel.

2. Orders & billing

Services are prepaid by the day, week, month or quarter, and all charges are billed in US dollars (USD). Before paying, check the machine, node, billing period, any additional SSD, Thunderbolt 5 clustering option and order total. Each billing period has its own listed price; do not calculate a weekly, monthly or quarterly charge by simply multiplying the daily rate. Your order record determines when the rental period starts and ends.

We accept only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). Available payment gateways are determined by the response from the payment interface. For USDT-TRC20, check the network, address and amount due shown with your order. For card payments, confirm the payment result and order status in the control panel; a redirect alone does not confirm successful payment.

If you have questions about an amount, payment result or order ownership, provide your order number and a transaction record we can verify. Do not pay twice, or send full card numbers, card security codes, private keys or verification codes in a ticket or email. Refunds, duplicate payments and payment issues are reviewed against the relevant order. Submitting a query does not itself complete a refund or cancel the service.

Before changing tiers, billing periods or add-ons, submit a ticket to confirm how the change will be handled, any charges and the impact on data migration. A request to make a change does not stop billing for a paid rental period. Unused time or add-ons are not guaranteed to be refundable separately.

3. Renewal, expiry & release

Use the expiry time shown in the control panel to plan your renewal. Before expiry, confirm that the renewal order has been paid and the service period has been updated. Starting a payment, submitting a ticket or sending an email does not by itself renew the service. If you have paid but the service period has not changed, promptly submit a ticket with your transaction record.

If you do not renew by the expiry date, access may be stopped and the machine may enter the release process. The retention deadline and erasure arrangements are those confirmed when you ordered and shown for that order in the control panel. No single additional retention period applies to every order on this page. If your order does not specify a retention period, export all your data before expiry; do not assume you will be able to sign in or recover the machine afterwards.

Secure erasure is performed when a service is cancelled or released. Once erasure is complete, projects, signing materials, keychains, caches and build artefacts on the machine cannot be recovered as usable copies. Keeping payment records or ordering the same tier again does not restore data from your previous machine. If you need to keep your environment, back it up and verify that it can be restored while your service is still active.

4. Uptime & service credits

OSXHost commits to 99.9% monthly uptime, with all nodes operating normally year-round, 365 days a year. Uptime measures the time the service is available; it does not guarantee how long an individual archive will take, that an app will compile successfully or that your local network will connect at a particular speed. Service incidents are assessed using order details, node operating records and support findings.

Based on a 30-day month, 0.1% equals 43.2 minutes, or about 43 minutes. Any outage beyond this allowance is converted into an extension of the service period based on the verified duration of the impact. This allowance is used only to calculate the monthly commitment. All nodes operate throughout the year, 365 days a year.

Within 7 days after an incident ends, submit a support ticket through the control panel with your order number, affected node, incident start and end times, and time zone. You may include connection errors, task logs and troubleshooting steps already completed. Remove credentials and signing materials first. If the incident is confirmed, the service credit will be applied as an extension to your service period; you can check the outcome in the ticket.

Downtime caused by force majeure or your own actions is not counted as a service incident under this commitment. Examples include shutting down the machine yourself, changing network or access rules incorrectly, or deleting system files. Local network outages and third-party dependency failures are assessed separately from physical machine faults. If you disagree with the cause or time period, add supporting evidence to the same ticket for review.

5. Acceptable use

You must not use the service for mining, bulk unsolicited email, attack scanning, distributing malware or unauthorised access, or to store, process or distribute unlawful content. You must have the necessary rights to use your projects, data, models and software, respect others’ rights, and comply with these restrictions even though your physical machine is dedicated to you.

Keep automated tasks within authorised projects and target systems, and manage your runners, scripts and dependencies responsibly. Do not use the service to disrupt other nodes, bypass access controls or compromise network security. Testing must not come at the expense of unrelated systems.

If we identify a violation or an active security risk, we may take necessary steps to restrict the relevant access or service and explain what we can disclose through your account contact details or a support ticket. You must cooperate with our review, stop the prohibited activity and provide information about corrective action. Any restrictions, reinstatement requirements and subsequent order handling will be based on the verified impact; restricting access does not determine liability.

6. Your responsibilities

You are responsible for keeping your account email, login credentials, SSH keys and machine connection details secure. Change the credentials provided at delivery when you first connect, and grant access only as needed. When a team member leaves a project or a pipeline moves to a different execution environment, promptly revoke their access and rotate any relevant keys.

You are responsible for managing signing certificates, provisioning profiles and other sensitive build materials. Keep sensitive information separate from your code, limit which automated tasks can access it, and do not put passwords in repositories, shell history or build logs. Before sharing support materials, redact access tokens, certificate contents and personal information from logs.

You are responsible for backing up data on the machine and verifying that backups can be restored. A project repository may not include uncommitted changes, signing materials, dependency caches or build artefacts, so check that these are covered separately. Before upgrading the system, changing toolchains, modifying storage or ending your service, save a copy that can restore your working environment.

If credentials are exposed or you notice suspicious access, revoke the affected keys immediately, stop impacted tasks and report the issue through a control panel ticket or to support@osxhost.com. Include your order number, when you noticed the issue and what happened. Do not send passwords or private keys that are still valid.

7. Liability & exclusions

We are responsible for delivering the agreed machine resources, investigating service faults on our platform and providing uptime credits where the eligibility requirements are met. If you cannot connect to your machine, its delivered specifications do not match your order or you suspect a hardware fault, submit a support ticket. Before a machine is replaced, confirm the impact on your existing environment and data; a replacement does not mean your data has been migrated.

Build results depend on your project code, dependencies, signing materials, toolchain versions and third-party services. We do not guarantee that every project will build without changes, or that third-party reviews, releases or dependency downloads will succeed. First determine whether an issue is due to a service fault or project configuration, then establish the appropriate scope of support.

Impacts caused by force majeure or your own actions are assessed based on the cause, what could reasonably be controlled and the actual loss. Any limitation of liability applies only to the extent permitted by applicable law. It does not exclude or limit liability where the law prohibits this, or affect rights you have under applicable law. Extensions under the uptime commitment are requested and assessed as set out in Section 4.

You should take reasonable steps to prevent losses from worsening, including keeping error records, pausing repeatedly failing automated tasks and backing up data promptly. Claims involving data loss, business interruption or other losses must be supported by facts relevant to the order, incident and scope of impact. Liability and remedies are determined under these terms and applicable law.

8. Changes & disputes

We will publish changes to these terms on the relevant page. For significant changes affecting existing orders, we will explain what applies through a control panel notice or your account email. Updates should not be understood to retroactively reduce rights already confirmed for an order. Before placing a new order or renewing, review the terms and order details then in effect, and keep any records you may need.

If you have questions about billing, release, incident assessments or service credits, first submit a control panel ticket with your order number, the issue in dispute, the relevant time period and what you would like us to check. If you cannot access your account, contact support@osxhost.com. We may need to verify your identity or order ownership before handling your request.

These terms are governed by the laws of the jurisdiction in which the platform operator is established. The parties will first try to resolve disputes through good-faith discussions. If they cannot reach a resolution, the dispute will be submitted to a court with jurisdiction in that jurisdiction, unless mandatory provisions of applicable law require otherwise.

Before ordering, make sure you understand and accept the selected rental period, your data backup responsibilities and the service scope described above. If anything remains unclear, obtain clarification about your order before completing payment.