Which service activities does this cover?
This policy applies to visits to armvms.com; account creation and management; order configuration; billing and node status; receipt of connection details for dedicated Apple Silicon physical nodes; and service communications through console tickets or the support email.
Data processing covers three areas: the website delivers pages, protects access, and records necessary technical events; management identifies accounts, processes orders, displays payment status, and delivers nodes; support receives issue descriptions, redacted logs, and necessary follow-up materials.
Website visits
This includes page requests, necessary access records, security events, and language and page preferences.
Orders and nodes
This includes selected configurations, rental terms, nodes, add-ons, delivery status, and related activity records.
Service support
This includes ticket content, email correspondence, issue timestamps, and diagnostic materials users voluntarily provide.
This policy concerns information ArmVMS processes to provide its services. Code, build artifacts, model files, and business data stored on physical nodes are organized by users themselves; they enter the support scope only when users voluntarily submit relevant excerpts for troubleshooting.
Types of information we process
The information required depends on what you do. Browsing the website, placing an order, completing payment, and submitting a technical ticket involve different data sets; viewing a single page does not require complete order details.
| Information category | Details | Primary source |
|---|---|---|
| Account and contact details | Email address, account identifier, verification status, and necessary communication records | User submissions and account activity |
| Order details | Order number, M4 or M4 Pro configuration, rental period, selected node, and add-ons | User selections and order workflow |
| Payment status | Amount due, USD settlement records, payment channel type, transaction status, and necessary reconciliation identifiers | Returned by the checkout process |
| Device and access logs | Request time, network address, browser or client type, login result, target of the action, and security events | Website, console, and security systems |
| Ticket and email content | Issue type, order number, node, time of occurrence, error description, redacted logs, and response records | Voluntarily submitted by the user |
| Other information provided voluntarily | Pre-sales workload details, project environment requirements, storage needs, or partnership inquiry materials | Voluntarily submitted by the user |
Before submitting support materials, remove passwords, private keys, access tokens, and other sensitive credentials not needed to diagnose the issue. If logs contain project paths, repository names, or internal addresses, redact them first.
How information is used to deliver services
Each processing activity must correspond to a defined service function. Key purposes include account identification, order fulfillment, node management, security, troubleshooting, and necessary notices directly related to existing services.
Account identification
Verify account ownership, maintain sign-in status, and associate orders, billing, and tickets with the correct account.
Order fulfillment
Verify the model, memory, storage, rental period, node, and add-ons, and create the related delivery record.
Node management
Display physical node status, linked orders, and connection details, and record necessary administrative actions.
Security
Detect unusual sign-ins, unauthorized access attempts, malicious scanning, and activity that may affect the service.
Troubleshooting
Reproduce and diagnose issues using the time of occurrence, node code, error information, and redacted logs.
Service notices
Send necessary information such as order results, security alerts, ticket replies, and policy updates.
If the purpose of processing materially changes, we will assess whether to update this explanation, narrow the data scope, or obtain additional authorization. Technical support materials already submitted will not be repurposed for unrelated uses.
Payment methods, currency, and processing fields
ArmVMS supports only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All transactions are settled in USD. The gateway actually available is determined by the result returned during checkout.
- Card payment
- The payment process handles the card details, verification result, transaction status, and reconciliation identifier needed to complete the transaction. ArmVMS uses the necessary result fields to confirm order status.
- USDT-TRC20
- We process the amount due, on-chain payment identifiers, confirmation status, and order association to complete reconciliation and delivery.
- Single currency
- Plan prices, add-ons, billing records, and refund or adjustment records are stated and calculated in USD.
- Data use
- Used to confirm payment, associate orders, reconcile finances, identify unusual transactions, and handle billing disputes.
The fields required vary by payment flow. Each flow should process only the information needed to complete payment, verify the transaction, and meet necessary recordkeeping obligations. ArmVMS advances orders based on the returned payment status rather than building service-unrelated user profiles from payment data.
How necessary logs support security and troubleshooting
To prevent abuse, investigate unusual access, diagnose delivery issues, and protect accounts and physical nodes, ArmVMS retains necessary event-related logs. Depending on the function, logs may include request time, network address, client type, account identifier, action result, order number, node code, and error information.
Log review sequence
- 1Confirm the event scope
Check the time, account, order, and node to avoid including unrelated sessions in the investigation.
- 2Identify the action result
Check whether the request succeeded, why it failed, and whether a security rule was triggered.
- 3Limit the material scope
Use metadata and error records first, requesting additional redacted materials only when necessary.
- 4Record handling actions
Retain necessary records related to event handling, ticket responses, and account protection.
The support team does not need passwords, private keys, or access tokens to verify order and node status. If a ticket accidentally includes any of these, say so immediately in the same conversation so we can assess the appropriate next steps.
Information moves only as needed
ArmVMS does not sell personal information as a business. Information is processed or provided only to the extent necessary to deliver services, process payments, meet applicable compliance requirements, or protect the lawful interests of users, the platform, and others.
Service delivery
To complete account verification, order processing, physical node delivery, email delivery, or technical support, the service workflow responsible for the function may receive the minimum fields needed to complete the task.
Payment processing
Card payments are processed by Stripe; USDT-TRC20 payments are verified through the transaction confirmation process. Each flow receives only what is needed to complete the transaction and return its status.
Compliance requirements
In response to valid and binding requirements, we may process information that must legally be provided and assess the scope, recipients, and necessity of the request.
Protection of rights
We may use and retain relevant evidence to investigate fraud, abuse, unauthorized access, malicious scanning, or other conduct that infringes lawful rights.
When an external process performs a specific processing task for ArmVMS, we limit data use and access to that task. If a change in our business structure materially changes the processing entity or purpose, we will provide an updated explanation through an appropriate channel.
Retention depends on the purpose of the record
Different records do not have the same retention period. We assess necessity based on order fulfillment, billing reconciliation, support handling, security investigations, dispute records, and legal obligations, then delete, de-identify, or restrict further use when the purpose is complete.
Order and billing records
The necessary retention period is determined by order delivery, transaction reconciliation, accounting records, and dispute handling needs.
Support communications
Retained as needed for issue handling, review, related requests, and follow-up materials; cleaned up when no further purpose remains.
Security logs
The retention scope is determined by the needs of risk investigations, account protection, abuse prevention, and evidence integrity.
Records required by law
Necessary records are retained to the extent required by the laws of the jurisdiction where the platform operator is based.
How to submit a request
Users can submit requests through support@armvms.com or by signing in tothe console to submit a ticket, including requests to access, correct, or delete information. To prevent account impersonation, we may need to verify the account email, order number, or other information sufficient to confirm the requester’s relationship to the account before processing the request.
A request should identify the relevant account, order, or ticket and specify the records to access, correct, or delete. If certain information is still needed to complete a transaction, handle a dispute, investigate a security issue, or meet a necessary obligation, we will explain its current status and applicable limits.
Policy updates, contact, and applicable rules
This policy takes effect on August 29, 2026. If information categories, processing purposes, sharing scope, or user request methods materially change, we will update this page and notify users through the website, console notices, or another method appropriate to the existing service relationship.
Privacy questions, security reports, data requests, and policy interpretations all use the same support channel. When emailing, put “Privacy Request” in the subject and include your account email, relevant order or ticket number, request scope, and verifiable context. Do not attach passwords, private keys, or access tokens.
This policy is governed by the laws of the jurisdiction where the platform operator is based. Any dispute arising from this policy that cannot be resolved through communication will be handled by a court with jurisdiction in that jurisdiction.
This policy should be read together with theTerms of Service. For configuration choices, node delivery, or general technical questions, check theHelp Centerfirst, then provide any necessary materials in the same ticket conversation.