1. Scope
This policy applies to data processing when you visit armcli.com, create or use an ArmCLI account, rent a cloud Mac dedicated physical machine, receive node delivery details, or communicate with our service team by email or console ticket.
Website processing covers page access, security protection, and necessary operational records. Console processing covers authentication, order configuration, rental management, node delivery, billing records, and ticket handling. Order delivery may also involve node identifiers, data center selection, credential issuance status, and service operation records.
This policy does not change your responsibility for managing your code, keys, business data, or self-installed tools. Upload only information required for your rental, troubleshooting, or support request, and remove passwords, private keys, access tokens, and other unnecessary sensitive content before submitting logs.
2. Data Collected
Account and contact information may include your name, email address, login verification status, account identifier, and information needed to confirm request ownership. We do not ask users to send valid credentials through public channels or make unrelated information a condition of order delivery.
Order and billing records may include the selected model, rental period, data center, add-ons, order amount, USD billing status, transaction reference, activation time, and expiration time. The actual availability of the three models and five data centers is shown in real time by the console.
Device and access logs may include request time, network address, browser or client type, login result, session identifier, node access status, and security event records. Support content may include ticket text, email exchanges, error summaries, redacted logs, command output, and reproduction steps provided by the user.
If you voluntarily submit additional materials, we process them only for the support purpose stated at submission. Do not include unrelated personal data, complete keys, payment credentials, or other unnecessary sensitive information in tickets, emails, or attachments.
3. Processing Purposes
We use account and contact information for identity verification, account management, important service notices, and responding to requests. Order data is used to confirm configuration, prepare dedicated physical nodes, issue connection credentials, record rental periods, process renewals, and display service status.
Device, access, and security logs help identify unusual logins, protect the console and nodes, investigate connection failures, restrict unauthorized access, and verify that critical operations completed as expected. Troubleshooting materials are used only to locate reported issues, reproduce errors, and provide the appropriate resolution path.
Billing and contract records are used to verify order amounts, confirm payment results, fulfill service commitments, resolve accounting issues, and meet necessary recordkeeping obligations. We may also process relevant data when required by applicable law or necessary to protect the legitimate interests of the platform, users, or third parties.
We do not use code snippets, build logs, or business descriptions in support tickets for public display unrelated to delivery or support. If a broader processing scope is needed, we will provide an explanation and take appropriate measures as required.
4. Payment Data
ArmCLI supports USDT-TRC20 and card payments by Visa, Mastercard, and Amex processed through Stripe. All orders are billed in USD, and the available payment gateway is determined by the console.
For USDT-TRC20, the order process may record the transaction reference, amount, time, and order association needed to verify payment status. Check the network, amount, and order details before paying, and never send private keys, seed phrases, or other information that could control assets in a ticket.
For card payments processed through Stripe, payment information follows the applicable processing flow. ArmCLI receives the payment result, transaction reference, and limited billing information needed for order confirmation, reconciliation, and support; users are not required to submit complete card details by email or ticket.
For billing inquiries, provide the order number, payment method, amount, time, and a redacted transaction reference. The service team may require account ownership verification, but will not ask you to send complete payment credentials through a standard support message.
5. Logs & Retention
Security logs are retained for the period necessary to prevent abuse, investigate unusual access, and maintain service integrity. Order and billing records are retained for the period necessary to fulfill contracts, handle accounting, resolve disputes, and meet essential recordkeeping obligations. Support materials are retained for ticket handling, review, and subsequent verification.
Retention periods may vary by processing purpose, record type, account status, pending requests, and applicable obligations. We regularly assess whether continued retention is necessary and do not retain data indefinitely by default.
After the retention period, relevant data is deleted, de-identified, anonymized, or access-restricted when continued storage is legally required. Expired records in backups gradually leave the available recovery scope according to backup rotation and recovery integrity requirements.
You must move your code, certificates, keys, caches, and business data off the node before the rental period ends. Data handling after node expiration is part of resource reclamation and does not replace your own backup and offboarding checks.
6. Data Sharing
We process and disclose data only as necessary to provide services, process payments, deliver nodes, handle support requests, meet legal obligations, or protect system security. Recipients may access only the information needed for the relevant task and must not use it for unrelated purposes.
Necessary data in the payment flow is transferred according to the payment method you choose. When infrastructure, communications, or security support requires service providers, we limit the data scope to what is necessary and reduce risk through access controls, contractual arrangements, and operational records.
When legally required to respond to a valid request, or when necessary to investigate fraud, unauthorized access, malicious code distribution, or other conduct that harms the platform or third parties, we may retain or disclose relevant records to the necessary extent. Such processing remains subject to applicable procedural and scope limits.
We do not operate a business model based on selling personal data. If our organizational structure or service operations change, data processing remains subject to this policy, applicable notices, and necessary safeguards.
7. User Rights & Requests
To the extent permitted by applicable rules, users may request access to data associated with their account, correction of inaccurate information, deletion of data no longer needed, or restriction of specific processing. Some requests may be limited by contract performance, security investigations, necessary recordkeeping obligations, or the legitimate rights of others.
Logged-in users should submit a ticket through the console first, including the account email, request type, relevant orders or record scope, and desired outcome. If you cannot log in, send an email from the address associated with your account to support@armcli.com.
To prevent data from being disclosed or deleted incorrectly, we verify the requester’s identity and relationship to the relevant account, order, or ticket. Verification may include the account email, order number, recent activity, or other information reasonably known only to the account holder; we will not require complete keys or unredacted credentials.
If a request is too broad or lacks sufficient information, we may ask for a specific time period, data category, or order identifier. After verification, we process the request as required and explain the reason if more time is needed or the request cannot be fulfilled in full.
8. Cross-Regional Processing, Updates & Contact
ArmCLI provides cloud Mac physical nodes in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the Eastern United States. When you select a data center, receive node delivery, or request cross-team troubleshooting, related account, order, security, and support data may be processed across regions as needed to provide the service.
We apply appropriate access restrictions, transfer safeguards, and recordkeeping measures based on the data category, processing purpose, and service location. A node’s location does not mean all account or support data is stored there; actual processing is limited to what is necessary to provide the service and protect the system.
This policy takes effect on September 1, 2026. If the data categories, processing purposes, user rights, or service scope change materially, we will update this page’s version and effective date and provide appropriate notice through the website, console, or account contact channels.
Privacy requests, security reports, and policy questions may be sent to support@armcli.com. Logged-in users may also submit a ticket through the console. The law applicable to this policy is the law of the jurisdiction where the platform operator is based, and disputes will be handled by a court with jurisdiction in that jurisdiction.