Legal

Terms of Service

Before renting, understand how the machine is delivered, how the rental period is calculated, and what happens if service is interrupted or an order changes. These terms apply to MacFTP Cloud Mac rentals and related account services.

Version 1.0 The version displayed at confirmation applies to your order

Contents

  1. 1. Service Definition
  2. 2. Accounts & Setup
  3. 3. Billing & Payment
  4. 4. Renewals, Expiry & Data
  5. 5. Availability & Credits
  6. 6. Acceptable Use
  7. 7. Refunds
  8. 8. Liability & Risk
  9. 9. Changes & Disputes
Open Console

For order, payment, or service issues, log in and submit a support ticket.

Chapter 1: Service Definition

MacFTP provides dedicated Apple Silicon physical Mac rentals. During the rental period, the entire Mac mini assigned to an order is for that customer’s use. It runs macOS natively, not in a virtual machine, and its processor, unified memory, and local SSD are not shared with other customers. Dedicated hardware does not mean the internet connection or third-party software services are exclusive to you.

The catalog offers three configurations: FTP M4 Core with M4, 16GB unified memory, and 256GB SSD; FTP M4 Plus with M4, 24GB unified memory, and 512GB SSD; and FTP M4 Pro with M4 Pro, 64GB unified memory, and 2TB SSD. Service is available in Singapore, Tokyo, Seoul, and Hong Kong only. Configurations outside the catalog and custom builds are not offered.

Your order is defined by the model, location, rental period, and add-ons shown on the confirmation page. Catalog configurations are generally available to order; check the Console for real-time availability. Renting does not transfer ownership of the equipment and does not include software licenses, app store review, or third-party service fees unless listed in the order.

Chapter 2: Accounts & Setup

Create your account with an email address you control, either personally or on behalf of an organization you are authorized to represent. Provide accurate order details and keep your email available for service notifications. Anyone placing an order for a team must have the necessary authority. Account holders are responsible for safeguarding login details, machine passwords, SSH keys, and other credentials. Do not expose them in public repositories, public logs, or bulk emails.

Once you confirm a configuration in the Console and complete payment, the platform processes setup and delivery according to the order status. Check Console records separately for payment confirmation, service activation, and access credentials. Initiating a transfer or seeing a card charge does not mean the physical machine has been delivered. Setup times are not guaranteed in a fixed number of minutes; the rental period begins and ends as shown in the order delivery record.

When you receive your credentials, verify the model, location, storage, and connection details. Change the initial password promptly and configure keys as needed. If the configuration is incorrect, you cannot connect, or credentials appear compromised, keep the order number and error details and submit a support ticket through the Console. If an account or credential may have been compromised, stop sharing the affected information immediately and request assistance with the investigation.

Chapter 3: Billing & Payment

Service is prepaid by the day, week, month, or quarter, with the selected term charged in full. All prices and charges are in US dollars (USD). The confirmation page lists the base rental price, selected add-ons, and total due; review each item before paying. Rental charges are not based on CPU usage or time logged in. Once the machine has been delivered, shutting it down, leaving it idle, or stopping a build does not pause the rental period.

Payment is accepted via USDT-TRC20 or Visa, Mastercard, and Amex cards processed by Stripe. Actual availability depends on the payment gateway response. For USDT-TRC20, follow the network, address, and amount shown on the payment page, and keep the transaction hash. For card payments, complete any verification required by the payment processor. Network fees, card issuer fees, and exchange-rate handling are not included in the machine rental price.

Storage expansion and Thunderbolt 5 interconnect are separate add-ons and are included only if selected and confirmed in the order; the interconnect is charged per machine. Get a confirmed quote before changing a configuration or rental term. Upgrades covering the remainder of a rental period are calculated under the confirmed pro-rated terms. Do not underpay or apply charges from an existing order to a new order without confirmation.

Check payment and billing status in the Console. To request a receipt or have a charge reviewed, provide the order number, payment method, and any necessary transaction reference. Do not send full card numbers, card security codes, machine passwords, or private keys in a support ticket or email. If records do not match, both parties will verify them against the order, gateway confirmation, and delivery records.

Chapter 4: Renewals, Expiry & Data

If you need to keep using the same location, confirm your renewal and pay through the Console before the current rental period ends. A renewal is complete only when the order status and updated expiry time confirm it. An expression of intent, support ticket, or initiated payment does not replace a completed renewal. Confirmed renewals continue under the updated order.

If service expires without a completed renewal, the platform may end access to the machine and begin the equipment recovery process. Expiry reminders are supplemental; you are still responsible for checking the expiry time shown in the Console. Export your projects, certificates, build artifacts, and other necessary data during the rental period, and verify that your backups can be restored. Do not treat the machine as a backup after expiry.

Files created or uploaded to the machine remain the property of you or their lawful owners. After a rental ends, the platform clears the previous rental environment as part of the recovery process and wipes disk data before delivering the machine to another customer. No recoverable copy is guaranteed to be retained after expiry. To check the recovery status for a specific order, submit a support ticket; do not rely on an unconfirmed data-retention period.

Moving to another location, reinstalling the system, or changing models may require a new environment setup. Do not assume the original disk will be fully migrated. Before making changes, confirm their scope, cost, and data-handling arrangements. Unless separately confirmed, a standard rental does not include automatic backups, project migration, or application-level disaster recovery.

Chapter 5: Availability & Credits

All locations operate year-round, 365 days a year. MacFTP targets 99.9% monthly availability. This is a service target, not a guarantee for every build time, public internet route, or third-party platform. Availability reviews cover the physical machine service delivered by the platform. An application error or connection failure from a single device alone does not establish that an entire location was unavailable.

Monthly availability is calculated over measurable service time within the active rental scope for that month: availability = (total eligible service time − verified downtime) ÷ total eligible service time. Both parties will determine start and end times using connection records, platform service records, and the customer’s incident timeline. Overlapping incidents are counted only once. Downtime caused by customer actions, such as shutting down the machine, misconfiguration, or removing required components, and downtime caused by force majeure are not counted as platform-attributable downtime.

If verified availability for a month falls below 99.9%, eligible downtime is converted into service-time credits. To request a review, provide the order number, location, incident start and recovery times with time zone, error details, and troubleshooting steps already taken. Credits are based on verified service-time records, not assumed business revenue, build counts, or third-party losses.

The credit duration, applicable order, and activation method will be confirmed through a support ticket. Service-time credits and refunds are separate remedies; a service period that has already been refunded or credited cannot be counted again. If you disagree with an incident assessment, you may provide additional logs or reproduction steps and request a review.

Chapter 6: Acceptable Use

Use the service only for development, builds, testing, inference experiments, or remote work that you are authorized to perform. You are responsible for uploaded data, programs you run, and software licenses. Do not use the service for cryptocurrency mining, bulk unsolicited email, phishing or fraud, malware distribution, unauthorized scanning or attacks, infringing content, or other unlawful activity.

Do not attempt to access another customer’s machine, credentials, or data; bypass platform access controls; disrupt data center networks; or use abnormal traffic to affect other services. Dedicated physical hardware does not grant unlimited use of shared network resources. Before running tests that may generate substantial external traffic or involve third-party systems, obtain authorization and assess the potential impact.

If the platform identifies suspected abuse, a security incident, or a substantiated infringement complaint, it may take proportionate measures, including restricting relevant connections, suspending affected services, and preserving necessary records. Where appropriate, the account holder will be notified. You must cooperate by explaining the use case and providing authorization or remediation materials. Any lifting of restrictions and further action on the order will depend on the investigation findings.

Chapter 7: Refunds

To request a refund, the account holder who placed the order must submit a support ticket through the Console. Include the order number, payment reference, reason for the request, and whether the service has been delivered. The platform will assess the request based on payment confirmation, activation records, the rental period already used, and the findings of any investigation. Submitting a request does not mean a refund has been approved, and delivered orders are not guaranteed an unconditional refund.

For duplicate payments, verified overcharges, or cases where the platform cannot deliver the confirmed order, the platform will verify the refundable amount and how it will be processed. For a service that has already been delivered, requests due to a project ending early, no longer needing the machine, or customer configuration issues will be assessed individually. Unused rental time does not automatically become a withdrawable balance. Platform-related service outages are reviewed for credits under Chapter 5; any refund will be confirmed separately where applicable.

Approved refund amounts, payment routes, and processing status will be recorded in the support ticket and are subject to the original payment method’s requirements. Card refund timing depends on the payment processor and card issuer. For USDT-TRC20 refunds, the network and receiving address must be verified. Do not provide an address you are not authorized to control. The platform will never ask you to disclose a card security code or private key to receive a refund.

A payment will not be refunded more than once, and the same service period will not receive both a refund and service-time credits. If you disagree with a decision, add supporting evidence to the original ticket to request a review. Nothing in this chapter excludes or limits rights you may have under applicable law.

Chapter 8: Liability & Risk

The platform is responsible for delivering the physical machine service specified in the confirmed order, reasonably addressing service incidents, and protecting account and order information it handles while fulfilling the order. You are responsible for application-level configuration, software licenses, access permissions, and backing up your own data. Both parties should take reasonable steps to limit losses when an issue occurs and should not allow a known risk to worsen without taking action.

Build success, software compatibility, model inference results, third-party review outcomes, and business revenue depend on factors such as code, dependencies, configuration, and third-party services. They are not delivery metrics for the physical machine rental itself. If a third-party tool or public internet connection has an issue, both parties should first establish the cause and scope, then address it according to their respective responsibilities. Not every application issue is a hardware failure.

Liability will be assessed in accordance with applicable law, actual performance, causation, and verifiable losses. If force majeure prevents performance, the affected party should give timely notice where reasonably practicable and cooperate to mitigate the impact. The platform remains responsible for obligations that cannot be excluded or limited by law. Nothing in these terms is intended to broadly waive liability the platform has under applicable law.

Chapter 9: Changes & Disputes

The platform may update these terms to reflect changes to the service catalog, payment process, or fulfillment rules, and will publish the current version on this page. Changes affecting users’ principal rights or obligations will be communicated by appropriate means. The applicable terms for new orders and renewals will be shown before confirmation. Updating this page does not automatically add charges to confirmed orders or reduce agreed benefits retroactively.

For questions about orders, billing, service-time credits, or data handling, please log in to the Console and submit a support ticket first. You can also contact support@macftp.com. Include your order number and a factual description, and do not send passwords, private keys, or other sensitive information that is not needed for the review. The parties should first seek to resolve the matter through discussion based on the order and support ticket records.

These terms are governed by the laws of the jurisdiction where the platform operator is based. Any dispute that cannot be resolved through discussion will be submitted to a court with jurisdiction in that jurisdiction. Mandatory provisions of applicable law will apply where relevant. If any provision is held invalid or unenforceable, the remaining provisions that can operate independently will remain in effect.

Rent a Cloud Mac Log in to submit a ticket