Cloud Mac Rental Terms

By accessing this website, creating or confirming an order, paying fees, receiving device information, or using a Cloud Mac service provided by DPLYMAC, you acknowledge that you have read, understood, and agreed to be bound by these Terms. If you act for a company, team, or other organization, you also confirm that you have authority to accept these Terms on its behalf.

If you do not agree to these Terms, stop ordering or using the services. Browsing public content does not require purchasing a service, but the rules concerning website access, security, and intellectual property still apply.

Account registration details, order contacts, and payment-related information must be truthful, accurate, and kept current. When using the service on behalf of a team, the team is responsible for managing member permissions and for the actions of its authorized users.

DPLYMAC provides Cloud Mac machines based on Apple Silicon. Each valid order corresponds to the physical node, dedicated physical machine configuration, billing cycle, and add-ons listed in the order confirmation. The product is not a virtual machine.

The current catalog includes two configurations: the Standard plan includes an M4, 16GB RAM, and a 256GB SSD; the Pro plan includes an M4 Pro, 64GB RAM, and a 2TB SSD. Available nodes and add-ons are shown in real time on the order page and are fixed by the order confirmation.

• The service includes remote access to the confirmed device, order management information, and necessary technical support procedures.
• Users are responsible for configuring and validating software versions, development tools, project dependencies, and user-installed software for their workloads.
• Devices may be used for iOS and macOS builds, CI/CD execution, remote development, and compliant AI experiments.
• Renting a device does not automatically grant licenses for third-party software, code repositories, signing materials, or other licensed resources.

Services may be billed by the day, week, month, or quarter. The amount due is based on the USD amount shown on the order page, the selected model, node, term, quantity, and add-ons, and is governed by the final order confirmation.

Submitting a configuration does not constitute an order. An order is formed once the user completes the required confirmations and receives a valid order record. Actual availability is returned in real time by the dashboard; although catalog combinations may be submitted normally, the order confirmation controls the final device details.

Before confirming, users should check the following:

• Whether the model, chip, memory, and base SSD meet the task requirements.
• Whether the target node suits the team's working time zone, primary access location, and dependency routes.
• Whether the billing cycle covers the complete period needed for builds, testing, release, and data export.
• Whether add-ons such as +1TB SSD, +2TB SSD, or Thunderbolt 5 parallel connectivity are actually needed.

Changes to the rental term, device quantity, or add-ons are governed by the executable options in the dashboard and the new confirmation record. Fees, terms, and device entitlements are calculated separately for different orders and are not automatically combined unless expressly recorded.

All orders are priced and settled in US dollars (USD). Only the following two payment methods are supported; the gateway actually available is determined by the backend response at checkout:

• USDT-TRC20.
• Visa, Mastercard, or Amex, processed by Stripe.

Users must verify the payment network, amount, recipient details, and order reference. Processing issues caused by selecting the wrong network, entering incorrect information, repeating an action, or using an unsupported payment route must be reported through a dashboard ticket with the order reference and verifiable records.

Required card payment information is handled by the applicable payment flow. DPLYMAC retains only the information needed for order verification, accounting records, security audits, and necessary obligations. Users must not submit full card security codes, passwords, private keys, or other unnecessary sensitive credentials.

Users may use Cloud Mac for lawful software development, automated builds, testing, remote development, data processing, and experimentation, but must not use the device, network, or account to:

• Conduct activities that violate applicable rules or help others evade lawful restrictions.
• Access, scan, disrupt, or control other systems, accounts, networks, or data without authorization.
• Create, host, or distribute malware, steal credentials, run destructive code, or conduct denial-of-service activities.
• Abuse computing, storage, network, or remote-session resources in a way that affects the normal operation of physical nodes, support systems, or other users.
• Infringe copyrights, trademarks, trade secrets, privacy rights, or other third-party rights.
• Forge identities, order information, payment records, support evidence, or system output.
• Bypass access controls, security audits, device isolation, or reasonable technical restrictions.

When activity presents a real risk to service security, device integrity, or third-party rights, DPLYMAC may restrict access, request an explanation, preserve necessary records, or terminate the affected service.

Users are responsible for their accounts, access credentials, code, data, build configurations, certificate materials, and task content. Teams must establish procedures for member authorization, offboarding, credential rotation, and activity logging.

• Use separate, strong, and securely stored credentials for accounts and remote connections.
• Install and use only software, dependencies, fonts, assets, and development tools obtained under valid licenses.
• Maintain independent backups of code, databases, build artifacts, configuration files, and critical logs.
• Securely manage certificates, provisioning profiles, keychain contents, deployment keys, and automation tokens.
• Redact logs before submitting a ticket and never send passwords, private keys, certificate passphrases, or recovery codes.
• Verify the permissions of scripts, runners, and automated tasks to prevent infinite loops, abnormal concurrency, or unbounded disk writes.
• Ensure that the purpose of each task, code source, data processing method, and release activity is lawful.

Users should promptly review order and device information in the dashboard. If they discover exposed credentials, suspicious logins, unknown processes, or tasks deviating from expectations, they must immediately stop the affected tasks, rotate credentials, and submit a dashboard ticket.

After an order is confirmed, delivery information including the device configuration, physical node, system information, access method, and rental term will be provided in the dashboard. After the first connection, users should verify the chip, memory, disk, operating system version, and development tool paths; if anything differs from the order record, pause critical tasks and submit a ticket.

Nodes and add-ons are governed by the order confirmation. Configuration, term, or additional storage changes must be made through an available dashboard process; verbal descriptions, email proposals, or local records that have not been confirmed do not change an order.

All nodes operate normally 365 days a year. If a device, network path, or access issue occurs, support will investigate based on the scope of impact, reproducibility, and submitted materials. A valid incident report should include, where possible:

• The order reference and device configuration.
• The selected node, time of occurrence, and time zone.
• Reproduction steps, expected result, and actual result.
• Redacted command output, error messages, and necessary screenshots.
• Actions already attempted and their results.

Technical support is intended to identify issues with order delivery, device access, and basic operation. It does not replace project architecture, third-party software licensing, business-code debugging, or review of release results by the user.

Users must always keep independent copies of their data and should not use a rented device as the sole storage location for code, assets, databases, signing materials, or build artifacts. Before the rental term ends, users should allow sufficient time for export, verification, and cleanup.

• Export code, build artifacts, logs, files still needed from caches, and project configuration.
• Verify that exported files are readable, checksums match, and restoration testing has been completed in an independent location.
• Revoke automation tokens, deployment keys, repository credentials, and temporary access authorizations.
• Remove certificates, provisioning profiles, keychain contents, environment variables, and scripts containing sensitive information.
• End remote sessions and stop runners, background processes, and scheduled tasks.
• Clean up project data, log copies, download folders, temporary directories, and recovery areas.

The end of a rental term does not create an ongoing storage service. Users are responsible for impacts caused by failing to export data promptly, verify backups, remove credentials, or complete environment cleanup. To request help confirming the end status of an order, submit a dashboard ticket before the rental term ends.

DPLYMAC provides the Cloud Mac physical node and related management capabilities described in the order confirmation. Final task duration, connection experience, build success rate, and release results may be affected by user configuration, local networks, cross-border network routes, code repositories, dependency sources, third-party services, and the project itself.

Users should test with real repositories, dependencies, and target workflows rather than infer the results of all tasks from a single latency measurement, build, or generic example. Failures caused by user scripts, permission settings, software versions, licenses, data quality, or changes to third-party systems do not indicate a mismatch between the device configuration and the order record.

To the extent permitted by applicable rules, neither party is liable beyond what the law requires for events reasonably outside its control, including major routing anomalies, interruptions to basic communications, third-party platform failures, natural disasters, public infrastructure incidents, and other force majeure events.

When raising an issue, users should provide enough information to distinguish device, network, third-party dependency, and project-configuration factors. The parties should prioritize verifiable measures proportionate to the actual impact, avoid aggravating the loss, and retain necessary order and troubleshooting records.

If a user seriously violates the acceptable use rules, threatens service security, infringes third-party rights, submits a fraudulent order, or refuses necessary security verification, DPLYMAC may restrict, suspend, or terminate the service based on the risk and may retain related records for security, accounting, and necessary obligations.

When users voluntarily stop using the service, they remain responsible for payment, data export, credential revocation, and environment cleanup associated with confirmed orders. Termination does not affect obligations incurred before termination or provisions concerning intellectual property, security, and dispute resolution.

These Terms may be updated when service procedures, ordering capabilities, or applicable requirements change. Material changes will be visibly notified on the website or in the dashboard, and the updated Terms will apply from the stated effective date. Continuing to order or use the service means accepting the Terms then in effect.

These Terms are governed by the laws of the jurisdiction where the platform operator is established. After a dispute arises, the parties should first communicate using order records, ticket materials, and verifiable facts. If negotiation fails, either party may seek resolution from a court with jurisdiction in that jurisdiction.

For questions about these Terms, orders, or support procedures, email support@deploymac.comor sign in to the dashboard to submit a ticket. Include the order reference and issue category, and remove passwords, private keys, certificate passphrases, and other sensitive credentials before submitting.