1. Service Definition
“Apple Cloud Mac” means a remote computing service delivered by VPSGit over the internet, running macOS on Apple Silicon. Each valid order corresponds to the physical node selected in the catalog and may be used by authorized users within the order’s scope for software development, automated builds, inference, media processing, or other workloads permitted by these Terms.
“Physical node” means the actual Apple Silicon device hosting the service. “Dedicated physical machine” means that, during the order term, the device’s compute, memory, and primary storage are not shared with other customers’ running instances. The service is not a virtual machine product, although network connectivity, payment processing, dependency downloads, and third-party software may involve other service providers.
“Console” means the management portal used to verify identity, place orders, view order status, manage instances, and submit support tickets. “Term” means the fixed daily, weekly, monthly, or quarterly usage period selected in an order. “Add-ons” include the SSD expansion and Thunderbolt 5 parallel configurations expressly listed in the order catalog; their scope, quantity, and price are determined by the information shown in the Console when the order is submitted.
2. Accounts & Eligibility
You must have the legal capacity required to enter into and perform these Terms and must provide true, accurate, and reachable account and order information. If you place an order for a team or other organization, you confirm that you have the necessary authorization and the right to bind that organization and its authorized members to these Terms.
You are responsible for protecting email verification codes, login credentials, SSH keys, remote-access credentials, and Console sessions, and must not disclose them to unauthorized persons. When a team uses the service, establish identifiable access boundaries for each operator and promptly revoke access for anyone who leaves or no longer participates in the project. Do not share credentials that prevent accountability.
If you discover an unusual login, exposed credentials, unauthorized configuration changes, or suspected abuse, immediately stop the affected access method, rotate the relevant keys, and notify us through a Console ticket or at support@vpsgit.com. To protect the service and other users, we may restrict suspicious sessions or request additional identity and order information during verification.
3. Orders & Delivery
Before placing an order, verify the model, term, node, storage add-ons, Thunderbolt 5 parallel configuration, and payment information. Combinations listed in the catalog are generally orderable, but actual availability is based on the real-time result returned by the Console when you submit the order. Delivery is not complete until payment has been confirmed.
Standard delivery includes payment confirmation, availability verification, system and network configuration, and issuance of access credentials, and normally takes about 4 minutes. This is a process target under normal conditions, not an absolute guarantee for every order. After delivery, promptly verify the remote connection, SSH, disk capacity, and that the selected node matches your order.
If the payment gateway is delayed, order information is incomplete, security verification requires additional materials, or an uncontrollable event prevents automated delivery from continuing, we will retain a verifiable order status in the Console and explain the required steps through a ticket. Do not submit the same payment again or attempt to bypass verification to accelerate delivery. If an order is disputed, first provide the order number and payment proof for review.
4. Pricing & Payment
All orders are priced and settled in US dollars (USD). We support only USDT-TRC20 and Visa, Mastercard, and Amex processed through Stripe. The available gateway is determined by the result returned by the Console. Verify the receiving network, order amount, and payment status before completing the transaction.
The amount due for the model, fixed term, and add-ons is the price displayed and confirmed in the Console when you submit the order. Pricing applies to the selected term and is not automatically converted to billing periods outside the catalog. For renewals, added storage, configuration changes, or a different model, rely on the items and amounts shown on the new order confirmation page.
You are responsible for fees charged by your payment account, blockchain transfer, or card issuer and must ensure that the received payment details match the order requirements. If payment has not been confirmed, the transfer network is incorrect, the amount does not match, or the payment cannot be linked to the order, we may request verifiable supporting materials before processing it.
5. Renewals, Changes & Termination
Renewals must be completed through the Console before the current term ends. Whether the original model, node, and add-ons can be retained depends on the real-time availability shown by the Console when the renewal order is submitted. Allow time for internal approval, payment confirmation, and data migration; a created but unpaid renewal order does not replace a valid term.
Changing the model or node generally requires a new availability check and may involve new device configuration, data replication, access-policy updates, and a short parallel validation period. Cross-region migration is not an instant, lossless switch. Confirm the destination node, dependency download paths, and team access routes before scheduling data transfer and retiring the old environment.
When the term ends without a completed renewal, access may stop and the service may enter the reclamation process. You are responsible for exporting code, build artifacts, models, media files, logs, and other necessary data before the term ends, and for revoking team access. If you seriously breach these Terms, endanger platform security, or continually affect other services, we may restrict or terminate the relevant service and retain necessary records for security investigations and dispute handling.
6. Acceptable Use
You must not use the service for unlawful activity, unauthorized access to other systems, scanning or exploiting vulnerabilities in targets you do not control, distributing malicious code, conducting cyberattacks, sending abusive traffic, or otherwise disrupting the normal operation of the platform, networks, or third-party services.
You must not infringe another person’s copyright, trademark, trade secrets, or other intellectual property; process data without lawful authorization; or evade responsibility by concealing origins, bypassing access controls, avoiding resource limits, or interfering with security monitoring. Automated builds, scraping, inference, and media workloads must use reasonable concurrency, retry, and rate limits.
If we detect conduct that may threaten service security or stability, we may take necessary measures such as restricting network access, isolating processes, suspending access, or requiring remediation. You must cooperate by providing the task purpose, process information, time range, and remediation records. If you refuse to remediate or repeatedly commit serious violations, we may terminate the relevant order.
7. Uptime & Service Credits
VPSGit targets 99.9% service uptime. Uptime is measured by whether the affected order can normally access its delivered physical node and core network connection during the valid term. The service runs continuously 365 days a year. An issue with an individual application, build script, or third-party dependency does not by itself mean that the Apple Cloud Mac service is unavailable.
Impacts caused by user configuration, user-initiated shutdowns, incorrect firewall rules, poor credential management, workloads exceeding device capacity, the user’s network, public network paths, third-party software or service failures, legally required restrictions, or force majeure are excluded from uptime calculations. We assess the event scope using platform monitoring, node logs, network records, and reproducible information supplied by the user.
Users who believe an order qualifies for service credits must submit a request through a Console ticket within 7 calendar days after the affected term ends, including the order number, node, start and end times of the impact, observable symptoms, and checks completed. If verification confirms eligibility, we will provide service credits for the affected period. Credits apply to future eligible services, are not redeemable for cash, and the outcome will be recorded in the relevant ticket.
8. Data & Backup Responsibilities
Maintain recoverable backups independent of the Apple Cloud Mac and configure versioning, verification, and recovery tests according to the importance of your workload. A code repository is not a substitute for complete backups of build artifacts, model files, media assets, configuration records, and local databases. Data stored only on a single physical node may be unrecoverable.
You are responsible for protecting signing materials, access keys, tokens, certificates, and other sensitive information, limiting their use with least-privilege controls, and rotating them promptly after team handoffs, personnel changes, or suspected exposure. Do not place sensitive materials in public repositories, build logs, or shared directories accessible to unrelated members.
Before the term ends, complete data export, result verification, account revocation, and any necessary local cleanup. After termination, the node will undergo access revocation and data cleanup under operational procedures. Do not treat this process as a backup service or rely on a temporary recovery opportunity after the term ends.
9. Liability & Indemnity
To the extent permitted by applicable law, neither party is liable for indirect, incidental, special, or consequential losses arising from use or inability to use the service, including lost profits, business interruption, lost opportunities, or builds and releases not completed as planned. Use independent backups, alternative build paths, and pre-release validation to manage business continuity risks.
Third-party software, code repositories, payment processing, public networks, dependency mirrors, and other services not directly controlled by VPSGit are the responsibility of their respective providers with respect to functionality, licensing, and availability. You are responsible for losses caused by your scripts, system configuration, permissions, data content, workloads exceeding resource capacity, or unauthorized operations.
To the extent permitted by applicable law, you must indemnify VPSGit for reasonable claims, losses, or costs arising from your breach of these Terms, infringement of third-party rights, unlawful data processing, or improper actions by your authorized members. No liability limitation excludes liability that cannot legally be limited. The parties’ specific responsibilities will be determined based on the order, incident records, and actual provable losses.
These Terms are governed by the laws of the jurisdiction where the platform operator is based. For disputes arising from these Terms or the service, the parties should first negotiate in good faith through support@vpsgit.com or a Console ticket. If negotiation does not resolve the dispute, it will be handled by a court with jurisdiction in that jurisdiction.
10. Changes & Contact
These Terms take effect on September 1, 2026. We may update them to reflect changes in service features, operational processes, security requirements, or legal obligations. Material changes affecting users’ principal rights or obligations will be announced prominently on the website, through the Console, or using the contact information associated with the account, together with the new effective date.
Continuing to use the service after changes take effect means you agree to be bound by the updated Terms. If you do not agree to a material change, stop creating new orders before the new Terms take effect and complete data export before the current term ends. Confirmed orders remain governed, within their applicable scope, by the fixed-term terms in effect when the order was submitted.
For questions about orders, interpretation of these Terms, service incidents, or disputes, log in to the Console to submit a ticket or email support@vpsgit.com. Include a verifiable order number, the relevant time range, and necessary facts. Do not include passwords, private keys, or other access credentials in an email or ticket.