1. Scope and effective date
This policy applies to personal information processed through the ArmRDP website and console, and in connection with renting a dedicated physical Mac. Our services include account setup, order payment, instance delivery, billing and support tickets. ArmRDP provides dedicated physical nodes, not virtual machines. This policy distinguishes information used to operate the service from user content stored on rented hosts.
This policy takes effect on its publication date. You can review the relevant sections before submitting account information, placing an order or sending a support ticket. Section 8 explains how to exercise your personal information rights, and Section 9 provides contact options. Service scope, billing and acceptable use are covered separately in our Terms of Service; this policy explains how information is handled.
This policy is governed by the laws of the jurisdiction where the platform operator is based. We encourage you to contact us through the channels listed in this policy to resolve any concerns. If a matter must be resolved through legal proceedings, it will be handled by a court with jurisdiction in that jurisdiction.
2. Information we collect
Account information. To identify your account, verify sign-ins and send service notices, we process the email address you provide, necessary verification records and any contact details you choose to add. Names, team details and information about your needs that you share in an enquiry or support ticket also become part of the related correspondence. Please provide only information relevant to your current service request.
Order and payment records. We process order numbers, Mac models, nodes, billing periods, add-ons, amounts charged in US dollars, payment results and renewal records. The only payment methods are USDT-TRC20 and Visa / Mastercard / Amex (via Stripe); available payment gateways are determined by the response from our backend. Payment reconciliation may involve a Stripe transaction ID or a USDT-TRC20 on-chain transaction ID, relevant addresses and amounts. Card details are submitted to Stripe during payment processing and should not be sent to us by email or support ticket.
Support ticket content. We process the issue description, host ID, time of occurrence, troubleshooting steps and any logs or screenshots you choose to provide. Screenshots and build logs may contain project names, paths, tokens or certificate information. Before submitting, redact anything unrelated to troubleshooting. Do not include private keys, full passwords or unredacted access credentials.
Access and service logs. To keep the website and console secure, we process necessary IP addresses, access times, request paths, browser and device types, request outcomes and security event records. These logs help protect sign-ins, diagnose issues and measure site traffic. They are not used to read or analyse code on your rented host.
3. What we don’t access
We do not access or analyse user files or code on rented hosts. Your repositories, build artefacts, project configuration and business data are outside the scope of website analytics and are not used for ad profiling or model training. Renting a dedicated physical node does not grant ArmRDP any rights to use your project content.
Our support starts with your account, order and connection details, plus any diagnostic materials you choose to provide. If resolving an issue genuinely requires more information, we will first explain what we need and why. You can then decide whether to share relevant redacted logs or results. To speed up troubleshooting, do not send complete projects, signing private keys or host passwords.
Code snippets, logs and screenshots you choose to include in a support ticket or email are handled as part of that support request. This distinction matters: we do not proactively analyse content stored on your host, while materials you send to support may be reviewed as needed to resolve your request.
4. How we use information
Setup and delivery. Account and order information helps us verify requests, link them to your rented instance, provide access details, display subscription status and send service notices to your account email. We process information only as needed for these tasks and do not ask you to provide project materials unrelated to your rental.
Billing and reconciliation. Order and transaction records help us confirm payments, issue invoices, verify renewals, resolve payment issues and handle eligible refund requests. Transaction IDs help us locate specific payments; a payment screenshot alone cannot replace verification against the order and transaction result.
Troubleshooting and security. Support tickets and necessary logs help us reproduce connection issues, investigate service disruptions, identify suspicious sign-ins and detect abuse. Traffic statistics help us see which pages or actions could be improved. We do not sell your personal information or use files on rented hosts as product analytics data.
5. Third-party processors
Stripe. If you pay by card, Stripe processes the information needed to complete payment and perform risk checks. ArmRDP uses the payment result, transaction ID and necessary reconciliation details associated with your order to confirm service status. Enter card details on the payment page; do not send them again by support email or ticket.
USDT-TRC20 transaction records. If you pay this way, we use the on-chain transaction ID linked to your order to verify payment. Blockchain records are publicly verifiable. Deleting your account information from ArmRDP does not remove transactions already recorded on the public ledger. Before sending payment, check the network, address and amount shown on the checkout page.
Data centre providers. Data centre providers help us host nodes, maintain network connectivity and secure physical facilities. They process only the equipment and network information needed for hosting, network troubleshooting and facility security. Providing hosting does not give them permission to access your project files or code.
We limit information shared with processors to what is needed for the specific service. If disclosure is legally required, we will verify the basis for the request and limit what we disclose. Where permitted, we will notify affected users.
6. Data retention and disk erasure after your rental
We retain account information for as long as your account is active and as needed to provide the service. Order, payment and support records are retained as needed for reconciliation, dispute handling, security and applicable legal requirements. Different types of information serve different purposes, so we do not apply a single retention period to all records. Information that is no longer needed is deleted or de-identified.
After your rental ends and the service is terminated, user data on the rented disk enters the erasure process. The node is not assigned to another renter until erasure is complete. Disk erasure and account record deletion are separate: erasing host data does not delete order or payment records that must be retained, and deleting your account does not automatically end an active rental order.
Before your rental ends, export any repository changes, build artefacts, certificates and other materials you need to keep. Once the host has been erased, do not assume data from the node can be recovered. To check the data handling status of an instance, submit a console support ticket with the host ID and order number. Do not attach original data you need to keep to an email.
We protect operational data with access controls and necessary activity records. Access to account, billing and support information is limited according to staff responsibilities. Materials provided to resolve a particular request should not be used for unrelated purposes.
7. Cookies and analytics
The website and console may use cookies or similar local storage to maintain sign-in sessions, support security checks and remember essential interface preferences. This storage enables account features to work properly. If you clear or block it, you may need to sign in again, and some session-based actions may not work.
We use same-domain analytics to record page visits and key interactions, such as viewing a plan, starting a rental or reading documentation, to understand whether pages help users complete tasks. Analytics do not include reading user files on rented hosts and should not capture passwords, verification codes, signing private keys or full payment card details.
You can use your browser settings to view, clear or restrict this site’s storage and manage the tracking protection options your browser provides. To learn how information related to your account is handled, you can submit an access request as described in the next section. Changes to your browser settings do not give us additional permission to use information for other purposes.
8. Access, correction, deletion and export
You can request access to your account information, correct inaccurate details, delete information that is no longer needed, or export available account and service records. A personal information export is not a host backup. You must use your own access method to export project files and build artefacts from a rented node.
If you can sign in, submit a support ticket in the console. Include the type of request, the relevant account or order, and the information you want us to handle. If you can’t sign in, contact us from your account email at support@armrdp.com. We’ll verify your identity in a way that matches the risk of the request to avoid sharing information with someone who isn’t authorised.
If a deletion request concerns an active order, an unresolved payment reconciliation or records we are legally required to retain, we will explain what can be handled, what must be kept and why. You do not need to send host passwords, complete identity documents or payment card details with your request. If we need additional information, we will explain exactly what we need and how it will be used.
You can add to, narrow or withdraw a request that is still in progress in the same support ticket or email thread. If you have questions about the outcome, quote the original request number and specify what you would like us to review. This helps us match the review to the original records.
9. Contact and policy updates
For privacy enquiries, requests to exercise your personal information rights, or data security reports, email support@armrdp.com or sign in to the console and submit a support ticket. We recommend using “Privacy request” or “Data security report” as the subject, and including the relevant account, incident details and a contact email in the message. Do not include passwords or private keys.
If we update this policy because of changes to product features, processing purposes or applicable requirements, we will publish the revised version here. We will also notify you by account email or through the console of significant changes to how information is processed or your rights. The new version will state when it takes effect. Where separate consent is required, silently updating this page does not replace your choice.
If you still have questions after reading this policy, please identify the relevant section and your specific concern. Sharing the clause and related order number helps us respond accurately and is more useful than sending an entire project or a large volume of unredacted logs.