Terms of Service

When you create an order, pay fees, receive node access credentials or actually use SDKMac Cloud Mac services, you confirm that you have read and accepted the version of these Terms in effect at that time. If you act for a company, team or other organization, you also confirm that you are authorized to order and manage services on its behalf.

These Terms apply to the service information displayed at sdkmac.com, order creation, delivery of dedicated physical Mac nodes, console management, billing and related support communications. The handling of personal information is described separately in the Data Privacy Policy, while the model, node, term and add-ons for a specific order are governed by its confirmation record.

If an order confirmation differs from a general information page in a specific configuration, the order details submitted and confirmed by the user take precedence. If the record contains an obvious error, submit a support ticket through the console for verification before continuing to use the service.

SDKMac provides dedicated physical Cloud Mac nodes rented for a selected term, console access and support related to orders and node use. Each valid order corresponds to the physical node resources listed in the order record; compute capacity and local storage are not allocated as multi-tenant virtual machine resources.

Service delivery includes order confirmation, node preparation, access credential generation and console status records. Once the node is accessible, users may use the macOS graphical interface or command line for approved software development, automated builds, testing, experiments and asset-processing tasks.

All nodes are provided under a service model designed to operate normally 365 days a year. Force majeure, user actions, external networks, third-party dependencies or security measures may affect specific workflows; responsibility is determined under the relevant sections of these Terms.

Users must provide accurate, complete account details that can be used for service communications, promptly update changed information and ensure that the email used for verification codes, order notices and support replies remains accessible. Do not create orders by impersonating another person, organization or payment account.

Users are responsible for managing account credentials, verification codes, node credentials and team permissions. Use strong credentials, limit sharing and promptly update or revoke access when a member leaves, a role changes or credentials may have been exposed. Do not publicly publish node access or transfer it to an unauthorized third party.

Orders, plan changes, node access, support tickets and billing actions completed through an account are generally treated as actions of the account holder or an authorized member. If you discover suspicious login activity, an unknown order, exposed credentials or questionable node activity, stop distributing the credentials, record the time and symptoms, and immediately submit sanitized evidence through the console.

The order total consists of the model, billing period, node region and add-ons selected by the user. Current plans support daily, weekly, monthly or quarterly billing. Each model has its own catalog price for each period; the confirmed order amount is not replaced by a simple multiple.

Before submitting an order, users should verify the model, memory, storage, node region, term and add-ons. Singapore, Japan (Tokyo), South Korea (Seoul) and Hong Kong are currently listed service regions. Both models can be ordered in all four regions; actual availability is shown in real time by the console.

After an order is confirmed, any change to its term or configuration must be made through an available console action or support ticket process. Unconfirmed email statements, project plans or internal purchase orders do not automatically modify a confirmed order.

SDKMac supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All plans, add-ons, invoices and orders are priced and settled in USD. The payment gateways actually available are determined by the backend response at checkout.

Before paying, users must verify the payment flow, order number, amount, currency and network type. For USDT-TRC20, confirm that the transfer network matches the page requirements. For card payments, ensure that the cardholder and payer are duly authorized. Verification work caused by choosing the wrong network, entering incorrect information or submitting a duplicate payment will be handled based on verifiable transaction records.

Payment completion is determined by the console invoice and payment-processing result. A bank or blockchain interface showing “submitted” does not necessarily mean that the order has been confirmed. If the status has not updated, retain the transaction ID and submit a support ticket through the console first to avoid duplicate payment.

Users may use nodes for lawful software development, automated builds, quality assurance, machine-learning experiments, remote development and content processing. All use must comply with applicable laws, software licenses, intellectual-property rules and the internal security requirements of the user’s organization.

Do not use nodes for unlawful activity, unauthorized access, credential theft, malware distribution, cyberattacks, disruptive scanning, resource abuse, access-control circumvention or infringement of third-party rights. Do not intentionally disrupt SDKMac infrastructure, other users’ services, payment processes or support systems.

If activity is detected that may threaten node, platform infrastructure or third-party security, SDKMac may, according to the level of risk, restrict the relevant connection, revoke affected credentials or suspend the associated order to investigate and contain the incident. Users must cooperate by providing necessary sanitized logs, timestamps, reproduction steps and expected behavior.

Users are responsible for confirming that the software, dependencies, models, assets, fonts, media files, signing materials and project content they install, upload, run or distribute are properly authorized. SDKMac provides node access but does not obtain licenses required for third-party software, development tools, datasets or content on the user’s behalf.

Users must also manage developer accounts, certificates, signing materials, repository tokens and team permissions themselves, and must not expose sensitive values in public repositories, shared logs or support requests. For collaboration, assign access according to least privilege and retain traceable change records.

Before installing system updates, Xcode, command-line tools, container tools or project dependencies, users should verify compatibility with the target version and existing project, and save configuration inventories and rollback materials. Project impact caused by voluntarily upgrading, deleting dependencies, changing permissions or modifying system settings must first be restored and verified by the user based on project records.

When users need to change a term, expand storage, use Thunderbolt 5 parallel connections or modify another order item, they must initiate an available console action or submit a support ticket. Whether the change can be completed within the current order, when it takes effect and what it costs are determined by the console response and final confirmation record.

Before an order expires, users should prepare to migrate project data, build artifacts, logs, configuration files and necessary credentials. After an order ends, is terminated or node access is revoked, the original access credentials may no longer work. Users must not treat a local copy on the node as the sole project copy.

For nonpayment, violations of acceptable-use rules, unauthorized resale, threats to infrastructure security or refusal to cooperate with a necessary investigation, SDKMac may, based on severity, restrict access, suspend the order or terminate the service. For remediable issues, follow-up action will be determined using the risk, evidence and order status.

Before voluntarily ending an order, users should check running tasks, external integrations, repository credentials and data-export results. Terminating an order does not automatically migrate or archive the user’s project or disconnect third-party services.

Before using a workflow in production, users should verify the compatibility of macOS, Xcode, command-line tools, project dependencies, signing materials, remote-access methods and automation scripts. A single task that passes testing does not mean that all projects, branches, dependency versions or concurrency conditions will produce the same result.

Remote networks, users’ local networks, code hosting, dependency downloads, payment processing and other third-party services may affect connectivity or workflows. When an issue occurs, the parties should assess its source using console status, order records, reproducible steps and sanitized logs, rather than relying only on a single speed test or subjective experience.

Users should maintain independent project backups, configuration inventories, artifact archives and recovery procedures, and should keep copies in code repositories, object storage or other locations consistent with team policy and business criticality. SDKMac does not limit liability that cannot lawfully be limited. Other liability is determined under the law of the jurisdiction where the platform operator is based, considering actual loss, the parties’ conduct and the order relationship.

SDKMac may update these Terms to reflect the service catalog, payment process, security requirements or legal obligations. Revised text will be published on this page. Continuing to create new orders or use the service after an update takes effect means that the user accepts the updated rules that apply.

For order, connection, billing or node-status issues, log in to the console and submit a support ticket so the relevant order and node records can be linked. For pre-purchase questions, terms inquiries or login problems, go to contact the service team or email support@sdkmac.com.

The parties should first seek to resolve disputes through the order records, payment records, console status and written communications. These Terms are governed by the law of the jurisdiction where the platform operator is based. If consultation does not resolve the dispute, it must be submitted to a court with jurisdiction in that jurisdiction.