How Cloud Mac data is handled

Scope of this policy

This policy applies to the armmacs.com website, order management portal, allocation and delivery of Cloud Mac dedicated physical nodes, email exchanges initiated through the contact page, and support tickets submitted through the console. It covers visitors, users requesting quotes, customers placing orders, current renters and authorized team members operating orders on behalf of an organization.

Public website content can be browsed without creating an order. When you enter the ordering process, complete payment, receive connection credentials or submit a ticket, we process the information required for that task. Different workflows require different information; simply browsing public pages does not automatically require complete order details.

Cloud Mac runs on dedicated physical machines, not virtual machines. Users directly control the data they create or import through the system interface, command line, development toolchain and working directories. This policy also describes the limited operational information the platform may access to deliver physical nodes, secure access and troubleshoot incidents.

Information we collect

We collect information based on the features you use. Not every user record contains every category listed below.

When a user acts on behalf of a team, we may also process their role, order ownership and necessary internal authorization details. We do not require identity materials unrelated to an ordinary inquiry, and support records should not retain sensitive credentials that are unnecessary to resolve an issue.

How we use information

Data processing is tied to specific tasks. The primary purposes and required information are as follows:

The same record may support related purposes. For example, an order number may confirm node delivery and link a later ticket to the correct model. If we plan to use information for a purpose materially different from the original purpose, we will provide required notice or take appropriate authorization steps.

Payment information and USD billing

All orders are billed in USD. The only available payment methods are USDT-TRC20 and Visa / Mastercard / Amex processed through Stripe. The payment gateway and order status available at checkout are determined by the results returned by the backend.

Billing records support payment confirmation, order delivery, renewal verification, dispute handling, audits and legal obligations. Payment records may be retained longer than ordinary inquiry records because financial and transaction verification generally requires a traceable order history.

Data responsibilities on Cloud Mac

Users are responsible for managing the code, certificates, keys, models, datasets, dependency caches, build logs and build artifacts they place on Cloud Mac. Based on project requirements, decide what data may enter the selected node and complete any necessary access review, encryption or redaction before importing it.

During the rental period

• Import only the repositories, models, certificates and environment variables required for the current task, and avoid copying unrelated production data.
• Use separate, revocable, least-privilege credentials for CI/CD Runners, code repositories and object storage.
• Keep critical code and build artifacts in an independent version control system or external backup; do not use a single physical node as the only copy.
• Record when credentials were created, their scope of use and revocation plan. Remove tokens and private fields from troubleshooting logs before submission.

Before the rental period ends

1. 01

   Export source code, models, test results, logs and build artifacts, then verify that the files can be read from another location.

2. 02

   Stop Runners and automated tasks, and remove repository remote credentials, environment variables, certificate copies and temporary keys.

3. 03

   Clean sensitive content that may remain in working directories, download folders, caches and command history.

4. 04

   Revoke access tokens created for the node and check your pipelines to ensure later tasks are not still sent to the expired node.

Expiration handling, node reclamation and access availability are governed by the order details. Reserve time to export your data during the rental period instead of waiting until the final build task ends.

Data sharing and service processors

We use service processors only as needed for delivery, payments, security, infrastructure operations and legal requirements. The data provided to each processor must match its assigned task; participation in one step does not grant access to all order or Cloud Mac work data.

Payment processing

Used to complete card payments, return transaction status, verify payment and handle necessary billing records.

Infrastructure and node operations

Used for network connectivity, physical node allocation, operational status checks, security protection and infrastructure operations required for delivery.

Email and support systems

Used to send account and order notifications, receive support requests, retain reply histories and track ticket status.

Professional and compliance support

When necessary for billing, audits, security investigations or legal requirements, limited records may be provided to processors responsible for the relevant function.

If we receive a legally valid information request, we will review its scope and process only the information legally required. Requests concerning user rights are handled under the laws of the jurisdiction where the platform operator is based.

Retention, access, correction and deletion

Retention periods are set according to the purpose of each data type rather than one fixed period for all records. We consider whether an order is still being fulfilled, financial record requirements, security investigations, whether a support issue is closed and applicable legal obligations.

Where applicable, you may request access to information relating to you, correction of inaccurate data, deletion of data that is no longer needed or restriction of specific processing. Requests may be sent to support@armmacs.com, or you may log in to the console to submit a ticket. To prevent unauthorized data actions, we may ask for your email, order number or other necessary information to verify the connection between the requester and the records.

Some information may not be deleted immediately because of order fulfillment, billing records, security investigations or legal obligations. In such cases, we will explain the scope of processing as required and carry out subsequent cleanup when the retention purpose ends.

Cross-region choices and security measures

ArmMacs currently offers nodes in Singapore, Tokyo, Seoul, Hong Kong and the western United States. Your node selection may affect where code, logs, models and build artifacts are actually processed. Choose a region based on project contracts, team policies and compliance requirements, and confirm whether the relevant data is suitable for the target node.

All nodes operate normally 365 days a year. Access to a physical node still depends on your local network, remote connection settings, credential status and real-time inventory in the selected region. Before choosing a region, also review repository location, team member locations, build artifact destinations and the remote desktop experience.

Users must also take security measures, including protecting login credentials, using separate keys, promptly revoking temporary tokens, limiting CI/CD Runner tag scope and avoiding sensitive environment variables in build logs.

Contact, policy updates and dispute handling

Privacy questions and requests for data access, correction or deletion may be sent to support@armmacs.com. If the issue concerns an existing order, node or active rental incident, log in to the console to submit a ticket and include the order number, node, time of occurrence and redacted details so the request can be linked to the correct record.

We may update this policy based on service workflows, the scope of data processing or applicable requirements. After an update, the effective date at the top of the page will change; significant changes to processing practices will be communicated through appropriate on-site or order notifications. Teams should review this policy again before adding nodes, changing data categories or expanding CI/CD use.

This policy and related privacy matters are governed by the laws of the jurisdiction where the platform operator is based. Disputes that cannot be resolved through support may be submitted to a court with jurisdiction in that jurisdiction.