Acceptance & Scope
When a user visits the NowMini website, creates or uses an account, places an order, completes payment, or actually connects to and uses the Cloud Mac service, they confirm that they have read, understood, and agreed to these terms and to the configuration, region, term, add-ons, and fee conditions shown in the order confirmation interface.
If a user acts for a team, company, or other organization, they confirm that they are authorized to accept these terms on its behalf and will ensure that everyone granted node access follows the same rules. Internal approvals, procurement procedures, or permission arrangements among members do not change the account holder’s responsibility for account activity and service use.
These terms apply to website information, account activity, order placement, node access, and related support. If an order page gives more specific details about a configuration or term, those details and these terms together form the agreed service conditions. If they conflict, the specific information clearly displayed in and confirmed for that order takes precedence.
Service Description
NowMini provides Cloud Mac services through dedicated physical machines. Each valid order corresponds to a physical node that is not shared with other customers as a virtual instance and is not a virtual machine service. Users may run development, build, automation, inference, and compliant creative workloads through supported command-line or graphical connection methods.
The current catalog configuration is NowMini M4: Mac Mini M4, M4 chip, 16GB RAM, and 256GB SSD. The chip, memory, storage expansion, Thunderbolt 5 pairing, node region, and term included in an actual order are determined by the order content confirmed at checkout.
Available nodes are in Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. Actual availability for each model and region combination is shown in real time in the console. Users should choose a node based on their team’s time zone, network access, data-transfer path, and workload. Differences in cross-region network quality do not change the node’s physical configuration.
Delivery & acceptance checklist
Once node information is available, users should verify the region, model, memory, base storage, term, and selected add-ons, then complete connection testing and environment validation before migrating production materials.
Accounts & Credentials
Users must provide accurate, complete information suitable for necessary notices and update it promptly when it changes. Users are responsible for protecting account credentials, node usernames, SSH keys, automation tokens, and other access materials. These must not be distributed through public repositories, unencrypted messages, or uncontrolled shared directories.
When teams use a node, they should assign appropriate permissions by task and member, restrict access sources, and prefer separate accounts with least-privilege keys. When someone leaves the team, responsibilities change, or temporary collaboration ends, the relevant access must be revoked and affected credentials rotated promptly.
Orders, configuration choices, node operations, support tickets, and other activity initiated under an account are generally treated as actions of the account holder. If a user suspects a credential leak, unusual login, or unauthorized use, they should immediately stop further distribution of the affected credentials, preserve necessary redacted records, and submit a ticket through the console.
Users must not attempt to bypass authentication, access controls, resource isolation, or security checks, nor transfer node access to third parties who are not authorized to use the service. Where shared access is necessary for business purposes, the account holder must still maintain an auditable member list and clear permission boundaries.
Orders & Billing
Services may be ordered by the day, week, month, or quarter. Before placing an order, users should confirm that the selected term covers environment preparation, task execution, result validation, and data export. Order fees consist of the model’s base fee, the selected term, and any explicitly added storage or pairing add-ons.
All amounts are charged and settled in USD. The only supported payment methods are USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The payment gateway actually available is determined by the checkout flow. Users should verify the payment network, amount, order ID, and recipient details to avoid processing delays caused by selecting the wrong network or entering incorrect information.
Payment results, order status, and node status are determined by the console records. Users may not request changes to a confirmed configuration or term because internal procurement is incomplete, team members were not informed, or the order status was not checked in time. Any adjustment request is handled separately based on the order’s current status.
If a payment status requires review, users should provide the order ID, payment method, time of the transaction, and verifiable information that does not contain complete sensitive credentials. Do not submit full card data, private keys, seed phrases, passwords, or key files that can directly log in to a node by email or ticket.
Acceptable Use
Users may use the service for lawful software development, iOS or macOS builds, CI/CD, automated testing, MLX inference, media processing, and other workloads that do not infringe third-party rights. Users must ensure that they have the necessary authorization to obtain and use code, models, data, certificates, media, and tools.
Users must not use or assist others in using the service for unlawful activity, unauthorized access, credential theft, malware distribution, abusive network scanning, denial-of-service attacks, spam distribution, evasion of security controls, or infringement of intellectual property, privacy, or other third-party rights. They must not intentionally compromise the stability of nodes, networks, or other service components through sustained abnormal loads.
Users must not impersonate others, falsify orders or support information, interfere with security investigations, or continue the same activity after receiving a risk-mitigation request. Automated tasks should use reasonable concurrency, timeout, log-retention, and failure-exit settings to prevent runaway loops from continuously consuming resources.
To determine whether activity violates these terms, NowMini may assess verifiable account records, node events, network anomalies, ticket materials, and related facts. Where necessary, NowMini may ask users to explain the nature of a task, its authorization source, or risk-reduction measures, but will not require passwords or keys to be submitted through public contact channels.
Data & Backup Responsibility
Users are responsible for maintaining recoverable copies of source code, certificates, model files, media assets, dependency caches, configuration files, and build artifacts. A Cloud Mac node should not be the sole storage location for these materials. Important data should be kept in a user-controlled repository, object storage, or another system suitable for recovery.
Before starting work, users should verify data imports, permissions, and the toolchain. During execution, they should retain necessary logs and intermediate results. Before an order expires, they should export the final output and verify that the copy is readable. Copying files without verifying their integrity does not constitute completed export.
Users must manage the minimization and cleanup of sensitive materials themselves. Logs submitted with support requests must be redacted and should not contain passwords, private keys, complete access tokens, or reusable authentication information. During team handoffs, users should also address work directories, caches, temporary accounts, and access keys—not just source code.
Users must export their data before service expiration, termination, or the end of node access. Failure to create and verify backups while access is available may make work results unusable. NowMini provides node services and support paths, but does not replace the user’s own version control, backup procedures, or business continuity planning.
Continuous Node Operation & Emergency Response
During the active service period, nodes are designed to operate 365 days a year. Users may run compliant workloads throughout their term and should check the current order and node status in the console.
If a real and immediate security incident, hardware failure, network anomaly, or force majeure event occurs, access may be briefly restricted to isolate risk, restore the node, or protect data and infrastructure. Such action is based on the actual event and does not constitute a fixed, periodic, or prearranged downtime mechanism.
When users detect a connection interruption or task anomaly, they should first record the time, node region, client error, last successful action, and troubleshooting steps already taken. They should then check their local network, access sources, credential permissions, and client logs. If assistance is needed, submit a ticket through the console with redacted information.
When changing system settings, adjusting permissions, clearing disks, terminating processes, or running automation scripts, users should assess the impact on current tasks. Environment changes caused by user actions should be investigated first through version records, task logs, and backup recovery.
Suspension & Termination
If an account is overdue, appears to involve unauthorized access or malicious activity, presents a security risk, has a material impact on infrastructure, or otherwise violates these terms, features may be restricted, node access may be suspended, or the relevant service may be terminated according to the level of risk.
Where the matter can be handled without increasing risk, users may be asked to provide information, correct a configuration, reduce abnormal load, revoke compromised credentials, or stop the relevant task. If the risk is urgent, the activity is clearly unlawful, system security is persistently affected, or the user refuses a reasonable mitigation request, restrictions may be imposed immediately.
Restriction or termination does not release the user from responsibility for orders already incurred or automatically extend a confirmed term. Users should maintain backups and export readiness while the service is active and accessible, rather than treating a termination notice as the sole trigger for data export.
When users wish to stop using the service, they should complete task wrap-up, result validation, data export, temporary credential revocation, and team permission removal before the current order expires. Order-related issues may be submitted through a console ticket with the order ID and requested action.
Responsibility, Updates & Contact
To the extent permitted by applicable law, each party is responsible for its own account management, permission settings, data processing, content authorization, and operational decisions. Users should establish version control, backups, rollback procedures, logging, and access audits according to the importance of their tasks, and should not treat a single node as the only recovery source.
For losses directly caused by incorrect information supplied by the user, leaked credentials, excessive authorization, prohibited workloads, faulty scripts, unverified backups, third-party tool failures, local network issues, or force majeure, responsibility will be assessed based on actual causation, each party’s conduct, and applicable rules. Any limitation of liability is subject to applicable law and does not exclude liability that cannot legally be limited.
These terms are governed by the laws of the jurisdiction where the platform operator is based, without affecting mandatory rules that must apply by law. Disputes arising from these terms or the service should first be addressed through written contact. If negotiation does not resolve the dispute, it may be submitted to a court of competent jurisdiction in that jurisdiction.
These terms may be updated as service processes, security requirements, or applicable obligations change. Material updates will be published on the website together with revised effective information. Continuing to place new orders or use the service after an update takes effect means that the user accepts the updated terms. The specific configuration, price, and term of a confirmed order remain governed by that order’s records.
Questions about these terms, disputes, orders, or compliance may be sent to support@nowmini.com. Users with existing orders should first log in to theconsole to submit a ticket, including the order ID, node region, time of occurrence, issue description, and redacted records.