This policy covers the MacMLab main website, console, Cloud Mac order delivery, and related support communications. We process only the data needed for specific business purposes and arrange deletion when the purpose is complete, the retention basis ends, or a valid deletion request is approved.
The determining factor is not the page name, but whether data enters MacMLab service workflows to access the website, manage an account, complete an order, deliver a physical node, or handle support matters.
This policy applies to data processing arising from visits to macminilab.com, console registration or login, configuration and management of Cloud Mac orders, billing status checks, support ticket submissions, and communications with us through support@macminilab.com.
A Cloud Mac is a dedicated physical machine delivered for a rental term. Each active rental maps to one physical node and is not a virtual machine service. To allocate nodes, manage connections, investigate faults, and conduct security audits, we process necessary records related to orders, nodes, and connection events.
Providing a physical node does not mean we may freely access your source code, models, build artifacts, certificates, or private keys. You manage business files within your rented environment. We process such content only when you voluntarily submit it for technical troubleshooting or when legally required security action is necessary, and only for a defined purpose and to the necessary extent.
Third-party development tools, code repositories, continuous integration platforms, and payment processing chains process data under their respective service relationships. This policy describes MacMLab’s responsibilities and does not alter the independent responsibilities of third parties.
Each data type enters the processing path corresponding to its purpose. If a business action has not occurred, simply viewing a public page does not require you to provide order or ticket information.
Includes the email address, account identifier, verification status, and security-setting records used for registration, login, identity verification, and service notifications. Passwords are handled in a protected verification form and are not collected in support ticket content.
Includes the selected MacMLab M4 16 or MacMLab M4 24, rental term, node region, SSD add-ons, number of Thunderbolt 5 interconnects, order status, and delivery-related information.
Includes settlement currency, amount due, payment method category, transaction status, reconciliation identifier, and necessary risk assessment results. Full card details must not appear in support emails or ticket content.
Includes physical node identifier, region, connection time, session events, network source information, error codes, and security event summaries for delivery verification, access control, and troubleshooting.
Includes order number, node region, time of occurrence, symptoms, reproduction steps, redacted logs, handling records, and status updates. Do not submit passwords, private keys, or signing credentials in tickets.
Includes page visits, referring pages, browser and device category, basic network information, and interaction events for security protection, page availability analysis, and service improvement.
When data comes from an enterprise account administrator, team purchasing lead, or authorized project contact, we record its source and purpose in relation to the order. Before providing someone else’s information, confirm that you have the necessary authorization and submit only what is needed for the current matter.
We primarily process data to provide services, protect accounts and nodes, respond to requests, and meet applicable obligations. Technical logs are not repurposed without defined limits.
Create and verify accounts, maintain login security, process password-change requests, and send notifications directly related to account status.
Confirm the model, term, region, and add-ons; verify payment status; and establish the delivery relationship between the order and physical node.
Allocate nodes in Singapore, Tokyo, Seoul, or Hong Kong, generate necessary connection information, and display service status in the console.
Identify unusual logins, unauthorized access, malicious activity, and resource abuse, while retaining enough timeline information to review security incidents.
Relate connection events, node status, and handling records to the symptoms, error information, and redacted logs submitted by the user.
Aggregate page availability, error types, and support issue categories to improve documentation, console workflows, and delivery checks.
Complete accounting records, security responses, rights-request verification, and legally binding procedures under applicable requirements.
If we propose using data for a new purpose that materially differs from the original purpose, we first assess necessity, compatibility, and the applicable basis. Where additional notice or consent is required, we complete the relevant steps before processing.
MacMLab supports USDT-TRC20 and Visa / Mastercard / Amex (via Stripe) only. All orders are settled in US dollars (USD); the gateway available in practice is shown in the console.
To identify payments and reconcile accounts, we may process the order amount, receipt status, transaction identifier, confirmation status, and information needed to match the payment to the order. Transaction records on a public ledger are governed by the relevant network and cannot be unilaterally removed like ordinary site records.
Card payments are processed through Stripe. MacMLab receives the payment result, transaction identifier, risk status, and necessary billing summary required to fulfill the order. We do not ask users to send full card numbers or security codes by email or ticket.
Payment processors handle necessary information according to their roles in the transaction. MacMLab uses payment results for order confirmation, refund reconciliation, dispute handling, accounting records, and security audits, and does not use payment credentials to verify remote connections to Cloud Mac.
Provide the order number, payment method category, amount, time of occurrence, and a transaction identifier suitable for reconciliation. Redact full card numbers, private keys, verification codes, and other sensitive fields not needed for review.
Retention periods are determined jointly by order fulfillment, security review, dispute handling, user requests, and applicable recordkeeping obligations. We do not assign one deletion cycle to all data.
| Record category | Primary retention basis | Handling after expiry | Deletion request considerations |
|---|---|---|---|
| Account information | Maintaining the account, identity verification, and security controls | Deleted or de-identified after account closure and the necessary verification period | Verify the requester’s relationship with the account first |
| Order and billing records | Order fulfillment, reconciliation, dispute handling, and applicable recordkeeping obligations | Cleared by record category after the retention basis ends | Some fields may need to be retained until the relevant obligation is complete |
| Connection and security logs | Access control, anomaly investigation, and node event review | Rotationally cleared or aggregated after no longer needed for security review | Records of incidents under investigation may be temporarily retained |
| Support tickets | Resolving issues, preserving handling context, and recording verification results | Cleared after the matter ends and no further review is needed | Unnecessary attachments or sensitive excerpts may be deleted first |
| Site access records | Security protection, error analysis, and experience improvement | Aggregated by purpose, shortened to reduce identifiability, or deleted | Provide enough access information to locate the record |
| Legally required records | Record-retention requirements applicable to the operating entity | Handled through the established deletion process after the obligation ends | Legal retention requirements may restrict immediate deletion |
Email support@macminilab.com or sign in to the console to submit a ticket. Specify the data category to be deleted, the relevant order or ticket number, and information that helps verify your relationship with the account. Do not send passwords, private keys, or signing credentials.
After receiving a request, we first confirm its scope and the identity relationship, then check whether the data is still needed for an active order, security incident, dispute, or applicable recordkeeping obligation. Deletable content enters the deletion process; content that cannot yet be deleted will be accompanied by its category, the reason for the restriction, and the conditions for later handling.
Data in backups or disaster-recovery copies may exit through the established rotation process rather than being rewritten item by item at the same time as the primary record is deleted. During this period, the copies are used only for recovery and integrity protection and are not returned to routine business use.
MacMLab is responsible for service-side access controls, node delivery records, and necessary security audits. Users are responsible for their own credentials, business data, and permission settings in development workflows.
If you detect unusual account activity, possible credential exposure, or unauthorized activity on a node, immediately stop sharing the relevant credentials, preserve the time and error information, and contact support through a console ticket or support@macminilab.com. To help us investigate, provide the order number, node region, symptoms, timeline, and a summary of redacted logs.
Cloud Mac nodes, team members, support personnel, and payment processors may be located in different regions. International processing is limited to defined purposes such as delivery, support, security, and settlement.
When a user selects a physical node in Singapore, Tokyo, Seoul, or Hong Kong, or when teams in different locations jointly manage an order, necessary delivery and connection information may be transferred between the relevant regions. We apply controls based on the data category, processing purpose, access permissions, and applicable requirements, without expanding routine access to business files because of the node location.
Confirm whether we process data associated with your account and obtain records or copies that may legally be provided.
Correct inaccurate or incomplete account, order contact, and support communication information.
Request deletion of data that no longer has a processing basis and learn which record categories cannot yet be deleted.
Request restriction of or object to specific processing, identifying the relevant account, order, and reasons.
Where applicable, obtain data you provided directly or that is directly associated with your account in a practicable format.
Request a review of how your request was handled or provide feedback through channels available under applicable rules.
State the request type, data categories involved, and relevant order or ticket number.
We use necessary information to confirm the requester’s relationship with the account or order and prevent mistaken disclosure or deletion.
Check whether active orders, security incidents, dispute handling, or applicable recordkeeping obligations affect the request scope.
Update the status through the original request channel and explain completed actions, restricted categories, or information still needed.
We update this policy’s version and effective date when the service scope, processing activities, or applicable requirements change. Changes that materially affect user rights or data use will be communicated through appropriate on-site or account contact channels.
This policy and disputes concerning related data processing are governed by the laws of the jurisdiction where the platform’s operating entity is located. Disputes that cannot be resolved through communication may be submitted to a court with jurisdiction in that jurisdiction.
Privacy access, correction, deletion, objection, security reports, compliance document requests, and reviews of processing results may all be sent to support@macminilab.com. Signed-in users may also submit a ticket in the console.
Specify the request type, relevant order or ticket number, and the necessary information for verifying your relationship with the account. Do not submit passwords, private keys, or signing credentials.