Clear terms for orders, delivery, and responsibility

PingMini provides Cloud Mac dedicated physical machine rentals and related management access. Each confirmed order covers the model, memory, storage, node, add-ons, and rental period specified in that order. A dedicated physical machine means that, during the valid order period, the computing resources assigned to the user are not simultaneously provided to another user as a shared virtual machine instance.

The current catalog includes three configurations: PingMini M4 Core, PingMini M4 Plus, and PingMini M4 Pro. Configuration details, node coverage, and period pricing are based on the catalog shown when the user places the order. After confirmation, the confirmation page, invoice, and service records govern the rental.

The service includes physical node allocation, access credential generation, basic network access, and console management. Users may operate the assigned device through a graphical interface, command line, or automated tasks, subject to the order configuration, system status, and security policies.

• Rental periods are available by day, week, month, or quarter. Start and end times are based on the order confirmation record.
• Available nodes include Singapore, Tokyo, Seoul, Hong Kong, and the US East Coast—a total of five nodes.
• Nodes are provided under a 365-day, year-round operating standard and are not delivered on the basis of a fixed daily downtime period.
• Actual availability for catalog combinations is based on the real-time result returned when the order is submitted through the console.

Users receive the right to use the specified device during the rental period, not ownership, resale rights, or control over the underlying infrastructure. Without written confirmation, users may not split, sublet, resell, or otherwise grant a third party control of the device.

Users must have the legal capacity required to enter into and perform these terms. Anyone activating the service for a team, organization, or other entity must have appropriate authorization and ensure that the order purpose, payment arrangements, and member permissions comply with that entity’s internal rules.

The email address, order details, payment information, and technical context provided during registration and checkout must be accurate, complete, and usable. If any information changes, users must update it promptly in the console or describe the required adjustment in a support ticket. Users are responsible for helping correct delays caused by inaccurate details, unavailable email, or unclear authorization.

Account credentials, access keys, device passwords, and team-member permissions must be managed according to the principle of least privilege. Users are responsible for authorized actions performed under their accounts, including placing orders, changing configurations, downloading connection details, submitting tickets, renewing services, and authorizing members to access devices.

• Do not share primary account credentials or store credentials in public code repositories, public logs, or documents without access controls.
• When a team member leaves a project or changes responsibilities, promptly revoke their access to devices, repositories, certificates, and automation tasks.
• If you detect an unusual login, suspected credential exposure, or an unauthorized order action, immediately rotate the affected credentials and submit a support ticket through the console.
• Keys used by automation scripts must be separated from everyday interactive accounts and limited to the minimum scope required to complete the task.

PingMini may ask users to verify account or order-related information to confirm that a request comes from an authorized person. If the required verification cannot be completed, sensitive actions may be temporarily paused to protect account and device data.

Users must select the model, rental period, node, and add-ons through the purchase flow, then submit the order after confirming the configuration and amount due. Submitting an order does not itself mean delivery is complete; the service becomes available only after payment confirmation, physical node allocation, and connection information generation are complete.

The standard process consists of order submission, payment confirmation, physical node allocation, and connection information generation. The approximately 4-minute process shown on the page is an operational summary under normal conditions, not a fixed completion-time commitment for every order. Actual processing time may depend on payment confirmation, real-time availability of the selected combination, security checks, and the completeness of user information.

Users should review the order summary again before payment. Once a model, node, rental period, or additional storage has entered the delivery process, changes may require recalculating fees, migrating data, or reallocating a device, so the original order may not be directly editable.

• The order start time is based on the confirmation result, not solely on the time the user submits the form or initiates payment.
• Connection information is provided only to authorized users under the order account. Users should update the necessary credentials after the first connection.
• If payment information cannot be matched to the order, users must provide the order number, payment identifier, and necessary details for verification.
• Failure to read connection information promptly does not change the confirmed rental start or end dates.

If the selected model-and-node combination does not pass real-time availability checks, users may return to the configuration flow and choose another combination in the catalog. PingMini will not treat an unconfirmed page display as a final order record; all delivery parameters are governed by the console confirmation result.

All orders are priced and settled in US dollars (USD). The only available payment methods are USDT-TRC20 and Visa, Mastercard, or Amex through Stripe. The payment gateway available for a transaction is determined by the result returned by the backend at checkout.

Users must pay the rental fee, additional storage fee, and Thunderbolt 5 parallel-connection fee shown on the order confirmation page. Each billing period has its own catalog price and is not calculated by simply multiplying the daily rate. For weekly, monthly, or quarterly rentals, use the amount shown for the selected period.

Before paying, users must confirm the payment network, amount, order number, and receiving details. Problems caused by selecting the wrong network, sending the wrong amount, paying twice, or using an unverifiable payment identifier require the user to provide verifiable records before processing can continue.

• Card payments are processed by the applicable payment processor. PingMini does not ask users to send complete card details through a support ticket.
• On-chain payments must use the network and receiving details specified for the order. Network fees are paid by the party initiating the transaction.
• If the billing, payment, and order statuses do not match, begin verification by submitting a support ticket based on the console records.
• Taxes and other amounts that must legally be collected, where applicable, will be shown separately in the order or invoice.

Unless the order confirmation states otherwise, a started rental period is billed for the selected term. Stopping use early does not automatically shorten the confirmed period or create an automatic credit for unused time. Verified duplicate charges, amount errors, or incomplete delivery will be handled according to the specific order record.

Users may use the service for lawful software development, Xcode builds, automated testing, CI/CD tasks, local model inference testing, audio and video processing, and other work suited to the rented configuration. Users must ensure that uploaded software, data, models, certificates, and build materials have lawful sources and the necessary authorizations.

Users may not use PingMini services for unlawful activity, unauthorized access, malicious payload delivery, credential theft, network scanning, denial-of-service attacks, spam distribution, bypassing security controls, or other conduct that could harm users, third parties, or infrastructure.

• Do not probe or access devices, accounts, storage, network segments, or management interfaces not assigned to you.
• Do not run programs intended to conceal malicious activity, destroy audit records, or continuously evade resource limits.
• Do not allow tasks to consume abnormal network, storage, or computing resources in a way that materially affects infrastructure stability.
• Do not use the service to infringe intellectual property, privacy, trade secrets, or other protected rights.
• Do not bypass connection controls, modify underlying infrastructure identifiers, or interfere with PingMini management and security capabilities.

When high-risk activity is detected, PingMini may take necessary measures, including restricting network access, pausing related tasks, isolating the device, or terminating the service. Where possible, the reason and next steps will be recorded through the account email or console; when immediate risk control is required, action may come first and notice later.

If users believe a security measure is affecting normal work, they should provide the order number, node, time of occurrence, task type, error details, and troubleshooting steps already completed. More complete information makes it easier to distinguish normal build loads, configuration issues, and genuine security incidents.

Users are responsible for managing code, project files, build artifacts, keys, certificates, provisioning profiles, models, assets, and caches stored on the Cloud Mac. A dedicated physical machine provides an isolated environment but does not replace the user’s own version control, team access controls, backup, or disaster-recovery arrangements.

Important project materials should have at least one independent copy, and backups should be tested for recovery. For continuously running CI/CD workflows, store source code, dependency lockfiles, environment configuration, and artifact indexes in a traceable location rather than treating a single rented device as the only source of record.

• Private keys, signing certificates, and access tokens should be kept in controlled storage and should not be written directly into scripts, build logs, or shared directories.
• Additional SSD storage may be used for project data, build caches, or large assets, but users remain responsible for designing their own backup strategy.
• Before handing over a project, review repository permissions, automation keys, certificates, provisioning profiles, task queues, and artifact locations.
• Before the rental period ends, complete data migration, necessary exports, access revocation, and cleanup of sensitive information.

Users are responsible for confirming and bearing the consequences of data changes caused by deleting files, reinstalling environments, overwriting configurations, or running automated cleanup. When requesting data recovery, promptly provide the order number, node, file path, operation time, and most recent usable copy. Recovery depends on actual technical conditions and is not a default backup service.

After the rental period ends or the service is terminated, the device may enter data cleanup and reallocation. Users should not rely on continued access to the original device after the rental ends or treat out-of-term data retention as a migration plan.

If users need to continue using a device, they must renew before the current rental period ends and confirm the payment status. Whether the original device, node, and configuration are retained depends on the confirmation result returned by the console at renewal. An unconfirmed renewal request does not extend the rental period.

Changes to the model, node, storage, or parallel configuration may involve a new order, fee adjustments, device migration, and updated connection information. Users should back up their data first and submit the change through the options available in the console. Do not stop critical tasks on the original combination before the new combination is confirmed.

• If renewal is not completed by the due time, access may stop and the device may then enter data cleanup and reallocation.
• Before voluntarily terminating the service, users should stop automated tasks, revoke team access, and complete data migration.
• Conduct involving serious security risks, unlawful use, malicious payloads, or continued interference with infrastructure may result in immediate restriction or termination.
• If necessary verification cannot be completed because account details are inaccurate, sensitive changes and renewal processing may be paused.

Voluntary termination does not automatically change a confirmed billing period. To cancel an order that has not entered the delivery process, users should promptly submit a support ticket through the console with the order number and reason for cancellation. Whether cancellation is possible depends on the order’s processing stage and confirmation record at that time.

Termination does not affect payment obligations incurred before termination, data-management responsibilities, security requirements, or liability limitations and dispute-resolution provisions that by their nature should remain effective.

PingMini provides the Cloud Mac dedicated physical machine and related management capabilities within the scope confirmed in the order. Service performance may be affected by public networks, the user’s local network, code repositories, software dependencies, external authentication systems, payment processors, user configuration, and other events beyond reasonable control. Users should prepare reasonable fallback plans for critical releases, continuous builds, and data delivery.

Failures caused by software, scripts, drivers, network rules, permission settings, credential management, or automation installed or configured by the user should first be investigated against the user’s change records, with reproducible information provided. PingMini may help identify infrastructure and device status but is not required to maintain the user’s project code, third-party software, or internal team processes.

To the extent permitted by applicable law, PingMini’s total liability for the service is limited to the service fees paid by the user under the specific order giving rise to the claim. PingMini is not liable beyond what applicable mandatory law requires for indirect losses, loss of anticipated profits, loss of business opportunities, or losses caused by the user’s failure to back up data, revoke access, or migrate data.

• Users must report problems promptly and take reasonable measures to prevent further loss.
• Liability assessments are based on order records, system records, ticket contents, payment records, and verifiable materials available to both parties.
• Liability for force majeure, public network failures, and other events beyond reasonable control will be determined under applicable law.
• If any part of these terms is found invalid, the remaining provisions remain effective.

These terms are governed by the laws of the jurisdiction where the platform operator is based, without affecting mandatory rights that cannot legally be excluded. In a dispute, both parties should first provide factual records through the support email or console ticket and attempt to resolve the matter through discussion. If discussion fails, either party may bring a claim before a court with jurisdiction in that jurisdiction.

If you have questions about these terms, an order, or the boundaries of responsibility, email support@pingmini.com, or log in to the console and submit a support ticket. Include the order number, relevant node, time of occurrence, and the issue you want resolved.