Cloud Mac Terms of Service

By visiting the MiniDebug website, creating an account, signing in to the console, placing a Cloud Mac order, or continuing to use a delivered host, you agree to comply with these Terms of Service and the rules for specific features stated on the order page, plan pages, security information, and Privacy Policy.

Anyone operating an account on behalf of a company, team, or other organization must confirm that they are authorized to accept these terms for that entity. Authorized account members must also understand their responsibilities before receiving device, order, or ticket permissions.

Each order record states the model, rental term, region, add-ons, quantity, and USD subtotal. The order record and these terms together form the agreement for that service. If general information differs from the specific parameters in a confirmed order, the confirmed order record prevails.

When registering and placing orders, provide accurate, complete information that can be used to fulfill the order. Update your account promptly when contacts, project ownership, or authorized members change, so delivery, billing, and security notices reach the correct people.

Credential and member management

• Use separate, sufficiently strong credentials for your account and remote connections. Never store them in plain text in repositories, build logs, or collaboration messages.
• Grant access only to members with a genuine work need, and revoke it promptly when members leave the team, change roles, or finish the project.
• Prefer key-based command-line access. Regularly review authorized keys, active sessions, and records of unusual activity.
• If credentials are exposed, an unknown login is detected, or an unauthorized order operation occurs, update the credentials immediately and submit a ticket through the console.

The account holder is responsible for orders placed under the account, region selection, add-ons, host operations, and ticket content. Collaboration between multiple people does not change the account holder’s responsibility for access configuration and activity records.

MiniDebug provides Cloud Mac rentals, physical node access, order management, remote connection details, and support tickets. Each valid order corresponds to one dedicated physical machine; the device is not a virtual machine. Dedicated device access does not mean that internet links, upstream networks, or public software services are exclusive to one user.

The current configuration is MiniDebug M4, with a Mac Mini M4, 16GB RAM, and 256GB SSD. When ordering, users may select supported regions and add-ons listed for this model. Actual availability is determined by the console’s real-time response.

Nodes operate normally 365 days a year. Host availability, remote connection status, and user build-task status are separate indicators. An accessible node does not guarantee that project dependencies, signing configuration, or build scripts will succeed; users should assess system status and project logs separately.

Delivery boundaries

MiniDebug is responsible for delivering the physical node associated with the order, the management entry point, and basic infrastructure operations. Users are responsible for project code, build parameters, certificates, provisioning profiles, repository permissions, dependency versions, remote sessions, and preserving build artifacts. Support may help identify infrastructure and environment information but will not make project release decisions for the user.

Cloud Macs are available with daily, weekly, monthly, or quarterly rental terms. The amount due for each order is the USD amount shown before submission on the order page. The invoice must list the base rental term, selected region, additional storage, Thunderbolt 5 parallel connection quantity, and order total.

Different billing periods are independent order options and must not be assumed to convert using a fixed multiplier. When renewing, review the period, price, region, and add-ons shown on the order page at that time before submitting.

The billing period is calculated from the order confirmation and entry into the delivery process according to the console record. Before the current rental term ends, users must decide whether to renew or migrate their data. Unread notices, missed team handoffs, or an ongoing project do not extend the rental term.

Orders support only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All amounts are settled in USD. The payment gateway actually available is determined by the backend response when the order is submitted.

When using USDT-TRC20, verify the network, recipient details, and order amount carefully. When paying by card, complete the required verification on the payment page. If records differ because of incorrect information, a wrong network, or duplicate submission, provide the order ID through a support channel for investigation.

New purchases must be made through the ordering entry point by selecting a model, period, region, and add-ons. Renewals, host management, billing review, and ticket handling must be completed in the console. The contact page does not replace order confirmation, and we will never ask you to send complete payment credentials by email.

At checkout, users may select +1TB SSD, +2TB SSD, or Thunderbolt 5 parallel connection. Add-ons are billed for the selected rental period; Thunderbolt 5 parallel connection is charged per device and by selected quantity.

Additional storage expands the workspace but does not change the base model designation of M4, 16GB RAM, and 256GB SSD. Choose capacity based on the size of repositories, dependency caches, archived artifacts, model files, and media assets, while leaving room for system and temporary files.

Thunderbolt 5 parallel connection must be selected when placing the order. Users are responsible for designing task orchestration, network topology, queues, and data synchronization for multi-device workloads. The parallel capability itself does not automatically create a build queue or assign tasks.

• Before submitting, confirm the add-on name, period, quantity, and USD subtotal.
• Confirm that the selected capacity can hold source code, dependencies, caches, archives, and temporary output.
• For multi-device tasks, define cleanup rules, concurrency limits, retry behavior, and the artifact aggregation location.
• After order confirmation, use the final invoice details in the console to verify delivery.

Cloud Macs may be used for lawful software development, automated builds, testing, AI inference experiments, audio and video processing, and authorized remote work. Users must ensure that their code, data, media, models, tools, and activities comply with applicable rules and that they have the necessary rights and permissions.

Prohibited activities

• Conducting unlawful activities or using the service to assist, conceal, or distribute unlawful content or operations.
• Scanning, attempting to access, or controlling accounts, devices, networks, repositories, or services without authorization.
• Creating, running, or distributing malicious code; stealing credentials; compromising system integrity; or bypassing access controls.
• Launching network abuse, resource-exhaustion attacks, spam distribution, or other activities that affect normal node operation.
• Copying, distributing, or processing content protected by intellectual property rights, trade secrets, or confidentiality obligations without permission.
• Circumventing order limits, sharing access beyond the authorized scope, or disrupting normal use by other nodes or users.

When an unusual task is detected, MiniDebug may ask the user to explain its purpose, stop related processes, rotate credentials, or provide redacted logs. Users must cooperate with necessary checks and retain records showing the task’s source, authorization scope, and execution time.

Users are responsible for the legality, accuracy, backup, and migration of their code, certificates, provisioning profiles, environment variables, repository tokens, media, models, caches, build artifacts, and other data. Device access does not change the ownership or rights associated with that data.

Before the rental term ends, the order is terminated, or the user releases the host, confirm that source code, signing materials, experiment results, audio and video projects, and build artifacts to be retained have been migrated to a user-controlled location and that the backups can be read.

Recommended pre-release checklist

1. 01
   Stop tasks

   Confirm that build, upload, synchronization, export, and model inference processes have finished.

2. 02
   Export artifacts

   Migrate archives, logs, experiment results, project files, and configurations that need to be retained.

3. 03
   Remove credentials

   Delete repository tokens, upload keys, environment variables, and sensitive materials stored locally.

4. 04
   Verify backups

   Spot-check key files at the destination and confirm that their contents are complete and can support future recovery.

When submitting logs for troubleshooting, remove passwords, private keys, complete tokens, payment credentials, signing certificate passwords, and unredacted source code. Keep only the timestamps, commands, error excerpts, and environment versions needed to reproduce the issue.

In cases of unresolved overdue payments, apparent security risks, exposed credentials, violations of acceptable-use rules, malicious activity, legal requirements, or device failures requiring immediate isolation, MiniDebug may restrict relevant functions, suspend access, or terminate an order based on the scope of the impact.

When taking action, MiniDebug will determine the response based on the urgency of the risk, affected scope, recoverability, and user cooperation. Where credential rotation, process termination, or reduced permissions can resolve the issue, we may first ask the user to take the corresponding action. Where there is a risk of continued spread, access may be restricted before investigation.

If a user wants to stop using the service, they should first migrate data, end tasks, and manage the order in the console. Termination does not waive payment obligations already confirmed before termination, nor does it affect the parties’ continuing responsibilities regarding data protection, intellectual property, dispute handling, or existing activity records.

If a user believes a restriction or termination was made in error, they may submit the order ID, region, time of occurrence, impact scope, reproduction steps, and redacted logs through a console ticket. The support team will review the records.

MiniDebug is responsible for the physical node delivery, management entry point, and order records within its control. Users are responsible for account permissions, project code, dependency services, build configuration, credential use, data backups, and release decisions. Responsibility for an issue will be determined according to the parties’ actual control, activity records, and direct impact.

For impacts caused by force majeure, public network issues, the user’s local network, the user’s own actions, unauthorized third-party activity, or failures in software and services relied on by the user, both parties should first take reasonable steps to mitigate loss, preserve records, and restore the workflow.

Governing law and dispute resolution

The formation, interpretation, performance, and dispute resolution of these terms are governed by the laws of the jurisdiction where the platform operator is based. In a dispute, the parties should first submit factual records through a support channel and attempt to resolve the matter through consultation. If consultation fails, either party may bring the matter before a court with jurisdiction in that jurisdiction.

Changes to these terms

MiniDebug may update these terms in response to changes in service features, billing processes, security requirements, or applicable rules. Material changes will be announced through the website, console, or other necessary notice, with the effective status of the new version stated. Continued use of the service after the changes take effect constitutes acceptance of the updated rules.

To obtain the current version, review change history, ask questions about these terms, or submit dispute materials, email support@minidebug.com or sign in to the console to submit a ticket. Include the information needed to verify your account and the relevant order ID. Do not send passwords, private keys, or complete payment credentials.