Scope
We distinguish between the public website, communications, and authenticated service workflows so that different contexts are not conflated.
This policy applies to data activities related to visiting the runamac.com website, reviewing plans and node information, preparing or sending an inquiry through the contact page, and using the console for account verification, configuration selection, ordering, billing review, term management, and ticket communications.
The website introduces RunAMac M4 cloud Mac rental services. The current service provides dedicated physical machines rather than virtual machines. The website does not read code, build artifacts, or working directories on rented devices. Such content enters the support workflow only when you voluntarily submit it to the support team or expressly authorize the necessary diagnostic materials for a specific issue.
When you send an inquiry by email, the email service processes the sender, recipient, subject, body, and attachments. Whether an unsent draft remains on your local device depends on your browser and email app. RunAMac receives the content only after the email has actually been sent and delivered.
Covered by this policy
Website visits, contact emails, accounts and orders, payment verification, delivery records, billing, tickets, and necessary security logs.
Not read by default
Project files, code repositories, certificates, build artifacts, and command history on rented devices are not read merely because you visit the public website.
Data We Collect
The data categories involved depend on what you do; you do not need to submit order details to browse public content.
Information You Provide
When you send a pre-sales, order, technical, or partnership inquiry, we may receive your email address, name, team or project background, expected rental term, preferred node, number of parallel tasks, storage needs, desired activation time, and other information included in your message. Please do not include private credentials that are not needed for troubleshooting in inquiry text, screenshots, or logs.
Account and Order Information
When you use the console, we process account identifiers, verification records, order numbers, RunAMac M4 configuration, rental term, selected node, additional storage, Thunderbolt 5 parallel connection options, amount due in USD, billing status, delivery status, and ticket correspondence. Account credentials are handled through secure procedures and are not exposed on public website pages.
Technical Diagnostic Content
To troubleshoot connection, network, build environment, storage, or session issues, we may process error output, log excerpts, command results, incident times, reproduction steps, client environment details, and node information that you submit. Support staff should limit diagnostics to the current issue and will not request an entire project directory when the available material is sufficient.
Necessary Website Access Records
To deliver pages, identify abnormal requests, and analyze service stability, the system may record request times, pages visited, referring pages, browser and device types, language settings, network address, response status, and security events. These records support website operation and protection; they are not used to build sensitive profiles unrelated to cloud Mac rentals.
How We Use Data
Each processing activity should correspond to a clear service, communication, security, or compliance purpose.
- Respond to inquiries: Understand your use case, term, node, and storage needs, then explain service boundaries, ordering steps, or technical issues.
- Create and Deliver Orders: Confirm the configuration, node, and rental term; initialize the dedicated physical machine; and provide connection and delivery status in the console.
- Process Billing: Reconcile the amount due in USD, payment status, add-ons, renewal results, and necessary transaction references.
- Troubleshoot Issues: Use timestamps, node details, error output, and reproduction steps to identify connection, network, storage, or build-environment problems.
- Protect Service Security: Verify account activity, detect abuse and unusual access, restrict unauthorized requests, and retain necessary audit records.
- Meet Legal Obligations: Process accounting records, lawful requests, dispute materials, and information needed to protect user and platform rights where required.
If a later use differs from the context in which the data was collected, we will assess whether further notice, authorization, or discontinuation is needed. The mere existence of data does not mean its use can be expanded without limit.
Payment Data
Payment verification information and complete card details are handled separately; the public website does not store card details.
RunAMac supports USDT-TRC20 and Visa, Mastercard, and Amex payments processed through Stripe. All orders are settled in USD; the payment gateway available to you is determined by the console.
To identify an order payment, we may process the transaction hash, sending and receiving addresses, amount, network confirmation status, and linked order number.
The card payment processor handles card-detail entry, authorization, and risk-control steps. The RunAMac website does not store full card numbers or security codes.
RunAMac retains the amount, currency, payment status, timestamp, processing result, and limited transaction references needed to reconcile an order.
Payment processors may independently process necessary data within their respective roles. RunAMac uses the information it receives only to confirm payment, resolve billing issues, and meet necessary record-keeping requirements; it does not rebuild complete payment profiles on the public website.
Sharing and Processors
Only roles essential to delivering the service may process data within the relevant scope.
RunAMac may engage providers of console, identity verification, infrastructure, payment processing, email communications, logging, security, and troubleshooting services to process limited data. Each processor should receive data appropriate to its role and should not access unrelated order or diagnostic content merely because it provides one capability.
- Console and Account Services
- Process the information needed for login verification, order linking, billing display, term management, and ticket status.
- Infrastructure Services
- Process the portions of node allocation, network delivery, runtime status, and security logs required to deliver the service.
- Payment Processing Services
- Process the information needed for payment authorization, on-chain transaction identification, risk control, and payment-result reporting.
- Communications and Security Services
- Process necessary records for email delivery, abnormal-request detection, access protection, and incident investigation.
Unless expressly authorized or supported by applicable law, we do not sell personal information to third parties unrelated to the service, nor do we use code, logs, or screenshots from technical tickets as public marketing materials.
Retention and Deletion
Retention periods are determined by business purposes, accounting requirements, security investigations, and dispute-handling needs.
Contact information is generally retained until an inquiry has been handled and necessary follow-up is complete. Account and order records are retained as long as needed for active services, billing reconciliation, renewals, and disputes. Technical diagnostic materials are retained as long as needed to complete troubleshooting, verify a fix, and address related security issues. Access and security logs are retained for the period required for risk control and system operation.
When the processing purpose is complete and there is no necessary basis for continued retention, data is deleted, de-identified, or placed in restricted archives. Backup copies may be removed later during the established rotation cycle, but they will not be restored for routine business use during that period.
Limits on Deletion Requests
After verifying your identity, we will assess and carry out feasible deletion requests. Information still needed to provide an active order, reconcile billing, protect account security, handle a dispute, prove a transaction, or meet legal obligations may not be deleted immediately. If only some data can be deleted, we will explain what categories remain and why.
Deleting account-linked information may affect order lookup, invoice downloads, ticket tracking, or management of services during a remaining rental term. Before submitting a request, save any billing records, logs, and project materials you still need.
International Transfers and Security
The locations of service regions, teams, and necessary processors may create cross-region data flows.
RunAMac currently offers five service nodes: Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, and the western United States. The node you choose determines where your dedicated physical machine is deployed. Account, order, payment verification, support, and security records may be processed in different regions by systems responsible for the relevant functions.
Cross-region processing does not mean that all data is copied to every node. Code, build artifacts, and working directories generally remain on the device you rent and manage. The console processes only the information needed for account, order, billing, delivery, and support workflows. If a ticket requires additional logs or screenshots, those materials enter the support workflow with the ticket rather than being automatically synchronized to every service node.
Access Controls
Permissions are granted according to role and task to reduce unrelated access to orders, billing, and diagnostic materials.
Least Privilege
Processors and internal personnel receive only the data scope and operational capabilities needed for their current responsibilities.
Logging and Tracking
Necessary account, security, and administrative actions are recorded to investigate unusual activity and verify processing.
Transmission and Isolation
Data is transmitted over protected connections, with unauthorized access restricted at the account, order, and node levels.
No security measure can eliminate every risk. If we identify a significant security incident that may affect you, we will investigate, contain, remediate, and notify as appropriate to the incident scope, available contact information, and applicable requirements.
Your Rights and Contact
You may request access, correction, deletion, or restriction of processing; identity verification may be required before we respond.
You may ask about the data categories associated with your account or contact records, obtain available copies, correct inaccurate information, delete data that is no longer needed, or request restriction of specific processing where a dispute exists. Complete fulfillment depends on the request, identity-verification result, active order status, and necessary retention obligations.
-
Step 1
Specify the Request
State which data categories you want to access, correct, delete, or restrict, along with the relevant email address, order number, or ticket number.
-
Step 2
Complete Identity Verification
We may ask you to reply from the email address linked to your account or confirm order information in a console ticket. Do not send complete payment credentials.
-
Step 3
Assess and Act
Our team will check data locations, active orders, billing requirements, and security restrictions, then take feasible action and explain anything that cannot be handled immediately.
-
Step 4
Receive the Result
The result will be sent to your original contact email or returned through a console ticket. If more information is needed, we will request it through the same communication channel.
All privacy, compliance, security-reporting, and data-rights requests can be sent to support@runamac.com. Users with an existing account or order can also log in to submit a console ticket so the request can be accurately linked to the order records.
Policy Updates
Version changes are recorded on this page; significant updates are communicated through available account or contact channels.
This policy is version 1.0 and takes effect on August 29, 2026. Future updates may reflect changes to service processes, data categories, processors, security measures, or applicable requirements. After an update, this page will show the new effective date and version information.
If a change materially affects data purposes, sharing scope, user rights, or important retention rules, we will provide reasonable notice before it takes effect through a website notice, account notification, console ticket, or contact email you have provided. Changes that correct wording, improve structure, or add explanations without materially changing processing may only update the version record on this page.
This policy is governed by the laws of the jurisdiction where the platform operator is based. Disputes arising from this policy that cannot be resolved through communication will be handled by a court with jurisdiction in that jurisdiction under applicable procedures.