BookaMac Terms of Service

Acceptance and contracting parties

By visiting this website, placing an order, completing payment, or using BookaMac services, you confirm that you have read and agree to be bound by these terms, the order confirmation page, and policies directly related to the service. If you disagree with any part, stop the relevant process before placing an order.

Eligibility to contract

You must have the legal capacity required to enter into and perform a contract. If you place an order for a company, team, or other organization, you confirm that you have sufficient authorization and can ensure the organization complies with these terms. The order contact must be authorized to receive delivery, security, billing, and termination notices.

Accurate information

Contact, usage, and payment information submitted with an order must be accurate, complete, and kept current. Update changed contact details promptly in the console. If invalid information prevents delivery of required notices, you remain responsible for checking the rental period, payment, and expiration arrangements against the order.

Service definition

BookaMac provides access to a Cloud Mac under each order. Every valid order corresponds to the dedicated physical Mac mini confirmed in that order: a physical node, not a virtual machine. The service includes essential connection details, basic delivery instructions, and support related to node access and basic operation.

Scope of the order

The service is limited to the model, chip, memory, storage, region, rental period, and add-ons confirmed in the order. Software, development dependencies, repository contents, build settings, automation scripts, and third-party licenses installed or supplied by the user do not automatically become BookaMac delivery obligations.

Basic support boundaries

Basic support can help verify the delivered configuration, connection details, node reachability, and known operational issues. For user code, certificates, third-party tools, dependency conflicts, or business-system architecture, the support team may suggest troubleshooting directions but does not perform development, signing, release, or data-management work on the user's behalf.

Orders and delivery

After you select a configuration, region, rental period, and add-ons in the console and submit them, the system generates pending confirmation details. The order takes effect once payment is confirmed through the applicable process and the console shows that the order is active. A cart, unsubmitted configuration draft, or checkout record alone does not constitute an accepted order.

Delivery verification

After delivery, first verify the node region, device configuration, connection address, and initial access instructions. If the order record differs from the actual delivery, stop writing sensitive data and submit the order ID, discovery time, and discrepancy through a console support ticket for review.

Catalog and live availability

Available model-and-region combinations depend on the catalog offered at the time. Live availability is determined by the console. Both BookaMac M4 and BookaMac M4 Pro are available across four nodes: Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. Once confirmed, the order record controls the specific fulfillment.

Protecting delivery information

Connection addresses, usernames, temporary credentials, and key-related information are for authorized personnel on the order only. Do not place complete credentials in public repositories, public issue trackers, or collaboration spaces accessible to unrelated people. Redact logs and screenshots before requesting support.

Pricing and payment

All prices are displayed and settled in USD. The applicable price is the amount shown on the order confirmation at submission, including the selected model, billing period, region, storage upgrade, Thunderbolt 5 parallel connection option, and total due. Other pages help with comparison; the order confirmation determines the transaction amount.

Supported payment methods

BookaMac supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The available gateway, payment steps, and processing result are determined by the information returned at checkout. Verify the network type, payment amount, and order ID to avoid sending funds through an incompatible process.

Payment status

Initiating payment does not mean payment is complete. The order status is determined by confirmation through the relevant payment process and synchronization to the console. If the payment record remains unchanged for an extended period, keep the transaction ID, order ID, and time, then submit a support ticket through the console. Do not resend funds that could cause duplicate settlement.

Taxes and records

You are responsible for determining whether tax matters require action based on your location, entity type, and business use. Keep the order and payment records shown in the console and reconcile them with your internal purchasing, reimbursement, or accounting processes.

Renewals, expiration, and cancellation

Renewals must be completed during the period when the console permits the action and are subject to renewal-order confirmation and payment results. Check the current rental end time yourself; do not rely on a single notification when scheduling critical builds, releases, or data migrations.

Before expiration

Before the rental ends, migrate out code, build artifacts, logs, caches, certificates, provisioning profiles, and other data you need to retain. Revoke unneeded runners, access keys, and automation tasks. Do not treat post-expiration access or data recovery as a backup plan.

Cancellation rules

Cancellation requests, eligible cancellation stages, and processing methods are governed by the rules displayed and confirmed when the order was created. Submitting a cancellation request does not automatically reverse completed resource delivery, usage already incurred, or payments already being processed.

Refund processing

Refund eligibility, amount, method, and status are determined by the applicable order rules and review result. Approved refunds are processed through the original payment method where feasible. If additional verification is required, provide the necessary order and payment records, but never submit private keys or complete access credentials.

Permitted use

You may use a rented Cloud Mac for lawful development, builds, testing, automation, inference, transcoding, and rendering, provided you comply with applicable law, third-party licenses, and these terms, and ensure your activity does not harm the node, network, other users, or external systems.

Prohibited activities

• Attempting unauthorized access to other devices, accounts, networks, services, or data.
• Creating, deploying, or distributing malware intended to cause damage, extort, steal, conceal control, or bypass security measures.
• Conducting scans, attacks, fraud, traffic amplification, credential abuse, or other activity that disrupts the normal operation of external systems.
• Evading resource limits, connection limits, payment processes, or technical measures protecting the service.
• Infringing copyrights, trademarks, trade secrets, privacy rights, or other lawful rights.
• Using the node to store, process, or distribute content that violates applicable law.

To investigate clear signs of abuse, BookaMac may ask you to describe the workload, provide redacted logs, or stop related tasks. Access may be restricted if you do not cooperate within a reasonable time or if the risk requires immediate control.

User responsibilities

You are responsible for your account, access keys, code, certificates, provisioning profiles, data, third-party licenses, backups, and workload compliance. The ordering party remains responsible for ensuring that actions performed by team members, contractors, or automated systems comply with these terms.

Access and permissions

Use separate SSH keys, least-privilege accounts, and auditable team authorization. Remove access for people who leave the project promptly. Long-term sharing of administrator credentials weakens auditability, so create distinct access paths for different roles.

Code and signing materials

Manage repositories, certificates, provisioning profiles, environment variables, and release keys according to your own security procedures. BookaMac does not manage your software release identity or determine whether third-party licenses cover a particular build, test, or distribution activity.

Backups and change records

Keep critical repositories, build artifacts, and configuration in an independent backup location, and record Xcode selections, dependency versions, runner labels, network rules, and environment changes. Before deleting files, overwriting configuration, or running irreversible commands, confirm the scope of impact and recovery path.

Availability and recovery

BookaMac operates all nodes for normal service availability 365 days a year. Access may still be affected by upstream network issues, hardware failures, regional infrastructure events, your own configuration, attack traffic, or other events beyond reasonable control.

Status communication

After identifying an issue affecting node delivery or connectivity, BookaMac will use the information available to confirm the scope, limit further impact, and work toward recovery. Status updates will distinguish confirmed facts, items still under investigation, and checks you can perform immediately, avoiding speculation presented as fact.

User-side checks

When reporting a connection issue, provide the order ID, node region, time of occurrence, connection method, and redacted logs. First check your local network, SSH host fingerprint, VNC client settings, and recent firewall changes. Do not send private keys or complete credentials in a support ticket.

Reasonable recovery

Recovery may include correcting network paths, restarting affected services, replacing failed components, reissuing necessary connection information, or taking other measures proportionate to the incident. The order of actions is based on reducing data risk, restoring reachability, and confirming node status.

Limitation of liability and indemnification

To the extent permitted by applicable law, each party is responsible for direct losses caused by its own breach of these terms, intentional conduct, or negligence. Liability is assessed in light of foreseeability, actual causation, mitigation measures taken by both parties, and the applicable order terms.

Indirect losses

To the extent permitted by applicable law, BookaMac is not liable for lost profits, lost opportunities, loss of goodwill, reduced anticipated savings, or other indirect losses where limitation is permitted and the loss is not the direct result ordinarily reasonably foreseeable from the breach. You should maintain independent backups and alternative processes for critical releases, builds, and data processing.

Third-party services and user content

Third-party software, code repositories, dependency sources, signing tools, network services, and systems deployed by you are controlled by their respective providers or by you. BookaMac delivers and provides basic support for the physical node within the order scope, but does not assume control of third-party licensing, availability, output accuracy, or the legality of user content.

User indemnification

If a third party makes a valid claim against BookaMac because of your content, unlawful use, infringement of third-party rights, license violations, or unauthorized actions, you are responsible to the extent permitted by applicable law and must cooperate by providing necessary facts, preserving evidence, and limiting further impact.

Changes, termination, and disputes

BookaMac may update these terms to reflect service processes, legal requirements, or risk controls. Material changes to your rights or obligations will be reasonably notified through the website, console, or order contact details. Updated terms apply from their stated effective time.

Termination and access restrictions

If you seriously violate permitted-use rules, refuse to address a clear risk, fail to complete payment under an order, or continue harming nodes or external systems, BookaMac may restrict access or terminate the affected service based on the level of risk. Whether time to remedy is provided depends on the urgency, scope, and reversibility of the incident.

Surviving terms

After an order ends, provisions concerning payment records, intellectual property, confidentiality, allocation of liability, indemnification, dispute handling, and any other provisions that by their nature should survive remain effective. You must still complete data migration, revoke access, and retain necessary records.

Governing rules and dispute resolution

These terms are governed by the laws of the jurisdiction where the platform operator is based. In a dispute, the parties should first negotiate based on order records, communications, and verifiable facts. If negotiation fails, either party may bring proceedings in a court with jurisdiction in that jurisdiction.

Contact

For questions about existing orders, node connectivity, or payment status, log in andsubmit a support ticket in the console. For general questions about these terms, security reports, or partnerships, email support@bookamac.com. Submit only the information needed to handle the issue; do not send private keys or complete credentials.