Identify your request type first

Share the essential context once so your request reaches the right team faster

New rentals, migration assessments, bulk deployments, partnership, and compliance requests can be sent by email. For connection, build, storage, or billing issues on existing orders, log in to the console and submit a ticket first, including your order number.

Public email
support@setmini.com
Existing order
Console ticket with order number
Available regions
Singapore, Tokyo, Seoul, Hong Kong
REQUEST ROUTING Request routing
01
Rental & migration Model, region, term, toolchain
Email
02
Existing-order issue Order number, time, error output
Ticket
03
Bulk & partnerships Quantity, timeline, delivery scope
Email
04
Compliance & privacy Entity, purpose, required materials
Email
Catalog facts 2 models

SetMini M4 and SetMini M4 Pro are dedicated physical machines, not virtualized environments.

Routing essentials 5 key details

Order, region, time of occurrence, client environment, and reproducible steps.

Response path Email is handled by subject; tickets retain order context

Do not include sensitive credentials, private keys, complete certificates, or payment keys in emails or issue descriptions.

Structured contact email

Start with the facts that affect routing

This form does not submit data to the website backend. After you click Generate, the page formats the fields into an email subject and body and hands them to your device's mail app. You can edit the message before sending.

A01

Contact and request scope

Required fields first
Request type
Required for existing orders, billing, or region issues; leave blank for new rental inquiries.
Target region
Target model
Estimated rental term
Team size
Describe the current environment, completed steps, blocker, and desired conclusion. Minimum 20 characters.
Workflow requirements

Tell us where this Cloud Mac fits in your workflow

Your use case affects the recommended model, storage expansion, and troubleshooting order. Select at least one workflow, then add your macOS, Xcode, and automation tool versions.

Primary workflow

Response preparation checklist

Record technical issues in reproducible order

“Cannot connect” or “build failed” alone is usually not enough to locate the problem. The six items below help the team define the scope first, then decide whether to check the client, network, system environment, project dependencies, or order status.

01

Order and region

Include the order number and the actual region: Singapore, Tokyo, Seoul, or Hong Kong. Do not provide only your team's location.

02

Time of occurrence

Record the local date, time, and time zone when the issue occurred, and say whether it is persistent, intermittent, or happened only once.

03

Client environment

State the local operating system, connection method, network type, resolution, and whether other services are accessible on the same network.

04

Error output

Copy the key error lines, exit code, and failure stage. For long logs, remove sensitive values first while retaining the necessary context around the error.

05

Reproduction steps

Starting from a normal state, list the commands run, click path, input conditions, and actual result, and state the expected result.

06

What you have already tried

List actions such as reconnecting, clearing caches, switching Xcode versions, checking storage, or rerunning the task to avoid repeating ineffective steps.

Payment guidance

Confirm payment methods before discussing order configuration

All orders are billed in USD. We support USDT-TRC20 and Visa, Mastercard, and Amex processed through Stripe. Available gateways are confirmed during checkout.

Billing currency USD
Digital asset payment USDT-TRC20
Card payment Visa / Mastercard / Amex
Processing Via Stripe
Ready to buy

Start a new order directly from configuration

Choose SetMini M4 or SetMini M4 Pro, then select Singapore, Tokyo, Seoul, or Hong Kong, along with the rental term and add-ons.

Create a Cloud Mac
Connection troubleshooting

Narrow the scope in the recommended order

For connection drops, keyboard mapping, resolution, session reconnection, or build issues, review the usage support first, then submit a ticket with the results.

View usage support
Privacy request

First confirm the data-processing scope

For access, correction, deletion, or processing-restriction requests, state the account-related information, request scope, and necessary context for identity verification.

View privacy policy
Next step

Place an order when the configuration is clear; submit a ticket for existing-order issues

New rentals do not require manual confirmation of catalog details. For technical issues, include the order number, region, time of occurrence, and error output to reduce first-round questions.