ZoneMini Cloud Mac Hosts Terms of Service

Accessing zonemini.com, creating a Cloud Mac order, completing payment, or beginning to use a host means that the user has read and agreed to these terms and the configuration records associated with the specific order. When ordering for a company, team, or other organization, the operator must confirm they are authorized to accept these terms and manage the relevant resources.

Account name, contact email, order purpose, and payment details must be genuine, accurate, and reachable. When contact information changes, users must update it promptly in the console so they can receive notifications about order status, security actions, and changes to service rules.

Purchasers must ensure that end users also comply with these terms. When team members, contractors, or automated Runners access a host using credentials configured by the purchaser, their activity remains within the scope of the associated order.

ZoneMini provides three tiers of Apple Silicon Cloud Mac Hosts as dedicated physical machines. Each order corresponds to the selected physical node, not a virtual machine. The processor, memory, and local storage are determined by the model confirmed in the order.

Available add-ons are limited to +1TB SSD, +2TB SSD, and Thunderbolt 5 interconnects. Before ordering, confirm whether an add-on suits your workflow based on capacity, task segmentation, and rental duration.

Available locations are limited to Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the Eastern United States. All three models can be ordered in all five locations; actual availability is determined by the console in real time. Choose a location based on your code repository location, team time zone, target user region, and local network path.

All locations operate continuously 365 days a year. When immediate action is required due to a security incident, hardware risk, user activity, or an external network issue, ZoneMini may take necessary measures such as isolation, migration coordination, or access restrictions.

Before creating an order, users must verify the model, location, rental period, add-ons, and contact details item by item. Once confirmed, the selected parameters form the delivery basis for that service. To change parameters, submit a request through the console; do not assume that different configurations can be exchanged automatically.

1. 01
   Choose a model

   Select one of the three catalog tiers based on the memory, storage, concurrency, and duration required by your workload.

2. 02
   Choose a location

   Select one of the five available locations closest to your repository, team, or primary release market.

3. 03
   Review the billing cycle and add-ons

   Confirm daily, weekly, monthly, or quarterly billing, and verify any SSD expansion or Thunderbolt 5 interconnect requirements.

4. 04
   Complete payment and receive access details

   After payment is complete, check order progress and connection details in the console, then update the initial credentials promptly.

Order management, connection details, billing records, and support requests for existing orders are handled through the console. Keep your order number safe and provide the location, model, timestamp, reproduction steps, and redacted logs when requesting assistance.

Provisioning time depends on order verification, payment results, and the console's real-time response. Do not schedule an unconfirmed host for production releases before usable connection details are provided.

All orders are billed in US dollars (USD). We support only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The actual available gateway is determined by the console; no payment method not listed in these terms is provided.

The amount due is determined by the selected model, billing cycle, location, and add-on combination. The page and console calculate prices by the published billing cycle; cycles are not converted into one another, and amounts are not rounded before quoting.

Before payment, verify the network type, recipient details, card authorization status, and order amount. USDT-TRC20 transfers must use the correct network; card transaction data is handled only to the extent necessary to complete the transaction.

If an order shows an inconsistent payment status, duplicate record, or questionable amount, retain the order number and redacted transaction details, then submit a billing ticket through the console or email support@zonemini.com. Do not send complete card details, private keys, or account passwords by email.

Cloud Mac Hosts are intended for lawful software development, builds, testing, inference, transcoding, and related engineering work. Users must ensure that the source and use of code, data, dependencies, models, media assets, and automation scripts comply with applicable laws and relevant authorization requirements.

Automation tasks should use reasonable concurrency, retry, and log-retention settings. Scripts that continually fail must not retry indefinitely. High-bandwidth synchronization, batch transcoding, and model processing must prevent unbounded growth of temporary files from filling local storage.

Users are responsible for protecting console login details, SSH keys, remote-access credentials, code repository tokens, signing certificates, provisioning profiles, CI Runner tokens, and team-member permissions. Credentials should be separated by purpose; the same administrator credentials should not be shared among multiple people over the long term.

• SSH:Prefer key-based authentication, verify the host fingerprint, and restrict read access to private-key files.
• Remote access:Update temporary credentials after the first connection, lock the screen when leaving a session, and do not save authentication information on public devices.
• Code repositories:Grant tokens access only to the minimum repositories and operations required for the build. Avoid high-privilege tokens covering an entire organization.
• Signing materials:Authorized personnel should manage certificates, private keys, and provisioning profiles. Submit only redacted information in logs and tickets.
• Team permissions:Revoke access promptly when a member leaves the team or changes roles, and rotate shared credentials they may have accessed.
• Automation logs:Mask passwords, tokens, signing passphrases, payment information, and internal addresses before outputting logs.

If you discover abnormal access, an unexpected host-fingerprint change, token exposure, or an incorrect permission configuration, immediately stop the relevant automation tasks, revoke affected credentials, and submit a ticket through the console. Emergency security reports must also use support@zonemini.com.

Data changes caused by the user's own reinstallation, deletion, overwriting, disk formatting, permission changes, or script cleanup must be restored using the user's backups and version repositories. Before running an irreversible command, verify the path, mount point, and backup status.

In response to a clear security risk, overdue payment, violation of the acceptable use rules, unauthorized access, or abnormal activity that may affect service operation, ZoneMini may take measures such as restricting network access, suspending access, isolating tasks, or terminating the service, according to the level of risk. Where feasible, we will explain the reason and required follow-up verification through the account contact details or console.

Security actions are intended to control risk and protect nodes. After the user completes identity, order, or remediation verification, restoration of access will be assessed based on whether the risk has been resolved, payment status, and the impact of the violation.

When planning to stop using the service, users must export code, build artifacts, logs, model files, media assets, configuration, and other required data before the service ends. Local storage on a Cloud Mac Host should not be treated as the sole long-term archive.

After service ends, resources enter the reclamation and data-handling process. Information retained for security, transaction records, or legal obligations is handled only as necessary and for the applicable period; host data that is no longer needed is handled through the resource-reclamation process.

If you believe a suspension or termination record is incorrect, submit a ticket through the console with the order number, location, model, timestamp, and redacted logs. Do not include private keys, complete passwords, or unredacted tokens in an appeal.

ZoneMini's service scope includes the dedicated physical node selected in the order, published add-ons, connection details, assistance with host status, and related order support. Xcode, Fastlane, GitHub Actions, GitLab CI, Jenkins, React Native, Flutter, Docker, and other third-party development tools are managed by their respective providers, including their features, version policies, and external service status.

Internet routing, local carrier networks, code-hosting platforms, certificate issuance, and app-store review may affect the end-to-end workflow. During troubleshooting, ZoneMini may help confirm physical-node status, basic connectivity, and in-scope configuration. Third-party tool configuration, application-code defects, and review decisions must be handled by the user using the relevant documentation and logs.

Users must independently verify that build artifacts, signing configuration, version numbers, privacy manifests, dependency licenses, and submission materials meet project and release-platform requirements. Successfully generating an archive on the host does not mean that the application has passed validation or review by an external platform.

When these terms, an order page, or service rules undergo a material change, ZoneMini will provide notice through the website, console, or account contact email. Creating a new order or continuing to use the service after the change takes effect means that the user accepts the updated applicable rules.

These terms are governed by the laws of the jurisdiction where the platform operator is based. For disputes arising from these terms, an order, or use of Cloud Mac Hosts, the parties should first communicate in good faith through the support channel. If they cannot reach a resolution, the dispute may be submitted to a court with jurisdiction in that jurisdiction.

Send terms questions, business inquiries, security reports, and compliance-document requests to support@zonemini.com. For existing order, connection, and billing issues, log in to the console first and submit a ticket so the order record and progress can be linked.