Privacy Policy

This policy applies to information processing when you visit minibinary.com, browse MiniBinary Cloud Mac service information, create or manage an account, configure an order, complete payment, use a delivered dedicated physical node, or communicate with our team by email or console ticket.

The ordering process includes choosing a model, rental term, region, storage extensions, and connection options, as well as confirming orders, generating invoices, verifying payment status, delivering services, renewing rentals, and handling expiration. Support includes pre-sales selection advice, order inquiries, remote access troubleshooting, network diagnostics, billing checks, security reports, and other service-related communications.

When you transfer project materials to a Cloud Mac through a code repository, controlled download URL, or other tool you choose, that tool’s own policy governs its processing. MiniBinary processes only the information required to provide physical-node rental, remote access, and technical support, and does not proactively read project content unrelated to a support request.

We collect the information needed to provide the service features you use. Not every category below is generated during every visit; the actual scope depends on whether you only browse the website, create an order, use the console, or request human support.

Account & Contact Details

This includes the email address used to identify and contact you, verification status, account security records, and contact or team information you voluntarily provide in a ticket.

Order & Service Records

This includes the order number, selected model, rental term, node region, add-ons, order status, delivery status, renewal records, invoice amount, and payment confirmation result.

Device & Browser Information

This includes browser type and version, operating system, interface language, access time, referring page, basic network identifiers, and security session information, used to maintain sign-in status, support interface compatibility, and detect unusual access.

Support Communications

This includes ticket subjects, issue descriptions, order numbers, target nodes, incident times, reproduction steps, and screenshots, diagnostic results, or log excerpts that you voluntarily submit after removing sensitive information.

Operational & Security Logs

This includes sign-in attempts, session creation, access-credential changes, key account actions, service-status events, error codes, and necessary network diagnostic data, used for delivery, troubleshooting, auditing, and security protection.

Do not submit unrelated secrets, tokens, complete payment credentials, private source code, or unredacted personal data in a ticket. Technical troubleshooting usually requires only the order number, time range, node, reproduction steps, error details, and a trimmed log excerpt.

We use information only as needed to provide services, fulfill orders, operate securely, and meet applicable requirements. Our main processing purposes are:

• Service delivery: Confirm the selected configuration, rental term, and node; assign a dedicated physical machine; generate access credentials; and display order and instance status in the console.
• Identity & account verification: Send verification codes, verify sign-in requests, handle account recovery, detect unusual sessions, and protect instances, invoices, and support records in your account.
• Billing & payment processing: Generate USD invoices, verify payment results, link transactions to orders, process renewals, and retain necessary financial records.
• Troubleshooting: Use the node, time, error code, network metrics, and reproduction steps to identify issues with remote connections, system status, access credentials, or order workflows.
• Security protection: Detect automated abuse, unauthorized access, malicious requests, account-takeover risks, and behavior that could affect node stability.
• Service improvement: Aggregate page-performance, feature-error, and compatibility data to improve website speed, user flows, and troubleshooting messages, without creating profiles unrelated to the service.
• Legal obligations: Retain, verify, or provide necessary records as required by the laws of the jurisdiction where the platform operator is established, and respond to legally authorized procedures.

Where processing requires your choice or consent, we will explain this in the relevant interface. Withdrawing optional consent will not affect processing lawfully completed before withdrawal, nor stop processing required for order delivery, account security, or billing records.

MiniBinary orders support only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe), all settled in US dollars (USD). The payment gateways actually available at checkout are determined by the real-time response from our backend.

Payment records are linked to order and billing records to confirm service delivery, process renewals, reconcile transactions, and meet necessary financial-record requirements. We do not use payment information to create marketing profiles unrelated to order fulfillment.

The website and console use necessary cookies or similar local-storage mechanisms to maintain secure sessions, save language preferences, link sign-in status, validate requests, and remember essential interface settings. Disabling these necessary mechanisms may prevent sign-in, ordering, instance viewing, or ticket submission from working properly.

We also collect basic website-performance data, such as page-load times, resource errors, page paths, device category, browser version, and approximate session duration. This helps us identify slow loading, broken links, compatibility issues, and unusual traffic, and assess website performance in aggregate.

You can use your browser settings to view, delete, or restrict cookies. After clearing session data, you may need to sign in again and select your language. We do not use basic analytics data to infer sensitive characteristics or sell personal information generated by website visits.

We work with service providers only as necessary for service delivery, payment processing, security, infrastructure operations, support communications, or compliance. They may process necessary information only for agreed purposes and must apply access controls and security measures appropriate to the processing risks.

Potential collaboration categories include payment processing, infrastructure and node operations, email delivery, security monitoring, website-performance analytics, and professional compliance support. We limit data fields, access scope, and processing periods for each task, and do not give partners access to account content, ticket records, or node data unrelated to their work.

Because website access, payment confirmation, service nodes, and support operations may be located in different regions, necessary information may be processed across borders. We assess the processing purpose, data categories, recipient capabilities, contractual safeguards, and security measures as required, and minimize the amount of data transferred between regions.

If a business reorganization, merger, or asset transfer involves a service successor, relevant information will be transferred only as needed to continue providing services and protect user rights, and will remain subject to this policy or rules providing an equivalent level of protection.

How Retention Periods Are Determined

Retention periods vary by information type and are determined separately based on the order-fulfillment period, account duration, billing and financial-record requirements, security-audit needs, ticket status, dispute-handling periods, and applicable legal requirements. When the processing purpose is fulfilled and there is no continuing basis for retention, we will delete, anonymize, or isolate the information with restricted access.

Service expiration does not mean that all order records are deleted immediately. Order status, amounts, payment results, and necessary communications may need to be retained for billing reconciliation, security investigations, and legal obligations. You should migrate data you manage on the node before the rental term ends; after access status changes, you may no longer be able to read the node’s contents.

Our Security Measures

We protect information through account verification, role-based permissions, least-privilege access, transmission safeguards, records of key actions, unusual-sign-in detection, credential management, and necessary internal access approvals. Personnel involved in support and operations access relevant records only as required for a defined task.

If you suspect unusual activity involving your account, access credentials, or order information, first update available credentials, then submit a console ticket with the order number, time of the incident, and actions observed. Do not attach unredacted secrets or complete logs to an ordinary email.

Requests You Can Make

Where applicable, you may request a copy of information related to you, correction of inaccurate data, deletion of information no longer needed, restriction of specific processing, objection to optional processing, or structured data suitable for transfer. We will verify the account relationship based on the request type to prevent disclosure to unauthorized persons.

1. 01
   Describe Your Request

   State the account email, relevant order number, information categories you want to access or have processed, and the action you want taken.

2. 02
   Complete Identity Verification

   We may confirm the relationship between the requester and the account through an account session, email verification, or order-linked information.

3. 03
   Receive the Result

   Track progress through the ticket status or email reply. If some records must still be retained, we will explain the relevant data categories, purposes, and basis for that decision.

A deletion request does not affect the lawfulness of processing completed before the request. For records still needed for order fulfillment, account security, billing reconciliation, dispute handling, or legal obligations, we will limit their use for the necessary period and delete or anonymize them once the basis for retention no longer exists.

We may update this policy when our service processes, data-handling practices, security measures, or applicable requirements change. The current version month is shown at the top of the page. For material changes to processing purposes, information categories, sharing scope, or user rights, we will provide notice in a prominent place on the website, in-account notifications, or the email associated with your account.

The updated policy applies from the version period stated on the page. For new processing that requires a separate choice or consent, we will provide clear information before enabling the relevant feature and will not rely solely on a general policy update instead of the required choice process.

This policy is governed by the laws of the jurisdiction where the platform operator is established. Disputes related to this policy should first be raised through support; if unresolved, they will be handled by a court with jurisdiction in that jurisdiction.