01 Service description
XcodeVNC provides remote access to Mac computers in the cloud. Each delivered instance is a dedicated physical Mac mini assigned to your order, not a virtual machine sharing compute resources with other orders. You can use the macOS graphical interface, screen sharing, VNC and SSH with the connection details provided for your instance.
Available locations are Singapore, Tokyo, Seoul, Hong Kong and the US East Coast. Both XV Desk M4 and XV Studio M4 are available in these locations. Check the dashboard for current availability when placing your order. Network latency depends on your location, routing and local network; we do not guarantee a fixed latency.
You are renting the right to use the device remotely for the agreed term, not ownership of the device. Screen sharing and VNC use the desktop resources of the same physical machine. For collaborative work, you are responsible for managing account permissions and scheduling concurrent sessions.
02 Accounts and setup
Before ordering, create an account with an email address that can receive service notifications. In the dashboard, select a model, location, billing period and any add-ons you need. Before paying, review the configuration, price and service term shown on the order page. Your order is based on the details submitted and paid for.
Once payment is confirmed, the system assigns a physical machine and initializes macOS. Setup usually takes about 4 minutes; this is an estimate, and the dashboard shows the actual progress. Once setup is complete, your connection address, SSH port and initial credentials will be available in the signed-in dashboard.
Keep your login details and instance credentials secure, change the initial password after your first connection, and take responsibility for orders and instance actions made through your account. If you notice an unfamiliar login or cannot access your delivery details, sign in to the dashboard to submit a support ticket or email support@xcodevnc.com.
03 Billing and payment
Services are prepaid by the day, week, month or quarter. The selected billing period applies separately to the model, storage upgrades and add-ons such as Thunderbolt 5 daisy-chaining. Before you pay, the order page lists each charge, the total and the selected period. Unless an order explicitly says otherwise, a price for one period should not be used to calculate the price for another.
All prices and payments are in US dollars (USD). We accept USDT-TRC20 and Visa, Mastercard or Amex cards processed by Stripe. Available payment gateways are determined by the response from the dashboard interface. Card payments are handled by the payment provider, and payment confirmations and billing records are available in the dashboard.
Before paying, check the receiving network, amount and order reference. An incorrect transfer network or order reference may prevent a payment from being matched automatically. If this happens, keep your transaction record and contact our team through a dashboard support ticket.
04 Renewals, expiry and release
Check the relevant order in the dashboard for an instance’s start and end dates, renewal price and next billing period. We send expiry reminders based on your account settings. These reminders are a courtesy; you are still responsible for checking the expiry date and renewing on time if you want to continue using the service.
If an order expires without renewal, access to the instance may stop. If a grace period applies, its duration and procedures are set out in the order terms shown in the dashboard. A grace period is not an additional free rental period. Before your service term ends, export any projects, build artifacts, certificates and other data you need to keep.
After an instance is finally released, the device enters a cleanup and reassignment process. Data on its disks will be erased and cannot be restored as a backup. You can check the status of renewals, releases and data handling in the dashboard. If you have questions about an expiry date, submit a support ticket before the instance is released.
05 Refunds
If you pay for an order but the instance has not yet been delivered, you can request cancellation and a refund of the service fees paid for that order. Submit your request through a dashboard support ticket and include the order number and payment record so we can verify the delivery status and original payment method.
After an instance has been delivered, early termination requests are handled according to the billing-period terms shown when you ordered, the service actually provided and applicable law. Unused calendar days do not automatically determine the refund amount. Before ordering, make sure the selected billing period suits your expected usage.
If you dispute a duplicate payment or a charge that differs from the confirmed order, provide the relevant order and transaction records. Once we have reviewed them, we will explain the outcome and refund route in the support ticket.
06 Availability
Our physical locations operate year-round. We commit to monthly service availability of at least 99.9%. Monthly availability is calculated as the time the service was available during a calendar month divided by the time it was due to be provided. This measures whether the service supporting a delivered instance was accessible; it does not measure your local network’s frame rate or the latency of an individual connection.
If verified monthly availability falls below 99.9%, we will extend the relevant instance’s service term by 10 times the confirmed downtime. Submit a request through a dashboard support ticket within 30 days after the affected month ends. Include the instance, affected time period and symptoms; we will review service records to confirm the downtime.
Issues caused by events beyond reasonable control, shutdowns or configuration changes made by you, problems with your local network or devices, incorrect credentials, or use that does not comply with these terms are not counted as platform downtime. If you disagree with the calculation, add connection logs and timestamps to the original ticket.
07 Acceptable use
You may use the instance for lawful development, builds, testing, remote demonstrations and compute tasks. You must ensure that data you upload, software you run and communications you send comply with applicable laws and third-party rights. If you use a self-hosted runner or automated tasks, you are responsible for managing secrets, access permissions and task logs.
You must not use an instance for mining, bulk or unsolicited email, unauthorized attacks or scans, distributing infringing content, bypassing security controls, or any other activity that harms the physical location, network or third-party rights. Do not publicly share connection credentials or use an instance to circumvent order or access restrictions.
If we identify activity that could put the service or a third party at risk, we may first restrict the relevant activity and notify you through your account. We may then take further action based on the conduct and its impact. You can explain the situation and request a review through a dashboard support ticket.
08 Software and licences
Use of macOS and Apple software is subject to the applicable software licence terms. This service provides a remote physical device and its available software environment; it does not transfer ownership of any software or grant rights beyond those permitted by the relevant licence.
You are responsible for obtaining and managing developer programmes, signing certificates, third-party tools and project dependencies as needed for your work. Before placing certificates or keys on a remote device, confirm that your team is authorized to use them. Remove sensitive materials you no longer need when your work is complete.
Before changing Xcode, command-line tools or other parts of the development environment, assess the impact on your existing build process and keep a recoverable copy of your project. You are responsible for software you install, configuration changes you make and any resulting data.
09 Liability and remedies
We provide remote access as agreed in your order and handle verified delivery, billing and availability issues under these terms. If something goes wrong, submit a support ticket promptly with the instance ID, time of the incident and steps to reproduce the issue. This information helps us assess the impact and restore access as quickly as possible.
You are responsible for keeping separate backups of project source files, certificates and build artifacts, and for exporting them before an instance is released at expiry. Both parties should take reasonable steps to limit losses that have already occurred. Requests for an extension due to service availability are handled under the calculation and process in Section 6.
Except where mandatory provisions of applicable law require otherwise, each party’s liability for a specific dispute will be determined in light of the order, actual impact, each party’s conduct and the records available. Nothing in this section limits any mandatory rights granted by law to consumers or other rights holders.
10 Changes, governing law and contact
If we change the service or its terms, we will publish the updated terms and their effective date. We will notify you through your account of any change that materially affects an order already in force. You can review the version then in effect before renewing or placing a new order.
The laws of the jurisdiction in which the platform operator is established govern the formation, performance and interpretation of these terms. If a dispute arises, the parties should first try to resolve it by referring to the order and support ticket records. If they cannot reach an agreement, the dispute will be submitted to a court with jurisdiction in that jurisdiction.
For questions about these terms, an order or the service, sign in to the dashboard and submit a support ticket, or email support@xcodevnc.com. Include your order number and a brief description of the issue. Do not send instance passwords or full payment credentials in ordinary email.