Service Definitions
OwnAMac provides Cloud Macs that can be accessed remotely over the internet. Each confirmed and active order corresponds to one dedicated physical machine and the physical location selected by the user. The compute, memory, and baseline storage resources assigned to that order are dedicated to it and are not shared with other tenants.
The service delivers Apple Silicon physical nodes, not virtual machines. Users may use the macOS graphical interface and command line for lawful development, builds, automation, model inference, audio and video processing, and other legitimate tasks. The specific OS version, available software, and access methods are determined by the order confirmation and the capabilities currently available in the console.
“Service term” means the daily, weekly, monthly, or quarterly rental period confirmed in an order; “location” means the data-center location hosting the dedicated physical machine; “credentials” means the authentication information required for remote access and management provided by the platform; and “add-ons” means separately selected storage or Thunderbolt 5 parallel-connection capacity beyond the base configuration.
Accounts and Eligibility
Users must have the legal capacity required to enter into and perform these terms and must provide truthful, accurate, complete, and reachable information. When a team or organization uses the service, anyone placing orders or managing nodes must have appropriate authorization and must ensure that all actual users follow these terms.
Users are responsible for protecting login credentials, remote-access credentials, keys, and locally stored connection settings. Credentials must not be transferred, sold, or disclosed to anyone who is not authorized to use the order. If credentials may have been exposed, an account shows unusual activity, or node access records do not match expectations, users must immediately change available credentials and submit a ticket through the console.
Configuration selections, order confirmations, node actions, ticket submissions, and data processing initiated from an account are generally treated as actions authorized by that account. Users are responsible for consequences resulting from voluntarily sharing credentials, using weak passwords, ignoring security warnings, or failing to promptly revoke access for departing team members.
Configurations and Locations
Orders are limited to the following three configurations currently on sale. The chip, memory, and storage capacity of a base configuration are determined by the selected tier; additional storage does not change the base configuration label or create a new model tier.
| Model | Chip | Memory | Base Storage |
|---|---|---|---|
| OAM M4 16 | M4 | 16GB | 256GB |
| OAM M4 24 | M4 | 24GB | 512GB |
| OAM M4P 64 | M4 Pro | 64GB | 2TB |
The five available locations are Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the Western United States. All three models can be ordered in each location, subject to real-time availability shown in the console. Users should choose a location based on where their primary users are, where task data travels, and network round-trip performance.
After an order is confirmed, changing the location or base model is not treated as an automatic modification of the original order. Whether a change is possible, requires reinitialization, or incurs a new charge depends on the operations available in the console and the order confirmation.
Billing Periods
Service is available by the day, week, month, or quarter. The applicable fee is the USD amount shown on theplans pageand on the order confirmation page displayed before the user submits the order. The order confirmation calculates the total due from the selected model, location, period, storage add-ons, and number of Thunderbolt 5 parallel connections.
Each period begins when the order is confirmed and enters the delivery process, and ends at the time shown in the order record. Each period is an independent billing option. Unless the console explicitly provides a change option, a started short-term period is not automatically credited toward another period.
Users should verify the model, location, period, and add-ons before confirming payment. After payment, any requested adjustment due to an incorrectly selected location, configuration, or period will be assessed based on whether the node has been initialized, whether service has started, and the order record.
- Base fee
- The fee for the selected OAM model during the applicable rental period.
- Additional fees
- The fee for the selected +1TB SSD, +2TB SSD, or Thunderbolt 5 parallel connections.
- Order total
- The USD amount equal to the base fee plus selected add-ons, based on the information shown before payment confirmation.
Payment Methods
OwnAMac supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All prices, billing, and order records are denominated and settled in USD. Actual gateway availability is determined by the backend response returned during checkout.
When using USDT-TRC20, users must verify the network, recipient details, transfer amount, and order identifier. If an order cannot be confirmed because of an incorrect network, address, or insufficient payment, the platform may request the transaction ID to verify the order status.
When using Visa / Mastercard / Amex, payment authentication and card processing are handled by Stripe. OwnAMac processes only the information needed to complete the order, verify payment status, and maintain required financial records. Users are not required to send complete card details by email or ticket.
An order will not enter physical-node initialization until its payment status is confirmed. For duplicate payments, mismatched amounts, or abnormal order status, users should retain the order number, payment time, amount, and necessary transaction identifier, then submit a ticket through the console.
Delivery and Use
After payment is confirmed, the platform processes the selected physical-node resource lock, system initialization, and credential delivery in sequence. The normal process takes approximately 4 minutes in total; network confirmation, payment-status responses, the selected configuration, and initialization tasks may affect the actual completion time. Delivery status and credentials are as shown in the console.
After receiving credentials, users should first verify that they can establish a remote connection, that the desktop resolution and keyboard layout meet expectations, and that a deliberate disconnect-and-reconnect test succeeds. If connection fails, credentials appear abnormal, or system status does not match the order, stop repeating actions that could alter the environment, record the time and error details, and submit a ticket.
Users may use the node for software development, Xcode builds, CI/CD, automated testing, model inference, audio and video workflows, and other normal computing tasks, provided the use is lawful, authorized, and does not affect the platform or other users. Users must not use the service for any of the following:
- Activities that violate applicable laws or regulatory requirements or infringe another party’s lawful rights;
- Unauthorized access to, scanning, probing, control of, or interference with any system, account, network, or data;
- Distributing malware, ransomware, credential-stealing tools, or software intended to damage system availability;
- Abusing network, storage, compute, or add-on-device resources through sustained abnormal traffic, malicious task queues, or other means;
- Evading security controls, concealing attack sources, interfering with logging, or preventing the platform from investigating security incidents;
- Reselling node access to a third party without authorization or bypassing order authorization limits by sharing credentials.
To protect the platform, nodes, and other users, OwnAMac may take necessary measures such as restricting connections, isolating tasks, or suspending access in response to clearly abnormal traffic, signs of unauthorized access, or malicious-program activity. OwnAMac will communicate handling requirements through the contact details associated with the order or through the console.
Renewal, Cancellation, and Termination
Daily, weekly, monthly, and quarterly periods are governed by the start and end times in the order record. Users should review renewal conditions in the console and confirm them before the current period ends. Service is not presumed to have renewed without user confirmation or a clear indication in the order record.
When the current period ends without a completed renewal, remote access may be stopped and the node will enter order-closure processing. Users should export code, build artifacts, logs, media, and other data they need to retain before the deadline. The timing and method of data processing after service ends are governed by the order confirmation and console notices.
If a user requests cancellation during the service term, charges for physical-node occupation, initialization, and add-on-device configuration already started are not automatically prorated based on unused time. The available cancellation method, service end time, and related outcome are determined by the order status and the parties’ confirmed records.
In cases including serious or continuing violations of these terms, refusal to stop unauthorized access, distribution of malicious code, fraudulent payment, threats to platform security, or circumvention of restrictions, OwnAMac may suspend or terminate the relevant account and node. Where circumstances permit, the platform will explain the violation and required corrective steps; where there is an urgent security risk, access may be restricted first while an investigation proceeds.
Termination does not affect payment obligations incurred before termination, confidentiality obligations, data-processing requirements, or liability provisions that must remain effective by law. Users who need available order records should submit a ticket through the console while their account remains accessible.
Liability and Disputes
OwnAMac is responsible for providing the selected dedicated physical machine, physical node, and necessary remote-access capability in accordance with a valid order. Nodes operate normally 365 days a year. Service experience may still be affected by the user’s local network, cross-region network paths, client configuration, third-party software, project dependencies, user actions, and events beyond reasonable control.
Users should maintain independent copies of business-critical data and confirm a recovery plan before performing system upgrades, disk changes, bulk deletion, build-environment resets, or other high-impact operations. Users are responsible for losses caused by their instructions, installed software, project scripts, poor credential management, or actions by unauthorized team members.
Licensing, compatibility, update schedules, and feature changes for third-party software are determined by the applicable rights holders. OwnAMac provides physical nodes and a remote-access environment and does not guarantee ongoing compatibility with any third-party software, a particular build result, or any business outcome.
For connection, order, or runtime issues, users should first submit a ticket through the console and provide the order number, location, time of occurrence, reproduction steps, error details, and necessary logs. If the console cannot be accessed, email support@ownamac.com. This address is also the sole external contact address for business, compliance, and security matters.
OwnAMac may update these terms as needed for service capabilities, compliance requirements, and risk management. Material changes will be visibly notified on the website or in the console with their effective date. Updated terms do not retroactively change order records completed before the update, except where required by law or expressly agreed by both parties.
The formation, interpretation, performance, and dispute resolution of these terms are governed by the laws of the jurisdiction where the platform operator is based. The parties should first attempt to resolve disputes in good faith through support channels. If consultation does not resolve the dispute, either party may bring proceedings before a court with jurisdiction in that jurisdiction.
Include verifiable information when submitting
For issues involving a specific order, provide the order number, selected model, location, rental period, time the issue occurred, and desired outcome. Do not send passwords, private keys, or recovery codes.